Deploy the component

  1. Open the application page by clicking Applications and then clicking the application name.
  2. In the same row as your environment, click the Request Process icon .
  3. In the Run Process window, accept the default value for the Only Changed Versions parameter. If this check box is selected, no previously deployed component versions are deployed.
  4. In the Process list, select the hello App Process process.
  5. Click Choose Versions. The Component Versions window opens.
  6. In the Component Versions window, click Select For All, and then select Latest Available. Click OK to return to the Run Processwindow.
  7. Click Submit. The Application Process Request page shows the progress of the request. From here, you can watch as the process runs. The following figure shows the running process.
    The Application Process Request page with running process
    If the process finishes, the Success status is shown, as in the following figure:
    The Application Process Request page with the Success status shown

    If the application process execution is not successful, click Expand All and in the same row as your application process, click View Child Execution. View Child Exection does not appear until you hover the mouse over the process. The Deployment of Component page shows the log for each step in the component process. From here, you can look at the output log for each step by clicking the Output Log icon .

  8. Open the target directory to confirm that the component artifacts are deployed.

Installs the selected component with one of the processes that are defined for the component.
Table 1. Install Component properties
Field Description
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 install another component, add another install step to the process.
Use Versions Without Status Restricts the components that can be used by the step. Components with the selected status are ignored. Available statuses: Active means ignore components that are currently deployed.
Component Process A process for the selected component. All processes that are defined for the component are available. Only one process can be selected per step.
Ignore Failure When selected, the step is always considered to have run to completion.
Limit to Tag User-defined can be used in processes see Tagging resources.
Run on First Online Resource Only Instead of being run by all agents that are mapped to the application, the step runs only by the first online agent that is identified by IBM® UrbanCode Deploy. The mechanism that is used to identify the "first" agent is database-dependent (thus indeterminate).
Precondition A JavaScript script that defines a condition that must exist before the step can run. The condition must resolve to true or false.

 

Install multiple components that are based on component tags or resource tags.

This step concurrently installs multiple components. All components that are associated with the application can be installed, or installation can be restricted to only those components with a particular component tag or resource tag.

Table 1. Install Multiple Components properties
Field Description
Name A name for the step. Other process steps can refer to this step by this name.
Component Tag A user-defined component tag that is used to select components. Components with the specified tag are installed. If the All Components value is selected, all components that are part of the application are installed.
Component Process A process for the selected component. All processes that are defined for the component are available. Only one process can be selected per step.
Ignore Failure When selected, the step is always considered to have run to completion.
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.
Maximum number of concurrent jobs The maximum number of component processes to run at the same time. To run an unlimited number of concurrent processes, specify -1.
Fail Fast If this check box is selected, the step does not start more processes after one process fails.
Run on First Online Resource Only Instead of being run by all agents that are mapped to the application, the step runs only by the first online agent that is identified by IBM® UrbanCode Deploy. The mechanism that is used to identify the "first" agent is database-dependent (thus indeterminate).
Precondition A JavaScript script that defines a condition that must exist before the step can run. The condition must resolve to true or false.

 

Rolls back a component version to the version in a snapshot.

This step replaces a component version with an earlier version, based on the most recent snapshot that was deployed to the environment.

This step is appropriate for switching between different incremental component versions. To switch between different full component versions, do not use this step; instead, deploy the new component version as usual.

Table 1. Rollback Component properties
Field Description
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.
Remove Versions With Status Restricts the components that are affected by the step. Only components with the selected status are affected. Available statuses: Active refers to components that are currently deployed.
Component Process A process for the selected component. All processes that are defined for the component are available. Only one process can be selected per step.
Ignore Failure When selected, the step is always considered to have run to completion.
Limit to Tag User-defined tags can be used in processes; see Tagging resources.
Rollback type Determines the type of rollback. If you specify Remove Undesired Incremental Versions, the server runs the uninstall process for each incremental version that is not in the snapshot. If you specify Replace with Last Deployed, the server uninstalls the incremental versions in the same way and then installs the version in the snapshot.
Run on First Online Resource Only Instead of being run by all agents that are mapped to the application, the step runs only by the first online agent that is identified by IBM® UrbanCode Deploy. The mechanism that is used to identify the "first" agent is database-dependent (thus indeterminate).
Precondition A JavaScript script that defines a condition that must exist before the step can run. The condition must resolve to true or false.

 

Uninstalls the selected component.

Table 1. Uninstall Component Properties
Field Description
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 uninstall more than one component, add another uninstall step to the process.
Remove Versions With Status Restricts the components that are affected by the step. Only components with the selected status are affected. Available statuses: Active refers to components that are currently deployed.
Component Process A process for the selected component. All processes that are defined for the component are available. Only one process can be selected per step.
Ignore Failure When selected, the step is always considered to have run to completion.
Limit to Tag User-defined can be used in processes see Tagging resources.
Run on First Online Resource Only Instead of being run by all agents that are mapped to the application, the step runs only by the first online agent that is identified by IBM® UrbanCode Deploy. The mechanism that is used to identify the "first" agent is database-dependent (thus indeterminate).
Precondition A JavaScript script that defines a condition that must exist before the step can run. The condition must resolve to true or false.