Restrictions apply when replying to a message using a WebSphere
MQ application, for example an application that has been developed using WebSphere
MQ JMS.
When a message with a reply to destination is sent to a destination that
is assigned to a WebSphere MQ server bus
member, the reply to destination is represented by the following WebSphere
MQ message descriptor fields:
- Queue name: this is set to the name of the service integration destination
that has been specified as a reply to queue.
- Queue manager name: this is set to the name of the service integration
bus from which the message was sent.
Queue names and queue manager names which are not recognized by WebSphere
MQ are truncated at the first character which is not a valid WebSphere MQ
character, or at the WebSphere MQ limit on the field length. This means that
there are some situations when a WebSphere MQ JMS application cannot reply
to a message received from service integration:
- If the reply to destination name is not a valid WebSphere MQ queue name.
- If the service integration bus where the reply to destination resides
has a name which is not a valid WebSphere MQ queue manager name.
- If the reply to destination does not reside on the same service integration
bus as the bus where the message originated.
- If a WebSphere MQ Link over which the reply can flow does not exist between
the service integration bus and the WebSphere MQ network.
- If the 'virtual queue manager name' allocated to the WebSphere MQ Link
does not match the name of the service integration bus to which the WebSphere
MQ Link points.