Overview of Multi-application stack setup

When implementing Digital Messaging across multiple applications within a single Pega environment, organizations must carefully configure their application stack to ensure that each application can independently use messaging features without interference. This feature addresses a critical limitation of the previous single-application constraint.

The most fundamental requirement for multi-application Digital Messaging implementations is credential isolation. Each application must use its own unique set of Digital Messaging credentials, consisting of a unique Manager ID and Manager Key combination. Reusing these credentials across multiple applications will result in Routing Service failures and Channel connection errors, effectively breaking the messaging functionality across your environment.

The requirement for credential isolation stems from how the Digital Messaging infrastructure manages routing services and channel connections. When multiple applications share the same credentials, the system cannot properly isolate routing decisions and channel states. This leads to conflicts that prevent messages from being delivered correctly, as shown in the following figure:

Recommendations for different application stack scenarios and how to configure them, so that the applications that are specific to different countries can all use Digital Messaging, include:

Scenario 1: The existing application stack already works for Digital Messaging. If your business operates in multiple regions, each region should get its own independent copy of the same stack.

This ensures that each region can have its own Digital Messaging credentials (Manager ID + Manager Key), avoiding routing conflicts.

Scenario 2: The core application stack is stable and already works well with Digital Messaging. Even if different regions (countries, markets, business units) need small variations, you do not customize or modify the base stack for each region.

Instead, you make a copy of the entire application stack for Region A and make another independent copy for Region B. Each region then applies its own configuration, especially Digital Messaging credentials, on its own copy.      

Scenario 3: The existing application stack is already stable, so you do not need to modify or customize it for each region.

In the new application stack, the Self‑Service application sits on top of the CSR Implementation application. The Self‑Service app inherits all CSR rules and can extend or override them to provide customer‑facing functionality. This stack arrangement ensures that both applications can use Digital Messaging, with the Self‑Service application serving as the primary front end for messaging channels. For each region, create a separate copy of the application stack.

Scenario 4:  If you have multiple Self-Service applications, consolidate them into a single unified Self‑Service app. Then place this unified app above the CSR Implementation app. Then, create independent stack copies for each region, as usual.

---

This Topic is available in the following Module:

• Multiple Application Support in a single environment v1