Message Body; Queue Selectors - IBM BJ0NJML - Service And Asset Management Integration Manual

Queue Selectors

Message Body

Queue Selectors
172
Properties
compressed
uncompressed_length
MSG_TRK_ENABLED
MSG_OP_MODE
MSG_TRK_STORE_MSG
MSG_TRK_EXTSYS
Msgkeyval
searchfieldval
msgoperation
msgstatus
msgerrmsg
The message body contains the XML message that is processed into the system or
sent to the external system.
Selectors act as WHERE clauses in the JMS queue consumer. Selectors can be
applied to message headers and properties in either a continuous or a sequential
queue.
The following table lists how you can use continuous selectors in the JMS queue
consumer.
Type of Queue
Sequential queue
Continuous queue
Description
Indicates whether the message is compressed.
Values can be true or false; the default value is
false.
The standard Java Inflater and Deflater APIs
(java.util.zip) are used for compression.
Stores the original message payload size before
compression. This value must comply with the
schema type int [xsd:int] and is present only when
the compressed property is set to true.
Internal value.
The endpoint name for the outbound messages,
fixed string MXJMS for inbound messages.
Internal value.
External system name for outbound and inbound
messages.
A field name message key.
A comma-separated search field value.
Indicates whether the publish channel or
enterprise service contains a sync, create, update,
or delete operation.
Indicates whether the message has a RECEIVED,
ERROR, DELETED, or a PROCESSED status value.
Contains the exception message text.
Where to Identify Selector
As a property of the cron task
In the ejb-jar.xml of the message-driven bean
Integration Guide