This content has been marked as final. Show 1 reply
The OAI 9.0.2 MQ Series adapter is implemented based on IBM's JMS API, i.e.
a message sent or received from a MQ Series destination (queue/topic) is
internally stored as a JMS message, before being converted to/from an OAI
message. Some native (C) MQ Series clients might not be prepared to
deal with (ignore) the JMS message header, which gets written by the JMS
In addtion to this, the MQ Series adapter always either writes (enqueues)
TextMessage's or BytesMessage's depending on the operational mode of the
adapter. When the adapter operates in XML mode (ota.type=XML), it always
sends a TextMessage, while it always sends a BytesMessage when operating in
D3L mode (ota.type=D3L) as the output from a D3L translation is always
considered a byte stream.
To loosen up both of these constraints, a new adapter.ini configuration
property has been introduced:
If this variable is assigned any value, then the sender destination
is assumed to be non-JMS compliant and hence the adapter will force the JMS
API not to write the JMS headers.
If the value of this configuration property is "MQFMT_STRING" (not incl.
the double quotes), then the adapter will always write (enqueue) the
message as a TextMessage, even though e.g. the result of a D3L translation
contains non-printable bytes.
For other values of this variable, check Chapter 10. MQMD - Message
descriptor in the MQ Series Application Programming Reference guide.
Normally this value would specify an application/user defined format,
(not starting with the letters "MQ") which typically at the receiving end
mandates a data-conversion exit program (see Chapter 11 of MQ Series
Application Programming Guide).
Note: Data-conversion exits are not supported on MQSeries for Windows or