Support Article

ADM responses are not getting updated properly across nodes



User has Next Best Offer (NBO) application running across four nodes and ADM server in one of the four nodes.

That is,
ADM setup with PRPC Culster Across multiple Data Centers.

User could observe that proposition responses are not getting updated properly from all individual nodes.

The responses that are captured from ADM node is getting added than from the non ADM node.

Error Messages

Not Applicable

Steps to Reproduce

1. Create a PRPC cluster each on separate data centres. The clusters are hosted in independent WebSphere Cells.
2. Include an additional server on one of the data centre hosting the ADM application.
3. Set responses from both data centres.

Root Cause

Having an ADM server running for each data center will be of no use unless the ADM server is reachable by all of the PRPC nodes.

Since ADM is not clusterable, it is not a suggested configuration to share ADM database by more than one ADM server.

Only the ADM server reachable to the PRPC/DSM nodes will be learning and that node should be configured in the ADM Services for the Decisioning infrastructure services.

Since the PRPC/DSM nodes will be sharing the database, it will not be possible to configure separate ADM services details (IP and Port) for each data center.


Configure foreign bus connections across the Pega Cluster so that the ADM server can receive JMS messages from PRPC nodes running on a different Cell/Cluster.

Published May 8, 2017 - Updated May 23, 2017

Have a question? Get answers now.

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