Advanced Queuing - Oracle

Converting Messages
Messaging Gateway defines {name, value} pairs for AQ message properties and the
header fields of non-Oracle messaging systems to convert native message headers
and allow users to override the default values. The {name, value} pairs are called
header properties. Whether or not you can access the header properties for a given
propagation job depends on the messaging systems involved and the AQ payload
type or transformation.
Default Message Header Mapping
Table 18–1 describes the default mapping between AQ message properties and
MQSeries header fields. (Refer to "Notes on Table 18–1" on page 18-34 for an
explanation of the numbers in parentheses.)
Table 18–1 Default Mapping Between AQ Message Properties and MQSeries Header
Fields
AQ Message
Property
MQSeries
Header Field
Notes on Table 18–1
Outbound Mapping (AQ
Value to MQSeries Value)
priority priority AQ values 0,1,2,3,4,5,6,
7,8,9 are mapped
respectively to MQSeries
values 9,8,7,6,5,4,3,2,
1,0
AQ values < 0 are mapped as
MQSeries value 9
AQ values >=10 are mapped
to MQSeries value 0
expiration expiry Time unit is mapped to tenths
of a second (1)
AQ value NEVER is mapped
to MQEI_UNLIMITED
1. For outbound propagation, the AQ expiration value is used to calculate the
remaining time-to-live because the AQ expiration value represents the
expiration time specified when the message is enqueued. For inbound
propagation, a direct mapping is done because the MQSeries expiration value
already represents the remaining time-to-live.
18-34 Oracle9i Application Developer’s Guide - Advanced Queuing
Inbound Mapping
(MQSeries Value to AQ
Value)
MQSeries values 0,1,2,3,
4,5,6,7,8,9 are mapped
respectively to AQ values
9,8,7,6,5,4,3,2,1,0
Time unit is mapped to
seconds (1)
MQEI_UNLIMITED is mapped
to NEVER