LinkedIn
Copied!

Table of Contents

Upgrading to Deployment Manager 3.4.x

Version:

Only available versions of this content are shown in the dropdown

After you install Deployment Manager 3.4.x, you must do post-upgrade steps. 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 Services 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 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.

    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.

    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 configuration steps. If you are upgrading from earlier releases and have pipelines configured, complete this procedure.
  3. On the orchestration server, log in to the release management application.

  4. In Designer Studio, search for pxUpdatePipeline, and then click the activity in the dialog box that displays the results.

  5. Click Actions Run .

  6. In the dialog box that is displayed, click Run.

  7. 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 Definition tab, in the Built on application section, for the PegaDeploymentManager application, press the Down arrow key and select 03.04.01.

    3. Click Save.

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

      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.
  9. In the target RuleSet/Information section, in the Name field, press the Down arrow key and select Pipeline Data.

  10. In the Version field, enter 01-01-01.

  11. For the Delete Source RuleSet(s) upon completion of merge? option, click No.

  12. Click Next.

  13. Click Merge to merge your pipelines to the PipelineData:01-01-01 ruleset.

  14. Click Done.

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.
You do not need to perform any of the required configuration procedures.

Have a question? Get answers now.

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