MQ Series and Publish and Wait

Hi,

Has anyone got any ideas on how to persist a destination id for a publish and wait over a call and response to MQ?

We have an overall Integration Component which is triggered by an intial request document and then makes a series of publish and wait calls, which trigger various other components to simulate a simple process flow.
The problem is that the send operation to the queue is in one Integration Component (triggered by a document) and the recieve operation has to be in another Component as it is triggered by an operation which deals with the returning MQ Message (and then outputs the response document). This means that the destination id/publication id of the original publish and wait is lost.

Do any of the MQ Message Descriptors allow you to persist system information? We can’t add to the application’s input fields.

any ideas gratefully accepted!!

Hello,

Yes, there are some fields in the MQ headers that allow you to store user’s information along with your payload. You can also use some of the system fields, such as message ID/message correlation ID. For instance, you can use either of fields to store the Publish ID.

That said, you need to make sure your MQ applications that process the MQ request documents retain those attributes of the MQ request documents in the MQ response document that are important to your IC and the webM document fields that it maps to.

Hope this helps.

Bruce

Hello,

Yes, there are some fields in the MQ headers that allow you to store user’s information along with your payload. You can also use some of the system fields, such as message ID/message correlation ID. For instance, you can use either of these fields to store the Publish ID.

That said, you need to make sure your MQ applications that process the MQ request documents retain those attributes (whatever that might be) of the MQ request documents in the MQ response document that are important to your IC and the webM document fields that it maps to.

Hope this helps.

Bruce