Configuring candidate systems
Configure each system that is used for the development, QA, staging, and production stage in the pipeline.
Do the following steps:
- On each candidate system, add the PegaDevOpsFoundation application to your
application stack.
- In the Designer Studio header, click the name of your application, and then click Definition.
- In the Built on application section, click Add application.
- In the Name field, press the Down arrow key and select PegaDevOpsFoundation.
- In the Version field, press the Down arrow key and select the version of Deployment Manager that you are using.
- Click Save.
- If your system is not configured for HTTPS, verify that TLS/SSL settings are
not enabled on the api and cicd service packages.
- Click .
- Click api.
- On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.
- Click RecordsIntegration-ResourcesService Package.
- Click cicd.
- On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.
- To use a product rule for your target application, test
application, or both, other than the default rules that are created by the New
Application wizard, on the development system, create product rules that define
the test application package and the target application package that will be
moved through repositories in the pipeline.
For more information, see Product rules: Completing the Create, Save As, or Specialization form.
When you use the New Application wizard, a default product rule is created that has the same name as your application. - Configure repositories through which to move artifacts in your pipeline. For more information, see Configuring repositories on the orchestration server and candidate systems.
Previous topic Configuring the orchestration server Next topic Configuring repositories on the orchestration server and candidate systems