Table of Contents

Robotic automation package deployment and migration between environments 8.2.2

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

Scenario 1: Robotic automation package migration between environments with separate repositories

A typical use case is the initial deployment and testing of a robotic automation package in your development environment and its subsequent use in your production environment. The two environments 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
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 relays 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 a robot runtime and run it in your source environment.

Migration and publication in your target environment

To run the automation in another 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 Automation Importer to your target environment repository (Repository B) by running the pxPublishRAPToRepo 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 a robot runtime and run it in your target environment.

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

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

Scenario 2: Robotic automation package migration 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 and its subsequent use in your production environment. 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
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 a robot runtime and run it 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 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 a robot runtime and run it in your target environment.

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

  • The package component is imported not 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.
Suggest Edit

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.