Skip to main content

Configuring Deployment Manager for data migration pipelines

Suggest edit
Updated on March 25, 2022

Use Deployment Manager to configure and run continuous integration and delivery (CI/CD) workflows for your Pega applications from within Pega Platform. You can create a standardized deployment process so that you can deploy predictable, high-quality releases without using third-party tools.

With Deployment Manager, you can fully automate your CI/CD workflows, including branch merging, application package generation, artifact management, and package promotion to different stages in the workflow. You can download Deployment Manager for Pega Platform from the Deployment Manager Pega Marketplace page.

Pega Customer Decision Hub
Before you begin: Learn about the architecture of a Pega Customer Decision Hub system, to which you want to add Deployment Manager. For more information, see Deployment architecture for Pega Customer Decision Hub. 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 environment.
  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 Using Deployment Manager for model-driven DevOps

    • If you are upgrading from a Deployment Manager release earlier than 3.2.1, do post-upgrade steps.

      For more information, see Using Deployment Manager for model-driven DevOps

  2. For first-time installations, configure communication between the orchestration server and the candidate systems.
    1. Enable 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.
  3. Optional: To move the 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 Using Deployment Manager for model-driven DevOps and Deployment Manager FAQ page.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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