Getting started with Deployment Manager

Deployment Manager is a simple, intuitive, and ready-to-use application that offers built-in DevOps capabilities to users. It leverages Pegasystems®’s market-leading case management technology to manage an automated orchestration engine, enabling you to build and run continuous integration and continuous delivery (CI/CD) pipelines in a model-driven manner.

You can run deployments involving your application updates with the click of a button, without the need for third-party automation services such as Jenkins or Bamboo. Fully automated pipelines help to significantly reduce the lead time to deliver value to end users.

Using a standardized way to deploy application changes with guardrail-related and testing-related best practices that are built into the out-of-the-box CI/CD models results in substantial operational efficiencies.

Frequently asked questions

For answers to frequently asked questions, see the Deployment Manager FAQ page.

Key features supported

Deployment Manager supports continuous integration, continuous delivery, test execution, reporting, diagnostics, manual approvals, deployment cancellations, change rollbacks, roles and privileges, and notifications.


The following video provides an overview of Deployment Manager:


On-premises users can download Deployment Manager from For information about installing Deployment Manager, see Installing or upgrading Deployment Manager.

Beginning with Pega Platform™ 7.4, Pega Cloud Services users have a dedicated instance in their virtual private cloud (VPC) at the time of onboarding with Deployment Manager functionality preinstalled.

This instance is referred to as the orchestration server and contains the “DevOps” keyword in the URL.

Upgrading to a new Deployment Manager release

On-premises users can directly download the latest release from

Pega Cloud Services users should create a support ticket to request a new release.

After you obtain the latest release, refer to the upgrade documentation for information about upgrading to the latest release. For more information, see Step 1: Installing or upgrading Deployment Manager 4.7.x.

Setting up and configuring Deployment Manager for a quick start

For details about how Deployment Manager works, see Deployment Manager architecture and workflows.

Deployment Manager is ready to use out of the box. There is no need to build on top of it; however, some initial configurations are needed before you can get started.

The following list of terms defines key Deployment Manager concepts:

  • Candidate systems – the individual environments that host the target application, typically the development, QA, staging, and production environments.
  • Repository – the artifact repository that stores the application archive as defined by a product rule.
  • DMAppAdmin – the operator ID, provided out of the box, that is used by an application pipeline to execute all the tasks such as deploying, running tests, checking guardrail scores, and so on.
  • DMReleaseAdmin – the operator ID, provided out of the box, that has administrative privileges for Deployment Manager. This is the user that you will start with for the Deployment Manager.
You should make changes only in the development environment and then move them to higher environments. Do not make changes in any other environment.

Set up and configure Deployment Manager by following these steps:

  1. Enable the DMAppAdmin and DMReleaseAdmin operators IDs:
    1. Log in to the orchestration server and enable the DMReleaseAdmin operator ID.
    2. Log in to candidate systems (development, QA, staging, and production) and enable the DMAppAdmin operator ID. Ensure that the same password is set on all environments.
    3. On the orchestration server, open the DMAppAdmin authentication profile and set the password to the DMAppAdmin operator ID password that you set in step 1b.
    4. On all candidate systems, open the DMReleaseAdmin authentication profile and set the password to the DMReleaseAdmin operator ID password that you set in step 1a.

For detailed steps, see Configuring authentication profiles on the orchestration server and candidate systems.

  1. On each candidate system, open your target application and add PegaDevOpsFoundation as a built-on application. For more information, see Configuring candidate systems.
  2. Optional: To use branches for application development, set the RMURL dynamic system setting on the development environment to be the orchestration server URL. For more information, see Configuring the development system for branch-based development (optional).
  3. Optional: For on-premises users, set up repositories for artifact archiving. For more information, see Configuring repositories on the orchestration server and candidate systems.

Deployment Manager leverages JFrog Artifactory, Amazon S3, Microsoft Azure, or file system repository types. After you configure one of these repositories, you will select one to use when you create your pipelines.

  1. Configure the product rule for your application. You will specify this product rule when you create your pipeline.
  2. Optional: To receive email notification for deployments, configure email accounts on the orchestration server. For more information, see Configuring email accounts on the orchestration server.
  3. Optional: If you are using Jenkins, configure Jenkins so that it can communicate with the orchestration server. For more information, see Configuring Jenkins.

Using Deployment Manager

After you set up and configure Deployment Manager, you can begin using it.

  1. Log in to the Deployment Manager portal on the orchestration server with the DMReleaseAdmin operator ID.
  2. Create a pipeline by modeling stages and steps and specifying environments, applications, product rules, and repositories.
  3. Run diagnostics by clicking Actions > Diagnose pipeline to verify that your pipeline is correctly configured.
  4. Run deployments directly from Deployment Manager or from development environments as you merge your branches.

For detailed information, see Using Deployment Manager 4.7.x.


When using Deployment Manager, remember these troubleshooting tips:

  • Run diagnostics and follow troubleshooting tips if your deployments fail to run.
  • Review pipeline logs that are available on the pipeline landing page and the output from diagnostics to troubleshoot your workflows.
  • Attach logs from Deployment Manager and the output from diagnostics in your support tickets.


If you experience problems using Deployment Manager, submit a support ticket in My Support Portal.

For product feedback or non-urgent questions, send an email to

    75% found this useful

    Have a question? Get answers now.

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