About deploying releases

Releases are deployed to your target environments by executing deployment process instances to run the actions defined in deployment process diagrams.

There are two ways to deploy releases to your target environments:

1. by executing deployment process instances to run the actions defined in deployment process diagrams
2. by executing deployment plan instances to run through the stages defined in deployment plans, which include multiple deployment processes.

There are two safeguards built into this process:

1. All actions can be suspended if an error occurs and users can rectify the issues before re-executing the process.
2. When authorization is required users can manage validation requests to approve actions/stages/processes.

The following actions, involved in executing the deployment processes, are all completed using the Operational Console Management perspective (see the Overview of the DROPS Studio) or in the DROPS web app.

The Console Explorer provides access to the deployment process execution procedures. This perspective is the functional side of DROPS.

•  Deploying releases (see Deployment process instances),
•  Addressing suspended actions (see Suspended actions),
•  Addressing validation requests (see Validation requests),
•  Addressing interruption messages (see Interruption messages),
•  Deployment plan instances (see Deployment plan instances).