Configuring the orchestration server
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:
- If your system is not configured for HTTPS, verify that TLS/SSL settings are
not enabled on the api and cicd service packages.
- In the header of Dev Studio, click .
- Click api.
- On the Context tab, verify that the Requires authentication check box is checked.
- On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.
- Click .
- Click cicd.
- On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.
- 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.
- In the header of Dev Studio, click .
- In the Owning Ruleset field, enter Pega-DeploymentManager.
- In the Setting Purpose field, enter OrchestratorURL.
- Click Create and open.
- On the Settings tab, in the Value field, enter the URL of the new orchestration server in the format http://hostname:port/prweb.
- Click Save.
Previous topic Understanding default authentication profiles and operator IDs Next topic Configuring candidate systems