Skip to main content

Moving your application to production: DevOps and Pega Deployment Manager

Suggest edit Updated on January 24, 2022

To integrate your application into a DevOps pipeline, Pega provides Deployment Manager to help you promote changes to your Pega application across your various Pega Cloud services environments.

What is DevOps?

Pega strongly recommends that you test your changes in non-production environments before pushing them to your production environment that your customers are using. To do so, you create and then test your changes in a development environment. A typical Pega Cloud client subscription includes the following environments:

  • Development and Testing environment (DevTest)
  • Staging environment, for user testing
  • Production environment

After you complete your change validation testing in your DevTest and Staging environments use your pipeline to push the changes into your production environment.

Pega designed flexibility in Pega Deployment Manager in order to support the use of most organization’s DevOps practices such as continuous integration and continuous delivery (CI/CD) pipelines. For details on DevOps for Pega applications, see DevOps release pipeline overview and related.

Deployment Manager

In order to make it easier for your DevOps engineers to accomplish these moves, Pega recommends Deployment Manager. Deployment Manager is a simple, ready-to-use Pega application that offers built-in DevOps capabilities to users. It leverages the Pegasystems case management technology to manage an automated orchestration engine, enabling you to efficiently build and run your CICD pipelines.

You may have a robust DevOps program already established in your company, and may be using tools such as Jenkins or Bamboo. Those products may be used with Deployment Manager. In addition, Deployment Manager allows you to run deployments of your application updates or other changes with the click of a button, without the need for third-party automation services such as Jenkins or Bamboo. As part of near-zero downtime upgrades, fully automated pipelines help to significantly reduce the lead time to deliver value to end users.

If your subscription includes Deployment Manager, your “welcome” email will contain the URL for your Deployment Manager “orchestration” environment and your administrator credentials to access your “devops” environment. Then follow the instructions in Getting Started with Deployment Manager for Setting up and configuring Deployment Manager for a quick start.

For detailed steps for setting up the operator IDs, see Step 3a: Configuring authentication profiles on the orchestration server and candidate systems in Installing, upgrading, and configuring Deployment Manager.

For an overview of the Deployment Manager functionality, see Deployment Manager architecture and workflows.

Design Patterns: For a prescriptive, Pega-recommended approach for managing your Pega application releases using Deployment Manager pipelines, see The Prescriptive Application Release Life Cycle.
Design Patterns: For an overview of the requirement for establishing prescriptive Routes to Live (RTL) for your Pega applications deployed in Pega Cloud, see Establishing a prescriptive Route to Live.
Did you find this content helpful? YesNo

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

Close Deprecation Notice
Contact us