Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring Deployment Manager 4.6.x for data migration pipelines

Updated on September 10, 2021

You can use Deployment Manager 4.6.x or later in data migration pipelines so that you can automatically export simulation data from a production system and import it into a simulation system.

For more information about using Deployment Manager 4.6.x with data migration pipelines, see Automatically exporting and importing simulation data with Deployment Manager 4.6.x.

To install, upgrade, and configure Deployment Manager on the simulation and production environments and on the orchestration server, perform the following steps:

  1. Install or upgrade Deployment Manager.
    • For first-time installations or upgrades from Deployment Manager 3.2.1, Deployment Manager on the candidate systems (production and simulation environments) and the orchestration server.

      Upgrading is done automatically, and you do not need to do post-upgrade steps.

      For more information, see Step 1:Installing Deployment Manager.
    • For upgrades from Deployment Manager releases earlier than 3.2.1, do post-upgrade steps.

      You do not need to do post-upgrade steps if you are upgrading from version 3.2.1 or later.

      For more information, see Step 2: Running post-upgrade steps.
  2. For first-time installations, configure communication between the orchestration server and the candidate systems:
    1. Enable the default operators on each system.
    2. Configure the authentication profiles, which enable communication between systems, on each system.

      Deployment Manager provides default authentication profiles, or you can create your own.

For more information, see Step 3a: Configuring authentication profiles on the orchestration server and candidate systems.

  1. Optional: To move the orchestration server to a different environment, migrate your pipelines to the new orchestration server, and then, on the new orchestration server, configure the URL of the new orchestration server. This URL is used to update the task status on the orchestration server and diagnostics checks.

For more information, see step 2 in Step 3b: Configuring the orchestration server.


Pega Platform 8.3 - 8.7 Cloud DevOps Decision Management

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us