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.

Discussion

 Manash Pratim Chaliha (Manash_LSA)
Phalanx Consultancy Limited
Pega Lead System Architect
Phalanx Consultancy Limited
GB
Manash_LSA Member since 2008 52 posts
Phalanx Consultancy Limited
Posted: Jan 11, 2016
Last activity: Feb 2, 2016
Posted: 11 Jan 2016 10:24 EST
Last activity: 2 Feb 2016 6:43 EST
Closed

Pega unable to capture JMSReplyTo from the message header

I have set up a Service-JMS rule and updated the request tab to capture the JMSReply to  attribute. The MQ message has the appropriate MQMD elements in the header payload. In WAS I also set the MQMD Read Enables option to yes for the particular JMS binding of my input MDB listener. I am still unable to get the JMSReplyTo in the service class page. Is there any other setting in WAS which i need to check in order to make the MQ header read enabled? Any idea why the process is behaving like this?

To see attachments, please log in.
Data Integration

Posted: 8 years ago
Updated: 8 years ago
Posted: 2 Feb 2016 6:38 EST
Updated: 2 Feb 2016 6:43 EST
Ipshita Borkakati (borki) Principal Technical Writer
Pegasystems Inc.
IN

Need more information on the following points:

  • Are you using Service JMS or Service MQ? Or is your actual input in MQ format and you want to convert it into a JMS message, which would mean that you are using Service JMS with MDB listener?
  • Is this configuration done on Websphere?

 

To see attachments, please log in.

Related content:

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