Application processes

Application processes, like component processes, are created with the process editor.

IBM® UrbanCode Deploy provides several common process steps. Otherwise, application processes are assembled from processes that are defined for their associated components.

Application processes can run manually, automatically on some trigger condition, or on a user-defined schedule. When a component has several processes, the application determines which ones run and in which order.

An application process is always associated with a target environment. When an application process runs, it interacts with a specific environment. At least one environment must be associated with the application before the process can run. Application processes are independent of environment; processes can be designed independently of any particular environment. To use the same process with multiple environments (a typical scenario), you associate each environment with the application and run the process separately for each one.

In addition to deployments, several other common processes are available, such as rolling-back deployments. IBM UrbanCode Deploy tracks the history of each component version, which enables application processes to restore environments to any point.

Application process and the steps that comprise them are configured with the process editor. For information about using the process editor, see Process editor. For information about individual process steps, see Application process steps.


Feedback