Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring Deployment Manager 4.x for Pega Platform 7.4

Suggest edit Updated on September 10, 2021

You can use Deployment Manager 4.x if Pega Platform™ 7.4 is installed on your candidate systems (development, QA, staging, and production). You can use many of the latest features that were introduced in Deployment Manager 4.x; for example, you can:

For information about key new features in Deployment Manager 4.x, see DevOps and Automated Testing.

Deployment Manager 4.x and Pega 7.4 feature support

Note the following usage restrictions:

  • This configuration does not support the following pipeline features:
    • Pipeline tasks:
      • Validate test coverage
      • Refresh application quality
      • Run Pega scenario tests
      • Enable test coverage
    • Enhancements to the Merge Branches wizard:
      • Associating user stories and bugs with a branch
      • Locked branches
      • Merging branches that span application layers
  • In Deployment Manager 4.5.x, some of the repository diagnostics do not work for candidate systems that are running Pega 7.4. These diagnostics work in Deployment Manager 4.6.x.

Configuring Deployment Manager 4.x to work with Pega 7.4

  1. On the orchestration system, install or upgrade to the latest version of Pega Platform.
  2. On the orchestration system, install or upgrade to the latest version of Deployment Manager 4.x.

    For more information, see Installing, upgrading, and configuring Deployment Manager 4.7.x.

     
  3. For candidate systems with Deployment Manager 3.4.1 installed, go to step 4.

    Otherwise, do one of the following actions:
    • For candidate systems with Deployment Manager 3.1.x - 3.3.x, upgrade to Deployment Manager 3.4.1.

      For more information, see Step 2:Upgrading to Deployment Manager 3.4.x.

       
    • For candidate systems without Deployment Manager, do the following actions:
      1. Install and configure the latest version of Deployment Manager 4.x on the candidate systems.

        For more information, see Installing, upgrading, and configuring Deployment Manager 4.7.x.

         
      2. Add PegaDevOpsFoundation 3.4.1 to your application stack by first extracting the DeploymentManager_03.04.01.zip file from the DeploymentManager04.07.0x.zip file.
      3. Use the Import wizard to import the PegaDevOpsFoundation_4.zip file.

        For more information about the Import wizard, see Importing rules and data from a product rule by using the Import wizard.
         
      4. In the Dev Studio header of Pega Platform, click the name of your application, and then click Definition.
      5. In the Built on application section, click Add application.
      6. In the Name field, press the Down arrow key and select PegaDevOpsFoundation.
      7. In the Version field, press the Down arrow key and 3.4.1.
      8. Click Save.
  4. Create and configure an application pipeline.

    For more information, see Configuring an application pipeline.
     
  5. Run diagnostics to ensure that your pipeline is configured correctly.

    For more information, see Diagnosing a pipeline.

Upgrading to Deployment Manager 3.4.x

Before you upgrade, ensure that no deployments are running, have errors, or are paused.

To upgrade to Deployment Manager 3.4.x either on Pega Cloud or on premises, perform the following steps:

  1. Enable default operators and configure authentication profiles on the orchestration server and candidate systems. For more information, see Step 3a: Configuring authentication profiles on the orchestration server and candidate systems.
  2. On each candidate system, add the PegaDevOpsFoundation application to your application stack.
    1. In the Designer Studio header, click the name of your application, and then click Definition.
    2. In the Built on application section, click Add application.
    3. In the Name field, press the Down Arrow key and select PegaDevOpsFoundation.
    4. In the Version field, press the Down Arrow key and select the version of Deployment Manager that you are using.
    5. Click Save.
Note:
Note:
If you are upgrading from Deployment Manager 3.2.1, you do not need to do the rest of the steps in this procedure or the required steps in the remainder of this document. If you are upgrading from earlier releases and have pipelines configured, complete this procedure.
  1. On the orchestration server, log in to the release management application.
  2. In Designer Studio, search for pxUpdatePipeline, and then click the activity in the dialog box that displays the results.
  3. Click Actions > Run.
  4. In the dialog box that is displayed, click Run.
  5. Modify the current release management application so that it is built on PegaDeploymentManager:03-04-01.
    1. In the Designer Studio header, click the name of your application, and then click Definition.
    2. In the Edit Application rule form, on the Definitiontab, in the Built on application section, for the PegaDeploymentManager application, press the Down Arrow key and select 03.04.01.
    3. Click Save.
  6. Merge rulesets to the PipelineData ruleset.
    1. Click Designer Studio > System > Refactor > Rulesets.
    2. Click Copy/Merge RuleSet.
    3. Click the Merge Source RuleSet(s) to Target RuleSet radio button.
    4. Click the RuleSet Versions radio button.
    5. In the Available Source Ruleset(s) section, select the first open ruleset version that appears in the list, and then click the Move icon.
