Skip to main content


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

Robotic automation package deployment and migration between environments

Updated on December 20, 2022

Pega Robotic Automation Importer provides the capability to migrate packages across environments.

Scenario 1: Migrating a robotic automation package between environments with separate repositories

A typical use case is the initial deployment and testing of a robotic automation package in your development environment, but later using that package in your production environment. The two environments (test and production) usually use separate Pega Platform instances and have separate repositories.

The following diagram illustrates the flow of a single robotic automation package from its initial deployment in Pega Robot Studio (step 1), through its publication in the source environment (steps 2 to 4), to the migration to the target environment (steps 5 to 7).

Robotic automation package flow during migration with separate repositories

Deployment and publication in your source environment

  1. You create a robotic automation package in Pega Robot Studio and deploy it.
  2. The Pega Robotic Automation Importer component generates all related data and rule artifacts, and describes the package and the automations that the package contains. Pega Robotic Automation Importer also bundles all data and rule artifacts into a Pega Platform component, and attaches this new component to your development stack.
  3. Pega Robotic Automation Importer automatically forwards the robotic automation package component to the source environment repository (Repository A).
  4. Pega Robot Manager automatically retrieves the robotic automation package component from the source environment repository.

You can now assign the automations within the package to Pega Robot Runtime, and run the package in your source environment.

Migration and publication in your target environment

To run the automation in a different environment, import the robotic automation package to the target environment.

  1. You manually import the robotic automation package component from the source environment repository (Repository A) to the target environment's Pega Robotic Automation Importer. After the import, you add the package to the application stack where your Pega Robotic Automation Importer resides in the target environment.
  2. You publish the robotic automation package component from Pega Robotic Automation Importer to your target environment repository (Repository B) by running the pxPublishRAPToRepository activity on the Pega Robotic Automation Importer component.
  3. You import the robotic automation package component from your target repository (Repository B) to Pega Robot Manager by running the pxImportAutomationPackageFromRepo activity.

You can now assign the automations within the package to Pega Robot Runtime, and run the package in your target environment.

The migration process is similar to the original deployment, with the following differences:

  • The package component is not imported from Pega Robot Studio, but from the source environment repository.
  • You run the activities that forward the package component to the target repository (pxPublishRAPToRepository) and to Pega Robot Manager in the target environment (pxImportAutomationPackageFromRepo).

Scenario 2: Migrating a robotic automation package between environments with a shared repository

A typical use case is the initial deployment and testing of a robotic automation package in your development environment, but later using that package in your production environment. In this case, the two environments use separate Pega Platform instances, but share a common repository.

The following diagram illustrates the flow of a final version of a robotic automation package from the deployment in Pega Robot Studio (step 1), through its publication in your development environment (the source environment - steps 2 to 4), to its publication in your production environment (the target environment - steps 5 and 6).

Robotic automation package flow during migration with a shared repository

Deployment and publication in your source environment

  1. You create a robotic automation package in Pega Robot Studio and deploy it.
  2. The Pega Robotic Automation Importer component generates all related data and rule artifacts, and describes the package and the automations that the package contains. Pega Robotic Automation Importer also bundles all data and rule artifacts into a Pega Platform component, and attaches this new component to your development stack.
  3. Pega Robotic Automation Importer automatically relays the robotic automation package to your shared repository.
  4. Pega Robot Manager automatically retrieves the robotic automation package from the shared repository.

You can now assign the automations within the package to Pega Robot Runtime, and run the package in your source environment.

Migration and publication in your target environment

To run the automation in a different environment, import the robotic automation package to the target environment.

  1. You manually import the robotic automation package from the shared repository to the target environment's Pega Robotic Automation Importer. After the import, you add the package to the application stack where your Pega Robotic Automation Importer resides in the target environment.
  2. You import the robotic automation package from the shared repository to Pega Robot Manager by running the pxImportAutomationPackageFromRepo activity.

You can now assign the automations within the package to Pega Robot Runtime, and run the packge in your target environment.

Tip: The migration process is similar to the original deployment, with the following differences:
  • The package component is not imported from Pega Robot Studio, but from the shared repository.
  • You run the pxImportAutomationPackageFromRepo activity that imports the package component from the shared repository to Pega Robot Manager in the target environment.
Tip: If the package migration does not complete in Robot Manager, you can import the Robotic Automation package from the shared repository to Pega Robot Manager using the import wizard (ConfigureApplicationDistributionImport). After the import successfully completes, you must run the pxPostImportActionsForPackage activity.
  • Previous topic Testing configurations for the Pega Robotic Automation Importer component
  • Next topic Migrating robotic automation packages between environments

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