Skip to main content

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

Configuring a consumer system for remote case types

Updated on March 29, 2022

To process cases that come from another application, configure the system that hosts your destination application as a consumer. As a result, at run time, users can perform work from multiple applications within the context of one consumer application, without the need to switch between different products.

For example, a customer service representative (CSR) can use a Financial operations application to work on cases that belong to the Loan requests and Mortgage requests applications. In this case, the Financial operations application is on a consumer system, while the Loan requests and Mortgage requests applications operate on a producer system.
Before you begin:
Configuring a consumer system requires a keystore and truststore that support connection to the producer system, as well as copying and then editing a token profile that Pega Platform includes by default.
  1. Create a truststore with the Remotecasetype_Truststore name, and then upload the .jks truststore file of the producer system.
  2. Create a keystore with the Remotecasetype_Keystore name, and then upload the .jks keystore file of the consumer system.
  3. In the navigation pane of Dev Studio, click Records.
  4. Expand the Security category, and then click Token Profile.
  5. In the list of instances, open the Remotecasetype_Consumer token profile.
    • For remote case types to work correctly, configure the token profile that Pega Platform includes by default instead of copying or creating a new instance of the token profile.
    • After an update to a higher version of Pega Platform, you must override the Remotecasetype_Consumer token profile again.
  6. In the Security section of the token profile, configure security settings:
    1. In the Security configuration list, select Signature.
    2. In the Signature type list, select Asymmetric.
    3. In the Signature type algorithm field, press the Down arrow key, and then select RS256.
    4. In the Keystore field, enter the keystore that you created in step 2.
      Tip: The JSON web key set URI from the Security section of this token profile is the URL that you use when you create a truststore for the producer system.
      Result: When you select the keystore, the system autpopulates the alias value.
    5. In the Password field, enter the password related to the keystore.
  7. Click Save.
For example: The following figure shows security configuration for the token profile of the consumer system:
Security section of a token profile
The Security section of the token profile configured for the consumer system
What to do next: Create a connection between your applications so that you can publish remote case types. For more information, see Creating remote case types.
    • Previous topic Mapping the identity mapping to the client registration for remote case types
    • Next topic Creating remote case types

    Have a question? Get answers now.

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

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us