When using DevOps to migrate your robotic solution, you must have the following types of environments:
- A single environment that contains the Deployment Manager application and coordinates the migration process between environments. As part of the Robot Manager deployment team, you use Deployment Manager to define the migration pipeline, which is a set of instructions for how to move your application between various environments.
- Any environment that the Deployment Manager pipeline manages, irrespective of whether that environment is a source of data or the target to which the data is migrated. Depending on your business needs, you can have multiple candidate environments in your system, for example, development, user acceptance testing, production, and so on.
For more information, see Understanding model-driven DevOps with Deployment Manager.
To facilitate migrating Robot Manager applications together with robotic artifacts and metadata, the orchestrator and the candidate environments must include the Pega-Robotics-DevOps component, as shown in the following figure:
After the pipeline configuration finishes, you can view the pipeline in the Robot Manager portal. In addition, the Robot Manager portal enables you to initiate the deployment of your application, as defined in the pipeline configuration.