Use this task to create a destination context property that determines
whether an MQRFH2 header is added to WebSphere MQ JMS messages produced by
foreign or alias destinations.
Before you begin
Why and when to perform this task
You only need to carry out this task if you want JMS messages produced
by foreign bus destinations or alias bus destinations forwarded to WebSphere
MQ. In this task, you define a destination context property called _MQRFH2Allowed
that adds an MQRFH2 header to JMS messages. If you do not configure _MQRFH2Allowed,
the default value is NO, and an MQRFH2 header is not added to the message.
WebSphere Application Server Version 5 users may be aware of a WebSphere MQ
flag called TARGCLIENT that was used to add RFH2 headers to JMS messages.
For more information about the use of the MQRFH2 header in interoperating
with WebSphere MQ, see
Mapping of messages flowing through the WebSphere MQ link and
Point-to-point messaging with a WebSphere 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:
Steps for this task
- Display the context properties for a selected foreign or alias
destination:
- In the content pane, click
the name of the service integration bus
- In the content pane, under Destination resources, click Destinations.
- In the content pane, select
the foreign or alias destination for which you 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
selection list.
- Context value
- Type the value true .
- Click OK.
- Save your 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 WebSphere
MQ as JMS messages.