Question

26
Views
Close popover
Sovan Parija (SovanP43)
Larsen & Toubro Infotech Limited

Larsen & Toubro Infotech Limited
IN
SovanP43 Member since 2015 13 posts
Larsen & Toubro Infotech Limited
Posted: December 8, 2020
Last activity: December 8, 2020

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

Data Integration Senior System Architect