Skip to main content

Preparing environments for deploying Pega Robot Manager applications

Suggest edit Updated on May 25, 2021

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.

Configuring the orchestrator environment for Pega Robot Manager DevOps

Prepare the orchestrator to manage the deployment of Pega Robot Manager applications between connected environments.

  1. Install the Deployment Manager application.
  2. Import the Pega Robotic Dev Ops application to the orchestrator environment.
    Note: Pega Robot Dev Ops application facilitates migrating Robot Manager applications and the associated automation package repositories between the connected environments.
    1. Download the PegaRobotManager_<version>.zip file from Pega Marketplace and then extract the contents of the file to a directory of your choice.
    2. Use the Import Wizard to upload the Pega-Robotics-DevOps.jar to your application.
      The PegaRoboticDevOps_<version>.jar file is in the PegaRobotManager_<version>\Rules folder.
  3. Include the Pega Robotics Dev Ops application in the system runtime context, above Pega Deployment Manager.
    1. In Dev Studio, select ConfigureSystemGeneralSystem Runtime Context.
    2. On the System Runtime Context tab, in the Applications section, click Add application.
    3. Select PegaRoboticDevOps by pressing the Down arrow key.
    4. Hover your mouse cursor over the number that corresponds to the PegaRoboticDevOps application and then move the application record so that PegaRoboticDevOps precedes PegaDeploymentManager, as shown in the following example:
      The current application on top of the system runtime context in the orchestrator environment
      System runtime context must include the PegaRoboticDevOps
                                        application on top of the application list
    5. Confirm your settings by clicking Save.

Configuring candidate environments for Pega Robot Manager DevOps

Prepare each candidate environment that contains the Pega Robot Manager application and the associated automation package artifacts for migration between environments.

Note: You do not need to import the Pega-Robotics-DevOps ruleset in a candidate environment because the latest version of the Robot Manager application includes that ruleset by default.
  1. To migrate automation package files in addition to Robot Manager applications, move the packages to a repository that Robot Manager controls.
    Important: You cannot migrate automation packages through a Deployment Manager pipeline if you are storing the packages in a local Package Server. For more information, see Storing robotic automation packages in Pega Robot Manager.
  2. Enable the Robot Manager application for DevOps.
    For more information, see Setting up candidate environments.
Result: This environment is now enabled for DevOps. The following figure shows an example application in a candidate environment that you can use as part of your deployment pipeline:
A client application implementing Robot Manager that is enabled for DevOps
After performing the DevOps setup, your application can take part in a
                        deployment pipeline
What to do next: Build a deployment pipeline. For more information, see Understanding deployment pipelines for Pega Robot Manager applications.
    • Next topic Understanding deployment pipelines for Pega Robot Manager applications
    Did you find this content helpful? YesNo

    Have a question? Get answers now.

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

    Ready to crush complexity?

    Experience the benefits of Pega Community when you log in.

    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