Moving your application to production: DevOps and Pega Deployment Manager
Your Pega application will require your input and changes. For each application, you are responsible for creating role-based access controls, and then providing user IDs that implement those controls for all your customers (for more information, see Securing your application with Pega Platform Admin Studio). You can also customize your application to reflect the way your company does business, as Pega apps are “built for change.”
What is DevOps?
Pega strongly recommends that these types of changes to your application(s) not be made in a “production” or live environment that are being used by your customers. Instead, create and then test your changes in a development environment. A standard Pega Cloud Services installation generally includes a Development and Testing environment (“dev/test”) and a Staging environment, for user testing, as well as the Production environment. The best practice for customizing a Pega application is to make the changes in the dev/test environment, and do some testing there. Then move these changes into the Staging environment for full user testing. Once all the testing has been successfully completed, the changes can be moved into production.
Development Operations (“DevOps”) is a culture of collaboration by development, quality, and operations teams to address issues in their respective areas. Tools and processes are put in place so you can sustain progress and bring continued improvement to your development efforts. 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 more details on DevOps for Pega applications, please see the DevOps release pipeline overview and related documentation.
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. You will also receive administrator credentials to access the “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, please see Deployment Manager architecture and workflows.