Skip to main content

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

Installing, upgrading, and configuring Deployment Manager 4.8.x

Updated on February 4, 2021

Use Deployment Manager to create continuous integration and delivery (CI/CD) pipelines, which automate tasks and allow you to quickly deploy high-quality software to production.

Note: You should make changes only in the development environment and then move them to higher environments. Do not make changes in any other environment.
Note: Each customer virtual private cloud (VPC) on Pega Cloud Services has a dedicated orchestrator instance to use Deployment Manager. If you are upgrading from an earlier release, contact Pegasystems Global Client Support (GCS) support to request a new version.
Note: This document describes the procedures for the latest version of Deployment Manager 4.8.x. To use notifications, you must install or upgrade to Pega 8.1.3 on the orchestration server.

For information on configuring Deployment Manager for data migration pipelines, see Installing, upgrading, and configuring Deployment Manager 4.8.x for data migration pipelines.

  • Installing or upgrading to Deployment Manager 4.8.x

    You must install Deployment Manager if you are using it on-premises. Because Pega Cloud Services manages the orchestration server in any Pega Cloud subscription, Pega Cloud Services manages the installation and upgrades of Deployment Manager orchestration servers. Deployment Manager is supported on Pega Platform versions 8.1-8.5.

  • Running post-upgrade steps

    If you are upgrading from Deployment Manager versions earlier than 3.2.1, you must run post-upgrade steps to complete the upgrade. Before you run post-upgrade steps, ensure that no deployments are running, have errors, or are paused. In Pega Cloud Services environments, the orchestration server name is similar to [environmentname]-DevOps.

  • Configuring systems in the pipeline

    Configure the orchestration server and candidates in your pipeline for all supported CI/CD workflows. If you are using branches, you must configure additional settings on the development system after you perform the required steps.

  • Configuring the development system for branch-based development

    If you are using branches in either a distributed or nondistributed branch-based environment, configure the development system so that you can start deployments when branches are merged. Configuring the development system includes defining the URL of the orchestration server, creating development and target applications, and locking application rulesets.

  • Configuring additional settings

    As part of your pipeline, users can optionally receive notifications through email when events occur. For example, users can receive emails when tasks or pipeline deployments succeed or fail. For more information about the notifications that users can receive, see .

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