JMS monitor adapter event
The following table describes the elements for JMS monitor adapter event.
JMS monitor adapter event elements
Element |
Description |
---|---|
|
Contains the JMS message response |
|
Specifies the queue or topic for the message |
|
Contains the message header fields |
|
Specifies the delivery mode for the message |
|
Specifies the expiration time for the message |
|
Specifies the priority of the message |
|
Specifies the unique message identifier |
|
Specifies the time-stamp of the message |
|
Specifies the ID used to link one message with another |
|
Specifies the string identifying the contents of the message |
|
Specifies the destination name (name of the queue or topic) for sending a reply |
|
Indicates whether a message has been resent |
|
Specifies the character set used to decode characters for inbound encoded messages (only for ByteMessage type) |
|
Contains the message body, in XML format |
The following figure shows an XML sample for the JMS monitor adapter event.
XML sample of the JMS monitor adapter event
<message>
<destination> the queue/topic </destination>
<header>
<JMSDeliveryMode/>
<JMSExpiration/>
<JMSPriority/>
<JMSMessageID/>
<JMSTimestamp/>
<JMSCorrelationID/>
<JMSType/>
<JMSReply-to/>
<JMSRedelivered/>
<properties>
<property>
<name>string</name>
<value type="Integer">string</value>
</property>
.
.
<property>
<name>string</name>
<value type="Float">string</value>
</property>
</properties>
</header>
<body>
<map>
<entry>
<name>Emp Name</name>
<value type="String">Mr Bean.</value>
</entry>
<entry>
<name>Emp id</name>
<value type="Integer">1234</value>
</entry>
.
.
<entry>
<name>Work Hours</name>
<value type="Float">23.45</value>
</entry>
</map>
<text>First message</text>
<bytes>SHJHDGJHG=</bytes>
</body>
</message>
To use the data from a monitor adapter event in the triggered process, a Job Input Parameter, inputevent must be created on the Start activity of the process. The <data>
element from the monitor adapter event populates this input.
The following figure shows the XML sample response for the JMS monitor adapter event for BytesMessages type.
XML sample of the JMS monitor adapter event message response for Byte content type
<message>
<destination>dynamicQueues/TestQueue</destination>
<header>
<JMSDeliveryMode>1</JMSDeliveryMode>
<JMSExpiration>0</JMSExpiration>
<JMSPriority>0</JMSPriority>
<JMSMessageID>ID:Host-IP-1399-1258954714529-0:4:1:1:1</JMSMessageID>
<JMSTimestamp>1258956950466</JMSTimestamp>
<JMSCorrelationID />
<JMSType>Bytes</JMSType>
<JMSRedelivered>false</JMSRedelivered>
<character-set>UTF-16</character-set>
<JMSReplyTo />
</header>
<body>
<Bytes>Bytes message with charset UTF-16</Bytes>
</body>
</message>
The following figure shows the XML sample response for the JMS monitor adapter event for mixed content type.
XML sample of the JMS monitor adapter event message response for mixed content type
<message>
<destination>dynamicQueues/TestQueue</destination>
<header>
<JMSDeliveryMode>1</JMSDeliveryMode>
<JMSExpiration>0</JMSExpiration>
<JMSPriority>0</JMSPriority>
<JMSMessageID>ID:Host-IP-1399-1258954714529-0:4:2:1:3</JMSMessageID>
<JMSTimestamp>1258967812374</JMSTimestamp>
<JMSCorrelationID />
<JMSType>Bytes</JMSType>
<JMSRedelivered>false</JMSRedelivered>
<character-set>UTF-16</character-set>
<JMSReplyTo />
<properties>
<property>
<name>Work hours</name>
<value type="Float">38.87</value>
</property>
<property>
<name>Emp id</name>
<value type="Integer">31100</value>
</property>
<property>
<name>Emp Nmae</name>
<value type="String">Mr. Bean</value>
</property>
</properties>
</header>
<body>
<Bytes>SGHGKJH87HCIU=</Bytes>
</body>
</message>
Comments
Log in or register to comment.