Skip to main content

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

Quick-start guide for Deployment Manager on Pega Cloud Services

Updated on December 13, 2021

Your Pega Cloud Services account comes with everything you need to start deploying your application to production. This guide summarizes all the steps necessary to deploy your new Pega Application to production. To request an update to the latest version, create a ticket on the Pega My Support Portal here.

Note: Determine two passwords that will be used throughout these instructions for the following operators:
  • DMReleaseAdmin
  • DMAppAmin

Configure the orchestration environment

In Pega Platform version 8.5.3 or earlier, you must continue to set up security on the orchestration environment. For more information, see Securely authenticating in Deployment ManagerIn Pega Platform version 8.5.4, you do not need to oAuth2.0 authentication.

  1. Log in to the DevOps environment as an administrator.
  2. Enable the DMReleaseAdmin operator and set the password.
  3. Enable the DMAgentUser operator.
  4. Open the DMAppAdmin authentication profile and set the password.
  5. Log in as DMReleaseAdmin.
  6. Optional: Perform the following steps if you require connection to any external systems, such as Jenkins:
    1. Click Generate client secret.
    2. Download the secret.
    3. Click Update authentication profiles.
    4. Upload the JKS keystore on DMKeyStore rule. For information on keystore and truststore setup, see Securely authenticating in Deployment Manager.

Configure the candidate environments

  1. Log in to each candidate environment as an administrator.
    • For the default Pega Cloud deployment, this will be dt1, stg, and prd.
  2. Enable the DMAppAdmin operator and set the password.
  3. If the candidate system is between Pega Platform 8.1 and Pega Platform 8.5.1, the candidate must have 4.8.4 Pega DevOps Foundation. If candidates are managed by an orchestrator on version 5 or later, you must create the PegaDevopsShared configuration and set the value to True. If not set, the candidate will fall back to using the older 4.x APIs for interactions with Deployment Manager and the pipelines will not be functional if using a 5.x orchestrator. Having the configuration created and set to true will ensure the candidates would leverage the 5.x API service.
    • Owning ruleset: PegaDevopsShared
    • Purpose: deploymentmanager/orchestrator/managed_by_5x/enabled
    • Value: True

See Setting up candidate environments for more information on configuring the candidate environments.

Configure the development environment

  1. Log in to the dt1 environment as an administrator.
  2. Open the application record with which you want to manage with a Deployment Manager pipeline, and set PegaDevOpsFoundation version 5 as a built-on application
  3. Optional: If you have multiple orchestrator servers and the development server needs pointing to a secondary orchestrator server, configure the orchestratorURL dynamic system settings.

See Setting up candidate environments for more information on configuring the candidate environments.

Configure the application

  1. The application that is being promoted by a Deployment Manager pipeline should be built-on the latest version of the PegaDevOpsFoundation application.

See Configuring an application for more information on configuring the candidate environments.

Create your first pipelines

  1. Log in to the devops environment as DMReleaseAdmin.
  2. Click New in the top-right corner and choose Deployment pipeline.
  3. On the first screen, enter the following information as it applies to your application:
    1. Application name and version
    2. Access group
    3. Product name and version that defines your entire application.
    4. Pipeline name
  4. Click Create to create the pipeline.

See Creating pipelines for more information on creating pipelines.

Test and execute the pipeline

  1. In the top right corner of the rule form, in the action menu, diagnose the pipeline to ensure your set up is valid.
  2. Click Start deployment to move your newly updated application through the pipeline.
    Note: This active deployment promotes changes from development to higher environments, as defined in the pipeline.

You are now ready to learn more about customizing Deployment Manager pipelines.

  • Previous topic Installing or updating Deployment Manager 5
  • Next topic Quick-start guide for Deployment Manager on-premises and client-managed cloud

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