Advanced Queuing - Oracle

Table 18–5 MQSeries Header Default Values
MQSeries Property Name Default Value
Using Header Properties: Examples
Converting Messages
putMessageOption MQPMO_SYNCPOINT will always be added;
refer to (2) in "Notes on Table 18–4" on
page 18-38.
The following propagation scenarios exemplify the use of header properties.
Using MGW_BASIC_MSG_T for Outbound Propagation: Example
Consider an outbound propagation job from an AQ queue to an MQSeries queue.
Because the MQSeries driver supports only the MGW_BASIC_MSG_T type, the
propagation job must be configured so that the AQ driver converts the AQ payload
to an MGW_BASIC_MSG_T canonical message. To accomplish this, either the source
queue payload type must be SYS.MGW_BASIC_MSG_T, or a transformation whose
output (to) type is SYS.MGW_BASIC_MSG_T must be supplied.
For outbound propagation, use the MGW_BASIC_MSG_T.header attribute to
specify native message header properties that are used when the message is
enqueued to the destination queue. In this example, it will contain {name,value}
pairs for MQSeries header properties, as described in Table 18–4.
Although the AQ driver generates {name,value} pairs for the AQ message
properties (refer to Table 18–2), the information is lost because the MQSeries
message format does not allow you to specify user-defined message property
information.
Using MGW_BASIC_MSG_T for Inbound Propagation: Example
For an inbound propagation job from an MQSeries queue to an AQ queue, the
MQSeries driver always converts its native message to an MGW_BASIC_MSG_T
canonical message. Therefore, the propagation job should be configured so that the
AQ driver converts the canonical message to a SYS.MGW_BASIC_MSG_T payload
type. To accomplish this, either the destination queue payload type must be
SYS.MGW_BASIC_MSG_T, or a transformation whose input (from) type is
SYS.MGW_BASIC_MSG_T must be supplied.
When used for inbound propagation, the MGW_BASIC_MSG_T.header attribute
contains {name,value} pairs for the native message header properties of the message
dequeued from the source queue. In this example, it will contain {name,value} pairs
for MQSeries header properties, as described in Table 18–4.
Messaging Gateway 18-39