Response for propositions are not updated properly in ADM Report
SummaryNBO 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 MessagesNot Applicable
Steps to Reproduce
- Login to individual nodes
- Accept any offer
- Update ADM reporting data from LB
- Check for the response count in the report
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.
Published February 2, 2017 - Updated February 4, 2017