Skip to main content

Challenge

Creating an enterprise change pipeline

3 Tasks

10 mins

Pega Customer Decision Hub 8.7
Visible to all users
Beginner Pega Customer Decision Hub 8.7 English

Scenario

The development team at U+ Bank team worked on core application changes to meet project requirements. As they completed the initial development phase and unit-tested the changes in the development environment, they want to configure Deployment Manager to deploy the initial changes of the core application from the development environment to the higher environments.

The application has a guardrail score of 85%, contains test rulesets and branches, and the test coverage stands at 75%.

Use the following credentials to log in to the exercise system:

Role User name Password
ReleaseManager ReleaseManager rules

Your assignment consists of the following tasks:

Task 1: Verify the Orchestrator URL

Ensure that your exercise system URL is the orchestrator URL in the Deployment Manager settings.

Note: The URL is automatically updated for you.

Task 2: Create an enterprise change pipeline

Create a new enterprise change pipeline to deploy core application changes from the development environment to the higher environments.

Note: For training purposes, the five production environments that you use in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. As a result, the training system uses Localhost. However, in real-life implementations, you provide the URLs of the five environments.

Task 3: Run the pipeline diagnostics

Run diagnostics to check that the orchestrator can communicate with the development, staging, Business Operations Environment (BOE), and production systems and that the provided overlay application details are correct.

Note: When the pipeline verifies the intersystem connections, a warning is displayed that recommends you use the IP address in the environment URLs instead of the Localhost system. You can ignore the warning as you configure all the environments in the same exercise system for training purposes.

 

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 Verify the Orchestrator URL

  1. On the exercise system landing page, click Pega CRM suite to log in to Deployment Manager.
  2. Log in as the Release Manager with username ReleaseManager and password rules.
  3. In the navigation pane of Deployment Manager, click Settings > General settings to ensure that the Orchestrator URL field is set to your exercise system URL.
    The orchestrator URL in the general settings of Deployment Manager
    Note: The URL is environment-specific and automatically updates for you.

2 Create an enterprise change pipeline

  1. In the upper-right corner of the Deployment Manager landing page, click New > Deployment pipeline to open the Application Details page.
  2. In the Select the source environment for application packaging section, in the Application packaging environment field, enter https://env-xxxx.pegaenablement.com/prweb.
  3. Replace XXXX with the value that is specific to your exercise environment by copying value from the URL that is displayed in your browser.
    Source environment URL and authentication profile details
    Note: Typically, you add the URL of the development environment because it acts as the system of record and contains the product rule that defines the application package. For training purposes, the five production environments that you use in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. As a result, the training system uses Localhost.
  1. In the Authentication profile list, select DMAppAdmin.
  2. In the Application details section, add the details for the overlay application:
    1. In the Application field, enter OpsMgr.
    2. In the Version field, enter 01.01.01.
    3. In the Access group field, enter OpsMgr:RevisionManager.
    4. In the Product rule field, enter InflectionPoint.
    5. In the Version field, enter 01-01-01.
    6. In the Pipeline name field, enter InitialDeployment.
      Deployment pipeline application details
  3. Click Next to open the Environment Details page.
  4. In the Environments section, in the Stage Name column, update the environment names:
    1. In the Quality Assurance cell, enter Staging.
    2. In the Staging cell, enter Business Operations.
  5. Enter the enter the URLs and authentication profiles of the environments for each of the stages:
    Stage Name Actions

    Development

    1. In the Environment URL field, enter https://env-xxxx.pegaenablement.com/prweb.
    2. In the Authentication Profile field, enter or select DMAppAdmin.

    Staging

    1. In the Environment URL field, enter http://localhost/prweb.
    2. In the Authentication Profile field, enter or select DMAppAdmin.

    Business Operations

    1. In the Environment URL field, enter http://localhost/prweb.
    2. In the Authentication Profile field, enter or select DMAppAdmin.

    Production

    1. In the Environment URL field, enter http://localhost/prweb.
    2. In the Authentication Profile field, enter or select DMAppAdmin.
    Note: For training purposes, the five production environments that you use in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. The training system uses Localhost for all the environments except development.
    Enterprise change pipeline environment details
  1. In the Artifact management section, modify the repositories:
    1. In the Development repository field, enter or select DMRepo.
    2. Production repository field, enter or select DMRepo
      Note: Deployment Manager stores application artifacts that are created throughout the life cycle of deployment in a repository. Deployment Manager requires the use of a supported artifact repository.
      For training purposes, the challenge uses DMRepo repository. In a real-life implementation, you might use an S3 bucket or another storage source.
      Missing media item.
  1. Click Next to open the Model Pipeline page.
    Enterprise change pipeline model
  2. In the pipeline model, modify the deployment process:
    1. In the Development stage, click the Check application compliance step.
    2. In the Task details pane, in the Input parameters section, clear the following checkboxes:
      • Validate if test rulesets exist
      • Validate application branches
        Development environment application compliance input parameters

        Clearing the Validate if test rulesets exists and Validate application branches checkboxes ensures that the application package includes the existing test rulesets and the application branches.
    3. In the Staging stage, click the Check guardrail compliance step.
    4. In the Task details pane, in the Input parameters section, in the Threshold guardrail score field, enter 80.
      Staging environment guardrail threshold score

      As the U+ Bank application compliance score is 85, lowering the guardrail score threshold will ensure the task is completed successfully.
    5. In the Staging stage, click the Validate test coverage step.
    6. In the Task details pane, in the Input parameters section, in the Application test coverage %, Data type test coverage %, and Case type test coverage % fields, enter 72.
      Staging environment test coverage percentage

      As the U+ Bank application has a 72% test coverage, you modify the validate test coverage % to match the application test coverage to ensures that the task completes successfully.
    7. In the Business Operations stage, click the Check guardrail compliance step.
      Business Operations environment guardrail threshold score

      As the U+ Bank application compliance score is 85, you lower the guardrail score threshold to ensure that the task completes successfully.
    8. In the Task details pane, in the Input parameters section, in the Threshold guardrail score field, enter 80.
  3. Click Create to create the pipeline.

3 Run the pipeline diagnostics

  1. In the deployment pipeline, click Run Diagnostics to ensure that the pipeline is configured successfully and the Orchestrator can communicate with the candidate environments.
    Pipeline diagnostics to check the pipeline configuration
    Note: When the pipeline verifies the intersystem connections, a warning is displayed that recommends you use the IP address in the environment URLs instead of the Localhost system. You can ignore the warning as you configure all the environments in the same exercise system for training purposes.
  1. Verify that the orchestrator can communicate with all the candidate systems and that the overlay application details are correct, as shown in the following figure:
    Pipeline diagnostics check
  2. In the upper-left corner, click the back arrow to view the pipeline.
    Enterprise change pipeline ready for deployment
    Note: In standard use cases, clicking Start deployment initiates the initial deployment and moves the application package from the development environment to higher environments. However, for training purposes, you do not initiate the initial deployment process because all your environments are in a single exercise system.

This Challenge is to practice what you learned in the following Module:


Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice