Specify whether messages are forwarded to IBM MQ as JMS messages
Create a destination context property that determines whether an MQRFH2 header is added to IBM MQ JMS messages produced by foreign or alias destinations.
This task assumes that we have created an alias bus destination or a foreign bus destination. See Create an alias destination on a bus or Create a foreign destination on a bus.
Carry out this task if we want JMS messages produced by foreign bus destinations or alias bus destinations forwarded to IBM MQ. In this task, we define a destination context property called _MQRFH2Allowed that adds an MQRFH2 header to JMS messages. If we do not configure _MQRFH2Allowed, the default value is NO, and an MQRFH2 header is not added to the message. WebSphere Application Server v5.1 users may be aware of an IBM MQ flag called TARGCLIENT used to add RFH2 headers to JMS messages. For more information about the use of the MQRFH2 header in interoperating with IBM MQ, see Mapping the message body to and from IBM MQ format and Point-to-point messaging with an IBM MQ network.
To create and configure a context property called _MQRFH2Allowed on a foreign or alias destination, use the administrative console to complete the following steps:
Tasks
- Display the context properties for a selected foreign or alias destination:
- Click Service integration -> Buses -> bus_name -> [Destination resources] Destinations.
- Select the foreign or alias destination for which we want to create the context property.
- Under Additional Properties, click Context properties.
- Click New to create a new context property.
- Specify the following context information:
- Name
- Type the name _MQRFH2Allowed.
- Context type
- Select the information type Boolean in the drop-down list.
- Context value
- Type the value true .
- Click OK.
- Save changes to the master configuration.
An MQRFH2 header is added to all messages produced by the foreign or alias destination. This means that JMS messages will be forwarded to IBM MQ as JMS messages.
Related:
Point-to-point messaging with an IBM MQ network Mapping the message body to and from IBM MQ format Mapping the message header fields and properties to and from IBM MQ format Mapping additional MQRFH2 header fields in service integration Mapping the JMS delivery option and message reliability to and from the IBM MQ persistence value Context properties [Collection] Context properties [Settings]