Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring candidate systems

Updated on February 4, 2021

Configure each system that is used for the development, QA, staging, and production stage in the pipeline.

To configure candidate systems, complete the following steps:
  1. On each candidate system, add the PegaDevOpsFoundation application to your application stack.
    1. In the header of Dev Studio, click the name of your application, and then click Definition.
    2. In the Built on application section, click Add application.
    3. In the Name field, press the Down arrow key and select PegaDevOpsFoundation.
    4. In the Version field, press the Down arrow key and select the version of Deployment Manager that you are using.
    5. Click Save.
  2. If your system is not configured for HTTPS, verify that TLS/SSL settings are not enabled on the api and cicd service packages.
    1. Click RecordsIntegration-ResourcesService Package.
    2. Click api.
    3. On the Context tab, verify that the Requires authentication check box is checked.
    4. On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.
    5. Click RecordsIntegration-ResourcesService Package.
    6. Click cicd.
    7. On the Context tab, verify that the Require TLS/SSL for REST services in this package check box is cleared.
  3. 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 Creating a product rule that includes associated data.

    When you use the New Application wizard, a default product rule for your target application is created that has the same name as your application. Additionally, if you are using a test application, a product rule is created with the same name as the target application, with _Tests appended to the name.

  4. If you are on Pega Platform 8.1 to Pega Platform 8.5.1 and you are setting up the candidate with 4.8.4 Pega DevOps Foundation. Please proceed with the steps below is the target environment is SSL-enabled with private certificates, configure the Deployment Manager connectors such that they can receive and process tokens by setting the KeyStore; For more information, see Creating a keystore for application data encryption.
    1. Configure the PegaDeploymentManagerIntegration/TrustStore dynamic system setting to reference the keystore ID by clicking RecordsSysAdminDynamic System Settings.
    2. In the Value field, enter the ID of the keystore that you created in the previous step.
    3. Click Save.
What to do next: Configure repositories through which to move artifacts in your pipeline. For more information, see Creating repositories on the orchestration server and candidate systems
  • Previous topic Configuring the orchestration server
  • Next topic Creating repositories on the orchestration server and candidate systems

Tags

Pega Platform 8.5 DevOps

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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