Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Response for propositions are not updated properly in ADM Report



NBO the decisioning application is running across four nodes and ADM server in one of the four nodes. The response captured for any offer in individual nodes are not getting updated properly in the ADM reporting. We could observer the responses of only two node is getting updated compared to all others.

Error Messages

Not Applicable

Steps to Reproduce

  1. Login to individual nodes
  2. Accept any offer
  3. Update ADM reporting data from LB
  4. Check for the response count in the report

Root Cause

The cluster set-up is spread across 2 data centers with each data center running its own WebSphere cell under which are 2 separate clusters. One cluster has the Pega and other EARs deployed and the other cluster has the ADM and VBD EARs deployed. Each of the data center Cells has its own JMS resources created at the cell level.

In general: all PRPC nodes in a cluster should connect to the same message bus; so all PRPC nodes can publish JMS messages on that topic, and the ADM server can subsequently pick it up. In the set-up described above, prpc nodes which are not under the same cell as the ADM server are not pushing the JMS message to the bus which is accessible to the ADM server running on the other cluster.


For the set-up described above, it is required to configure 'Foreign Bus Connections' in WebSphere. This option is available on the Buses screen in the Deployment Manager console of WebSphere. This will allow adding of SIBs / Messaging Engines from a different cell.
Suggest Edit

Published February 4, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us