Close popover

Table of Contents

Setting up and configuring Deployment Manager for a quick start

Version:

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. For details about how Deployment Manager works, see Understanding Deployment Manager architecture and workflows.

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.
  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.

  2. On each candidate system, open your target application and add PegaDevOpsFoundation as a built-on application. For more information, see Configuring candidate systems.

  3. To use branches for application development, set the RMURL dynamic system setting on the development environment to be the orchestration server URL.

  4. For on-premises users, set up repositories for artifact archiving. For more information, see Creating 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.

  5. Configure the product rule for your application.

    You will specify this product rule when you create your pipeline.

  6. To receive email notification for deployments, configure email accounts on the orchestration server.

    For more information, see Configuring email accounts on the orchestration server.

  7. If you are using Jenkins, configure Jenkins so that it can communicate with the orchestration server.

    For more information, see Configuring Jenkins.

Suggest Edit

0% found this useful

Have a question? Get answers now.

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