Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Migrating robotic automation packages between environments

Updated on October 7, 2021

Easily migrate robotic automation packages between environment by using the Import Wizard and the activities provided with Pega Robotic Automation Importer and with Pega Robot Manager.

For more information about the flow of robotic automation packages during deployment and migration, see Robotic automation package deployment and migration between environments.
Before you begin:
  • Ensure that you have access to the source and target repositories
  • Ensure that you have the privileges required to import packages into the production Pega Robotic Automation Importer and Pega Robot Manager environment.
  • If you are using separate Pega Package Servers in the target and source environments: Copy the automation package binaries from one Package Server to another and retain the original directory structure. For more information, see Back up configuration files and packages in the Pega Package Server and Server Status Page User Guide on Community.
  1. Export the automation package component from the source environment repository.
  2. If you are using separate repositories in the source and target environments, save the automation package component from the repository to your local drive:
    1. Import the automation package component into the production environment that contains the Pega Robotic Automation Importer component and add it to your application stack.
    2. Run the pxPublishRAPToRepository activity on the Pega Robotic Automation Importer component to push the automation package component to migrate.
    3. Run the pxImportAutomationPackageFromRepo activity on the target Pega Robot Manager system to pull the automation package component.
  3. If you are using a repository that is shared between the source and target environments, save the automation package component from the repository to your local drive:
    1. Import the robotic automation package component into the target environment that contains the Pega Robotic Automation Importer component and add it to your application stack.
    2. Run the pxImportAutomationPackageFromRepo activity on the target Pega Robot Manager system to pull the automation package component.
Result: The robotic automation package is now migrated from the source environment to the target environment. Depending on your choices, you migrated either all versions of the automation package (default behavior) or only some specific version.
  1. Importing robotic automation package components to Pega Robotic Automation Importer

    After saving a robotic automation package component from the source environment, import it to the target environment's Pega Robotic Automation Importer by using the Import Wizard. Then, add the imported package component to the application stack.

  2. Publishing automation package components to a repository in the target environment

    An automation package component published in Pega Robotic Automation Importer is automatically relayed to the depository in the original environment. The package component versions are also kept synchronized.

  3. Importing automation package components from your repository to Pega Robot Manager

    During migration, you first import an automation package component to Pega Robotic Automation Importer and then you publish it to your repository in the target environment. Finally, you import the package component to the target environment's Pega Robot Manager.

  • Previous topic Robotic automation package deployment and migration between environments
  • Next topic Importing robotic automation package components to Pega Robotic Automation Importer

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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