Using the Provisioning application with DCommandsAdded by IBM on October 5, 2011 | Version 1 (Original)
|Provisioning operations can also be initiated if the platform is already running. Through the use of DCommands, command arguments can be passed into a receiving class inside of the running platform.
Provisioning operations can also be initiated if the platform is already running. Through the use of DCommands, command arguments can be passed into a receiving class inside of the running platform.
To start the platform such that either the DCommands are passed through to a running instance, or a new instance is launched to process the arguments, use the following syntax to launch:
-com.ibm.rcp.provisioning#provisioningCommand –provisioningOperation command
This results in one of the following:
- The existing platform (currently running the workbench) is passed the provisioning arguments, and the provisioning occurs inside of the existing platform. When provisioning is complete, the existing platform will continue to run until the user currently using the platform decides to shut down.
- A new instance of the platform will start using the Provisioning application and the provisioning will occur using this new instance of the platform. When provisioning is complete, the platform will exit.
The incoming requests are validated prior to processing the request. A validation failure will result in the immediate failure of the request. No attempt to partially process the request will occur if there is a validation failure. There are two types of validation failures that might occur:
Parent topic: Using the Provisioning application
- The first type of validation failure is an incorrect ProvisioningRequest object. Refer to the ProvisioningRequest documentation for information on the required attributes for a particular request type, and the values that may be supplied for each of the requests.
- The second type of validation failure can occur if multiple requests for the same feature ID are supplied in a single service request. The requests submitted on a service request are grouped by action—install (and installonly), enable, disable, and uninstall. For the install and enable action groups only, the list of requests may not contain multiple ProvisioningRequest objects for the same feature ID that are not attribute equivalent. This will result in a validation failure. As an example, an attempt to install feature ID A (version=1.0.0, match=perfect) and feature ID A (version=1.0.1, match=compatible) in the same request will fail. If the ProvisioningRequests supplied are equal (all fields match), this is not considered a validation failure and the request will attempt to be processed.