Skip to main content

 –

Configuring the orchestration server

Suggest edit Updated on July 6, 2020

The orchestration server is the system on which the Deployment Manager application is installed and release managers configure and manage CI/CD pipelines. Configure settings on it before you can use it in your pipeline.

To configure the orchestration server, do the following steps:

  1. If your system is not configured for HTTPS, verify that TLS/SSL settings are not enabled on the api and cicd service packages.

    1. In the header of Dev Studio, click RecordsIntegration-ResourcesService Package.

    2. Click api.

    3. On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.

    4. Click RecordsIntegration-ResourcesService Package.

    5. Click cicd.

    6. On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.

  2. To move the orchestration server to a different environment, first migrate your pipelines to the new orchestration server, and then configure its URL on the new orchestration server.

    This URL will be used for callbacks and for diagnostics checks.

    1. In the header of Dev Studio, click CreateSysAdminDynamic System Settings.

    2. In the Owning Ruleset field, enter Pega-DeploymentManager.

    3. In the Setting Purpose field, enter OrchestratorURL.

    4. Click Create and open.

    5. On the Settings tab, in the Value field, enter the URL of the new orchestration server in the format http://hostname:port/prweb.

    6. Click Save.

Configure the candidate systems in your pipeline. For more information, see Configuring candidate systems.
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