To fully leverage the React-based Constellation UI in Pega Platform 8.8 and above, it is essential to configure your environment with the appropriate Constellation services. This guide provides a detailed overview of each service, deployment considerations, and the necessary Dynamic System Settings (DSS) configurations to ensure seamless integration.

Starting in Pega 8.8, Pega infinity and above, Pega provides three Constellation services:

1. Constellation Pega Static Service

Purpose:

Delivers Pega-engineered JavaScript content essential for the Constellation UI. This service is mandatory for utilizing Constellation UI in Pega Platform deployments.

Pega Static is JavaScript static content generated by Pega engineers. It takes the UI metadata and Case values and builds the presentation on the client while managing interactions between the browser and the Case engine. It uses the Pega Digital Experience (DX) API version 2 and provides the same static content for all customers.

Pega provisions Pega Static over a Content Delivery Network (CDN). The Pega CDN has regional caches to ensure fast content delivery worldwide and supports HTTP/1 and HTTP/2 protocols.

Deployment Options:

• Default (Recommended): Utilize Pega’s Content Delivery Network (CDN) for effortless integration.
• Air-Gapped Environments: If your deployment is isolated from the internet, host the Pega Static Service within your infrastructure.

DSS Configuration:

• Setting Name: ConstellationPegaStaticURL
• Value: URL of the CDN or your internal service, e.g., https://release.constellation.pega.io

Note: Configuring this service is mandatory for basic Constellation UI functionalities.

2. Constellation Application Static (AppStatic) Service

Purpose:

Manages custom UI assets such as images, components, and localizations created by your team.

Deployment Considerations:

• Pega Cloud Deployments: Automatically configured to reference a regional instance, ensuring data residency compliance. No additional action is required.
• Client-Managed Environments (VM-based or Containerized): Deploy the AppStatic Service once per organization using the Docker image provided by Pega. This single deployment supports all Pega Platform instances within your organization.

DSS Configuration:

• Setting Name: ConstellationSvcURL
• Value:
  • For Pega Cloud-based apps: https://community.constellation.pega.io/c11n-appstatic
  • For other servers: https://HOSTNAME/constellation-appstatic

Note: This service is optional but necessary if your applications utilize custom UI assets.

3. Constellation Messaging Service

Purpose:

Facilitates real-time UI updates by pushing changes to the Constellation UI, ensuring users receive the most current information without manual refreshes.

Deployment Considerations:

• Pega Cloud Deployments: Automatically configured to reference a regional instance, ensuring data residency compliance. No additional action is required.
• Client-Managed Environments (VM-based or Containerized): Deploy the Messaging Service once per organization using the Docker image provided by Pega. This single deployment supports all Pega Platform instances within your organization.

DSS Configuration:

• Setting Name: ConstellationMessageSvcHostPath
• Value: URL of your deployed Messaging Service

Note: This service is optional but recommended for applications that benefit from immediate UI updates.

Deployment Summary

Key Takeaways:

• For foundational Constellation UI capabilities, the Pega Static Service is essential.
• Incorporate the Application Static Service when your applications require custom UI elements.
• Implement the Messaging Service to enable real-time UI updates, enhancing user experience.

By thoughtfully configuring these services and their corresponding DSS settings, you can optimize your Pega Platform environment to fully harness the power of the Constellation UI.