Representation of messages across the JMS Transport

The following figure depicts the JMS message tree that is used by the JMSInput and JMSOutput nodes: The diagram depicts the JMS message tree that is used by the JMSInput and JMSOutput nodes

JMSTransport
  • Header_Values subfolder:

    This subfolder is mandatory and is always created.

    JMS message properties are optional. If they are present in input messages, they are stored in the appropriate property subfolder.

  • Properties subfolders:

    JMS message properties are optional. If present in the message, they are stored in the appropriate properties subfolder.

  • Message_MetaData subfolder:
    This subfolder is included in order to preserve the payload type of the JMS message. It is used by the JMSOutput node when creating a JMS message. The payload type can be one of the following values:
    Message type Payload values
    Base JMS message with no payload jms_none
    TextMessage jms_text
    BytesMessage jms_byte
    MapMessage jms_map
    StreamMessage jms_stream
    ObjectMessage jms_object

Body

The message payload is stored in the body folder, which is the last child of Root. The payload is transferred by using one of the following message domain parsers:
  • XML
  • XMLNS
  • XMLNSC
  • BLOB
  • JMSMap
  • JMSStream
  • MRM
  • MIME
  • IDOC
Related concepts
Simplified JMS message representation
Related reference
JMS message types
JMS message structure
JMS input message header and property data
JMSInput node
JMSOutput node
MQInput node