MQ connection via Cluster Queue
Hi team,
Is there a way Pega Smart Investigate (8.8) can connect to request MQ via Cluster Queue?
For most of our queue we are connecting immediately to the request MQ using the queue name, however there were unknown changes done in the MQ team that for newly setup queues it goes via Cluster queue and it seems at the moment Pega cannot get through and ends up with: Could not connect to request queue : DATA.FROM.PEGA.ISO.NORMAL.Q01 MQJE001: Completion Code '2', Reason '2085'. - Invalid queue name.
It is quite urgent, so please let me know if it's better to make a support ticket.
Thank you.
Accepted Solution
Updated: 3 Sep 2024 9:09 EDT
KBC Groep NV
CZ
Unfortunately that we are already using. However we figured out another way, when we remove the Request queue manager from the Connect-MQ it is working fine as we then are using decision tables to connect each of them to specific environments.
So our solution was to not mention the Queue Manager in the Connect-MQ.
Updated: 30 Aug 2024 11:40 EDT
Pegasystems Inc.
GB
To resolve the issue with connecting to the request MQ via Cluster Queue, verify the queue name and configuration in the MQ cluster. Ensure the necessary dynamic system settings are configured. If the issue persists, consider using JMS Connectors instead of Connect MQ rules.
According to the Pega Platform 8.6.3 Patch Resolved Issues, there was an update to handle Connect MQ rules that used an alias queue. The support documentation has been revised to outline the necessary steps for updating an application to perform as expected. You may need to create dynamic system settings in the Pega-IntegrationEngine ruleset with the following default values: 'mq/pmo' = 0, 'mq/gmo' = 0, 'mq/oo_request' = 1040, and 'mq/oo_response' = 16. This might help resolve the issue with connecting to the clustered queue
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Platform 8.6.3 Patch Resolved Issues
Connect MQ form - Completing the Request tab
To resolve the issue with connecting to the request MQ via Cluster Queue, verify the queue name and configuration in the MQ cluster. Ensure the necessary dynamic system settings are configured. If the issue persists, consider using JMS Connectors instead of Connect MQ rules.
According to the Pega Platform 8.6.3 Patch Resolved Issues, there was an update to handle Connect MQ rules that used an alias queue. The support documentation has been revised to outline the necessary steps for updating an application to perform as expected. You may need to create dynamic system settings in the Pega-IntegrationEngine ruleset with the following default values: 'mq/pmo' = 0, 'mq/gmo' = 0, 'mq/oo_request' = 1040, and 'mq/oo_response' = 16. This might help resolve the issue with connecting to the clustered queue
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Platform 8.6.3 Patch Resolved Issues
Connect MQ form - Completing the Request tab
Connect MQ form - Completing the Service tab
I would suggest if the product is not working as documented that you log a support incident via the msp. Pelase provide the INC id here so that we can help track it.
Accepted Solution
Updated: 3 Sep 2024 9:09 EDT
KBC Groep NV
CZ
Unfortunately that we are already using. However we figured out another way, when we remove the Request queue manager from the Connect-MQ it is working fine as we then are using decision tables to connect each of them to specific environments.
So our solution was to not mention the Queue Manager in the Connect-MQ.