Skip to main content
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.
LinkedIn
Copied!

Table of Contents

Configuring Deployment Manager for data migration pipelines

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 Business Operations system.

Perform the following steps:

  1. Install or upgrade to Deployment Manager 4.6.x or later.
    • For first-time installations or upgrades from Deployment Manager 3.2.1 on the candidate systems (production and Business Operations environments) and the orchestration server.

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

      For more information, see the "Installing or upgrading Deployment Manager" of the Installing, upgrading, and configuring Deployment Manager article for your Deployment Manager release, which is available at Deployment Manager.
       
    • If you are upgrading from a Deployment Manager release 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 the "Running post-upgrade steps" section of the Installing, upgrading, and configuring Deployment Manager article for your Deployment Manager release, which is available at Deployment Manager.
       
  2. For first-time installations, configure communication between the orchestration server and the candidate systems.
    1. Enable default operators on each system.
      For more information, see the "Step 3a: Configuring authentication profiles on the orchestration server and candidate systems" section of the Installing, upgrading, and configuring Deployment Manager article for your Deployment Manager release, which is available Deployment Manager.
    2. Configure the authentication profiles, which enable communication between systems, on each system.

      Configuring communication consists of enabling the default operators in each system and configuring the authentication profiles, which enables communication between systems, on each system. Deployment Manager provides default authentication profiles, or you can create your own.
       
  3. Optional: To move orchestration server to a different environment, migrate your pipelines to the new orchestration server, and then configure, on the new orchestration server, the URL of the new orchestration server. This URL is used to update the task status on the orchestration server and for diagnostics checks.

For more information, see step 2 in the "Step 3b: Configuring the orchestration server" section of the Installing, upgrading, and configuring Deployment Manager article for your Deployment Manager release, which is available at Deployment Manager..

 

Did you find this content helpful?

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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us