Configuring a business change pipeline

Archived

3 Tasks

15 mins

Pega Customer Decision Hub 8.6

Pega Deployment Manager 5.5

Visible to: All users

Beginner

Pega Customer Decision Hub 8.6

Pega Customer Decision Hub 8.7

English

Scenario

U+ Bank's content team has started working on the Business Operations Environment (BOE) to implement some business changes. They have Deployment Manager and DevOps installed in their orchestrator system and DevOps in all their candidate systems. To deploy the business-as-usual changes made in BOE, U+ Bank wants to set up a business change pipeline.

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

Role	User name	Password
ReleaseManager	ReleaseManager	install@1234

Your assignment consists of the following tasks:

Task 1: Ensure the Orchestrator URL is set

Ensure that your exercise system URL is set as the Orchestrator URL in the Deployment Manager settings.

Task 2: Create a new business change pipeline

Create a new business change pipeline to migrate business-as-usual (BAU) changes from business operations environment to development, staging, and production environments.

Task 3: Run the pipeline diagnostics

Run diagnostics to check if the orchestrator can communicate with all the candidate systems and if the provided overlay application details are correct.

 

Challenge Walkthrough

Detailed Tasks

1 Ensure the Orchestrator URL is set

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

2 Create a business change pipeline

1. In the navigation pane of Deployment Manager, click Pipelines.
   
2. On the Application Pipelines screen, click New > Business change pipeline.
   
3. In the Select the source environment for application packaging section, in the Application packaging environment field, enter http://localhost/prweb.
   Note: Typically, you add the URL of the Development environment here because it acts as the system of record and contains the product rule that defines the application package. For training purposes, the five environments that are used in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. As a result, localhost is used.

4. In the Authentication profile list, select DMAppAdmin.
   
5. In the Application details section, enter or select the following information for the overlay application.
   1. Application: BusinessChange
   2. Version: 01.01.01
   3. Access group: BusinessChange:RevisionManager
   4. Product rule: BusinessChange
   5. Version: 01-01-01
   6. Pipeline name: BusinessChange
      
6. In the Merge policy section, select New ruleset version, and then in the Password field, enter install.
   
7. Click Next.
8. In the Environments section, enter the following information.

   Environment	Environment URL	Authentication Profile
   Development	http://localhost/prweb	DMAppAdmin
   Staging	http://localhost/prweb	DMAppAdmin
   Business Operations	http://localhost/prweb	DMAppAdmin
   Production	http://localhost/prweb	DMAppAdmin

   Note: For training purpose, the five environments used in a typical enterprise are combined into a single environment that acts as the orchestrator and 4 candidate systems. Hence, localhost is used for all the environments.
   

9. In the Artifact management section, enter or select the following information:
   1. Development repository: LocalFilesystem
   2. Production repository: LocalFilesystem
      Note: Deployment Manager stores application artifacts created throughout the life cycle of deployment within a repository. Using Deployment Manager requires the use of a supported artifact repository.
      For training purposes, the challenge uses a LocalFilesystem. In a real-life implementation, you might use an S3 bucket or another storage.
      

10. Click Next to create the pipeline model.
    
11. In the Model Pipeline view, in the Development stage, click the Create application version task to view the Task details area.
    
12. In the Task details area, in the Input parameters section in the Application name field, enter PegaCRM_Marketing.
    
13. Click Create to create the pipeline.

3 Run the pipeline diagnostics

1. Click Run Diagnostics to ensure that deployments are successful.
   
   Note: Notice that four warnings are displayed while verifying the intersystem connections. These warnings tell you that the system recommends using the IP address in the environment URLs and not localhost. You can ignore these warnings as you configure all the environments in the same exercise system for training purposes.
   

2. Verify that the orchestrator can communicate with all the candidate systems and that the overlay application details provided are correct.
   
3. On upper left, click the back arrow to view the pipeline.
   

---

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

• Promoting changes with a business change pipeline v1

---

Available in the following mission:

• Deployment Manager for 1:1 Customer Engagement v2