Skip to main content

Migrating Pega Robot Manager applications by using DevOps

Suggest edit Updated on October 7, 2021

Simplify migrating Pega Robot Manager applications with the associated automation package files and metadata between environments by using Deployment Manager. In this way, you avoid manual downloading and uploading of package components and generating multiple copies of the same package.

With Deployment Manager, you can speed up the migration process, reduce the operational costs of each migration, and ensure that you consistently meet your quality requirements. For example, you can include Pega Platform unit testing in the migration process.

When using DevOps to migrate your robotic solution, you must have the following types of environments:

Orchestrator
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.
Candidate
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:

Environment types that manage Robot Manager migration
Migrating Robot Manager applications between environments requires two
                            types of environments: Orchestrator and Candidate

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.

What to do next: Follow these steps to use DevOps for migrating and deploying Robot Manager applications:
  1. Preparing environments for deploying Pega Robot Manager applications

    Before building a Deployment Manager pipeline for migrating Pega Robot Manager applications and associated artifacts, you must complete several tasks to prepare the orchestrator and candidate environments.

  2. Understanding deployment pipelines for Pega Robot Manager applications

    Learn how to build a deployment pipeline for Pega Robot Manager applications. By setting up your DevOps infrastructure, you can enable interaction between connected environments and deploy changes from one environment to another with just a few clicks.

  3. Initiating a deployment of Pega Robot Manager applications

    Save time and reduce operational costs by deploying Pega Robot Manager applications by using DevOps.

  • Previous topic Package repository data model
  • Next topic Preparing environments for deploying Pega Robot Manager applications
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us