JMS message domain properties

The JMSInput node can receive all of the JMS message types that are specified in the Java Message Service Specification, version 1.1. For more information see JMS message types.

The following JMSInput node properties can be specified:
Property Description
Message Domain
  • blank
    The messages to be received are for either JMS TextMessage or BytesMessage. The JMS message header field is set according to the format:
    mcd://domain/[set]/[type]/[?format=fmt]
    Valid JMS Message types for each domain are described in JMS message types.
  • BLOB

    Messages in this domain are processed by the BLOB parser. The BLOB parser is a program that interprets a bit stream or message tree that represents a message that belongs to the BLOB domain, and generates the corresponding tree from the bit stream on input, or a bit stream from the tree on output.

  • XML, XMLNS, and XMLNSC

    For messages conforming to the W3C XML standard.

  • MIME

    For messages conforming to the MIME standard implemented by WebSphere Event Broker.

  • MRM

    For modelling a wide range of messages including XML, fixed-format binary and formatted text.

  • JMSMap or JMSStream

    For messages produced by the WebSphere MQ implementation of the Java Messaging Service standard.

  • IDOC

    The IDOC domain processes messages that are sent to the broker by SAP R3 clients across the MQSeries® link for R3.

Message Set If the node is expecting a TextMessage or a BytesMessage that contains a payload to be interpreted using the MRM domain, the Message Set property should be set to the appropriate MRM Message Set ID. This is mandatory when using a Message Domain of MRM.

The default value is blank (not set).

Message Type If the Message Set property has been specified, you have the option to specify the Message Type.

This property is used when you define multipart messages.

The value that you specify is used as an absolute or relative path to the innermost message from the outermost message. The value is used as a prefix to the value of the Message Type property that is specified for the outermost message. The Message Set property value is specified either in the MQRFH2 header of the message, or in the input node of the message flow.

If you set a value, it must be in the form id1/id2/.../idnu where id1 is the identifier of the outermost message, id2 is the identifier of the next element or message, and idn is the identifier of the innermost message.

The default value is blank (not set).

Message Format If you are using the MRM domain, you can model a variety of different physical representations using named physical formats.
  • Use the Custom Wire Format (CWF) physical format to model fixed format messages from legacy applications written in C, COBOL, PL/1 and other languages. This support includes the ability to create a message model directly from a C header file or COBOL copybook.
  • Use the XML Wire Format (XML) physical format to model XML messages, including those that use XML namespaces. This support includes the ability to create a message model directly from an XML DTD or XML Schema file.
  • Use the Tagged Delimited String Format (TDS) physical format to model formatted text messages, where the field content is identified by tags, is separated by specific de-limiters, or both. This support is rich enough to model industry standards such as SWIFT, EDIFACT and X12.
Related concepts
JMS Transactionality
Related reference
JMS properties for application communication models
JMS message selector