Queue Selectors
172
Integration Guide
Message Body
The message body contains the XML message that is processed into the system or
sent to the external system.
Queue Selectors
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.
compressed 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.
uncompressed_length 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.
MSG_TRK_ENABLED Internal value.
MSG_OP_MODE The endpoint name for the outbound messages,
fixed string MXJMS for inbound messages.
MSG_TRK_STORE_MSG Internal value.
MSG_TRK_EXTSYS External system name for outbound and inbound
messages.
Msgkeyval A field name message key.
searchfieldval A comma-separated search field value.
msgoperation Indicates whether the publish channel or
enterprise service contains a sync, create, update,
or delete operation.
msgstatus Indicates whether the message has a RECEIVED,
ERROR, DELETED, or a PROCESSED status value.
msgerrmsg Contains the exception message text.
Properties Description
Type of Queue Where to Identify Selector
Sequential queue As a property of the cron task
Continuous queue In the ejb-jar.xml of the message-driven bean
To Next Page
Loading...