LinkedIn
Copied!

Table of Contents

Configuring a producer system for remote case types

To pass remote case types to another application, configure the system that stores your case types as a producer system. As a result, you provide a framework for case workers to process work from multiple applications without changing context, which promotes efficiency and saves time in your organization.

For example, your system might host Loan requests and Credit card operations applications. You want to publish case types from these applications to a VIP customers operations application so that users can perform work by logging in to this application only. You configure the system with the Loan requests and Credit card operations applications as the producer system first.
Ensure that your applications in the producer system use Cosmos React. For more information, see Cosmos React (early adopter).

Accessing remote case assets that are available in the producer system requires performing security configurations. Pega Platform provides the OAuth 2.0 client registration, identity mapping, and token profile that you copy into your ruleset and edit to meet your business needs. The security configuration also requires your own truststore.

  1. Preparing OAuth 2.0 client registration for remote case types

    To ensure that remote application from a consumer system can properly communicate with your producer system, prepare the OAuth 2.0 client registration in your producer system. As a result, you create a secure and reliable connection between your producer and consumer systems.

  2. Preparing a token profile for remote case types

    After you prepare the OAuth 2.0 client registration for your remote case types, prepare a token profile. Token profiles secure data exchange between two parties, such as producer and consumer systems.

  3. Preparing identity mapping for remote case types

    After you prepare the client registration and token profile for your producer system, prepare identity mapping to ensure that Pega server correctly identifies operators in your application. You also define how to map the user identity information for use in the Pega application.

  4. Mapping the truststore to the token profile for remote case types

    After you prepare the identity mapping, map the token profile to the truststore to ensure a secure encryption of data between your producer and consumer systems.

  5. Mapping the identity mapping to the client registration for remote case types

    Ensure that the producer and consumer system can communicate correctly and securely by mapping the identity mapping to the client registration that you created for the producer system.

Have a question? Get answers now.

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