Skip to main content

Exercise setup - Orchestrator configuration

2 Tasks

30 mins

Visible to: All users
Intermediate
Pega Customer Decision Hub 8.8
Next Best Action
English
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Scenario

To ensure that the development environment can communicate with the Business Operations environment, you must update the environment URLs.

Caution: This step is necessary to complete this assignment.

 

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 Business Operations environment details

Caution: All the following steps must be completed in the Business Operations environment:
  1. Start the Business Operations environment.
  2. Log in to Dev Studio as the system administrator by entering the following credentials:
    1. In the User name field, enter SystemAdmin.
    2. In the Password field, enter rules.
  3. In the navigation pane of Dev Studio, click Records > SysAdmin > Dynamic System Settings to update the OrchestratorURL.
  4. Update the OrchestratorURL in the Business Operations environment with the Development environment URL.
    Update the development environment URL

2 Development environment details

Caution: All the following steps must be completed in the Development environment:
  1. Start the Development environment.
  2. Log in to Deployment Manager as the deployment manager release administrator by entering the following credentials:
    1. In the User name field, enter DMReleaseAdmin.
    2. In the Password field, enter rules.
  3. On the Application Pipelines page, perform the following steps:
    1. Click Initial Migration to modify the pipeline configurations.
      Initial Migration Pipeline
    2. In the upper-right corner, click Actions > Edit pipeline.
      Edit Pipeline settings
    3. On the Pipeline model tab, click the Business Operations stage.
      InitialMigrationPipeline Business Operations stage
    4. In the Stage details section, update the Environment URL with the URL of the Business Operations environment. (For example: https://pega.XXXXXXXXXX.pegaenablement.com/prweb)
      UpdateURLforBusinessOperations
    5. In the upper-right corner, click Save.
    6. Click the Run Diagnostics to confirm the communication between the Development and the Business Operations environment is established.
  4. In the navigation pane of Deployment Manager, click Pipelines to return to the Application Pipelines page.
  5. On the Application Pipelines page, click Continuous Enterprise Changes to modify the pipeline configurations.
    1. Repeat steps 3.b - 3.f to update the Continuous Enterprise Changes pipeline with the environment details of the Business Operations environment.
  6. In the navigation pane of Deployment Manager, click Pipelines to return to the Application Pipelines page.
  7. On the Application Pipelines page, modify the Standard Release pipeline:
    1. Click Standard Release to modify the pipeline configurations.
    2. Follow steps 3.b - 3.f to update the Standard Release pipeline with the environment details of the Business Operations environment.
      Environment URLs for Standard release pipeline
  8. In the navigation pane of Deployment Manager, click Pipelines to return to the Application Pipelines page.
  9. On the Application Pipelines page, modify the Fast-Release pipeline:
    1. Click Fast Release to modify the pipeline configurations.
    2. Repeat steps 3.b - 3.f to update the Fast Release pipeline with the environment details of the Business Operations environment.


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