We would need to specify a replyTo queue for the middleware and external messaging system through the Message request sent from Pega. In a Service JMS rule there is a provision to Set the JMSReplyTo in the request header, but there is no such option available in the Connect-JMS rule.
By default if the response destination is not dynamic , Pega is setting the response destination as the value for both the response queue and the reply to queue. But this is not correct in my context. Any help in this regard would be helpful.
***Updated by Moderator: Marissa. Removed user added Ask the Expert group tag. Apologies for confusion, shouldn't have been an end-user option***
In the Service-JMS there is a provision to "look for" the JMSReplyTo "property" in the incoming header. There is also a provision in the accompanying JMSListener to set the response queue or to look for the response destination in the incoming message.
In the Connect-JMS, you can create the "message header property" as well. Its just not part of the two header-level fields that the rule-form sets as "header" - namely Type and CorrelationId. The JMSReplyTo, JMSType and JMSCorrelationId are all Message Header Properties.