Configuring a consumer system for remote case types
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.- Configure the system that you want to use to publish case types as producer system. For more information, see Configuring a producer system for remote case types.
- Ensure that the application for processing remote case types at run time uses Cosmos React. For more information, see Cosmos React.
- Prepare
.jksfiles of the consumer system to upload to the keystore and truststore. For more information, see Creating the keystore.jks and truststore.jks files. - Ensure that you configure the consumer system with the same operator ID that the producer system uses.
- Ensure there is at least one unlocked ruleset open in the consumer system to register the remote case type or to update connection details. For more information, see Branches and unlocked rulesets.
- Create a truststore with the Remotecasetype_Truststore
name, and then upload the
.jkstruststore file of the producer system.For more information, see Creating a keystore for application data encryption. - Create a keystore with the Remotecasetype_Keystore name,
and then upload the
.jkskeystore file of the consumer system.For more information, see Creating a keystore for application data encryption. - In the navigation pane of Dev Studio, click Records.
- Expand the Security category, and then click Token Profile.
- In the list of instances, open the
Remotecasetype_Consumer token profile.
Note: - 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.
- In the Security section of the token profile, configure
security settings:
- In the Security configuration list, select Signature.
- In the Signature type list, select Asymmetric.
- In the Signature type algorithm field, press the Down arrow key, and then select RS256.
- 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. - In the Password field, enter the password related to the keystore.
- Click Save.
Previous topic Configuring a producer system for remote case types Next topic Creating remote case types