Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sovan Parija (SovanP43)
OCBC

OCBC
SG
SovanP43 Member since 2015 13 posts
OCBC
Posted: Dec 8, 2020
Last activity: May 25, 2021
Posted: 8 Dec 2020 4:41 EST
Last activity: 25 May 2021 6:00 EDT
Closed

Asynchronous Connect MQ implementation and Custom Headers

Hi Team,

Our requirement is to connect to the Websphere MQ server asynchronously. We are facing two issues while implementing it

(i) When we are invoking the connector using Connect MQ method, we are running into the 'MQJE001: Completion Code '2', Reason '2033'' exception. The reason according to https://community.pega.com/support/support-articles/connect-mq-error-comibmmqmqexception-mqje001 article is that Pega is not configured to support asynchronous processing when acting as a connector.

Can anyone please share the custom java changes that need to be done in InvokeMQConnector to support asynchronous processing?

(ii) The team which hosts the service is using custom headers for MQ connectivity and there is no provision in Pega to add custom headers in Connect MQ and Service MQ rules. The message headers vary in their exact names and data types as well which is causing number format exception and failing the request.

Kindly advise on how to add custom headers in the Connect MQ and Service MQ rules.

 

Thanks

Sovan

***Edited by Moderator Marissa to change type from General to Product, update Product details****
To see attachments, please log in.
Pega Platform
Data Integration
Senior System Architect

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

Pega Collaboration Center 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