Use this process step to roll back a component version to the version in a snapshot or to the version that was deployed when the process began.
Applications, components, and generic processes share some process steps. This step applies only to application processes.
For a video demonstration of rolling back components, see Rollback Scenarios in IBM® UrbanCode® Deploy.
In most cases, to switch to a different version of a component, you deploy the new version over the existing version. If necessary, you can run the uninstall process for the component first.
- Remove Undesired Incremental Versions: This option removes versions that are not in a specified snapshot. See Rolling back to a snapshot.
- Replace with Last Deployed: This option rolls back components that fail to deploy. See Uninstalling components with an application process.
|Name||A name for the step. Other process steps can refer to this step by this name.|
|Component||Component that is used by the step; a step can affect a single component. All components that are associated with the application are available. If you want to roll back another component, add another rollback step to the process or use the Rollback Multiple Components step.|
|Remove Versions with Status||Restricts the component versions that are affected by the
step. Only versions with the selected status are affected. By default, the status
|Component Process||The component process to run. In most cases, select a component process that uninstalls the component.|
|Limit to Resource Tag||The user-defined resource tag that determines which resource runs the process. Only a resource with this tag, or a resource that has a parent with this tag, runs the process. See Adding tags to objects.|
|Rollback type||Determines the type of rollback. If you specify
|Maximum number of concurrent processes||The maximum number of concurrent processes to run. This
setting limits the number of processes that run simultaneously. For example, if you set the maximum
number of concurrent processes to 2, only two instances of a component are rolled back at a time,
even if there are many instances of the component. To run an unlimited number of concurrent processes, specify
The server attempts to resolve the value to an integer. If the value does
not resolve to an integer, then the
Note: The maximum number of component processes that can run concurrently is limited by the hardware that hosts the agent.
|Fail Fast||If this check box is selected, the step does not start more processes after one process fails.|
step can run. The condition must resolve to