Note:
Note:
All your current pipelines are stored in the first open ruleset. If you modified this ruleset after you created the application, select all the ruleset versions that contain pipeline data.
  1. In the target RuleSet/Information section, in the Name field, press the Down Arrow key and select Pipeline Data.
  2. In the Version field, enter 01-01-01.
  3. For the Delete Source RuleSet(s) upon completion of merge? option, click No.
  4. Click Next.
  5. Click Merge to merge your pipelines to the PipelineData:01-01-01 rulset.
  6. Click Done.
  7. Your pipelines are migrated to the Pega Deployment Manager application. Log out of the orchestration server and log back in to it with the DMReleaseAdmin operator ID and the password that you specified for it.

For backup purposes, pipelines are still visible in your previous release management application. However, you should not create deployments with this application, because deployments might not work correctly.

Configuring authentication profiles on the orchestration server and candidate systems

When you install Deployment Manager on all the systems in your pipeline, default applications, operator IDs, and authentication profiles that communicate between the orchestration server and candidate systems are also installed.

On the orchestration server, the following items are installed:

  • The Pega Deployment Manager application.
  • The DMReleaseAdmin operator ID, which release managers use to log in to the Pega Deployment Manager application. You must enable this operator ID and specify its password.
  • The DMAppAdmin authentication profile. You must update this authentication profile to use the password that you specified for the DMAppAdmin operator ID, which is configured on all the candidate systems.

On all the candidate systems, the following items are installed:

  • The PegaDevOpsFoundation application.
  • The DMAppAdmin operator ID, which points to the PegaDevOpsFoundation application. You must enable this operator ID and specify its password.
  • The DMReleaseAdmin authentication profile. You must update this authentication profile to use the password that you specified for the DMReleaseAdmin operator ID, which is configured on the orchestration server.

The DMReleaseAdmin and DMAppAdmin operator IDs do not have default passwords.

Configure the default authentication profile by doing these steps:

  1. On the orchestration server, enable the DMReleaseAdmin operator ID and specify its password.
    1. Log in to the orchestration server with administrator@pega.com/install.
    2. In Designer Studio, click Records > Organization > Operator ID, and then click DMReleaseAdmin.
    3. In the Designer Studio header, click the operator ID initials, and then click Operator.
    4. On the Edit Operator ID rule form, click the Security tab.
    5. Clear the Disable Operator check box.
    6. Click Save.
    7. Click Update password.
    8. In the Change Operator ID Password dialog box, enter a password, reenter it to confirm it, and then click Submit.
    9. Optional: Clear the Force password change on next login check box if you do not want to change the password for the DMReleaseAdmin operator ID the next time that you log in.
    10. Log out of the orchestration server.
  2. On each candidate system, update the DMReleaseAdmin authentication profile to use the new password. All candidate systems use this authentication profile to communicate with the orchestration server about the status of the tasks in the pipeline.
    1. Log in to each candidate system with the DMAppAdmin user name and the password that you specified.
    2. Click Records > Security > Authentication Profile.
    3. Click DMReleaseAdmin.
    4. On the Edit Authentication Profile rule form, click Set password.
    5. In the Password dialog box, enter the password, and then click Submit.
    6. Save the rule form.
  3. On each candidate system, which includes the development, QA, staging, and production systems, enable the DMAppAdmin operator ID. If you want to create your own operator IDs, ensure that they point to the PegaDevOpsFoundation application.
    1. Log in to each candidate system with administrator@pega.com/install.
    2. In Designer Studio, click Records > Organization > Operator ID, and then click DMAppAdmin.
    3. In the Designer Studio header, click the operator ID initials, and then click Operator.
    4. On the Edit Operator ID rule form, click the Security tab.
    5. Clear the Disable Operator check box.
    6. Click Save.
    7. Click Update password.
    8. In the Change Operator ID Password dialog box, enter a password, reenter it to confirm it, and then click Submit.
    9. Optional: Clear the Force password change on next login check box if you do not want to change the password for the DMAppAdmin operator ID the next time that you log in.
    10. Log out of each candidate system.
  4. On the orchestration server, modify the DMAppAdmin authentication profile to use the new password. The orchestration server uses this authentication profile to communicate with candidate systems so that it can run tasks in the pipeline.
    1. Log in to the orchestration server with the DMAppAdmin user name and the password that you specified.
    2. Click Records > Security > Authentication Profile.
    3. Click DMAppAdmin.
    4. On the Edit Authentication Profile rule form, click Set password.
    5. In the Password dialog box, enter the password, and then click Submit.
    6. Save the rule form.
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