WebSphere Message Brokers
File: ac24870_
Writer: John Cooper

Reference topic

This build: July 31, 2007 21:19:41

Order of precedence for deriving the message domain

When a JMS Message is received by the JMSInput node, the message domain is derived according to the following criteria and in the following order of precedence:

  1. The Message Domain property is set to a specific domain type.

    In this case, the node expects to receive only the following JMS message types:

    Message domain Valid JMS message types
    BytesMessage TextMessage MapMessage StreamMessage ObjectMessage
    BLOB X X     X
    XML   X      
    XMLNS   X      
    XMLNSC   X      
    MRM X X      
    JMSMap     X    
    JMSStream       X  
    MIME X X      
    IDOC X X      

    If a JMS Message type is received, which is not valid for the Message Domain that is configured in the JMSInput node, the node issues a warning and backs out the message either to the source JMS provider destination, or to the backout destination.

  2. The Message Domain property is blank (default). The JMSType header value from the JMS input Message is set according to the URI format shown below:
    JMSType Broker domain
    mcd://domain/[set]/[type]/[?format=fmt] MRM
    mcd://XML or mcd://xml XML
    mcd://XMLNS or mcd://xmlns XMLNS
    mcd://XMLNSC or mcd://xmlnsc XMLNSC
    mcd://IDOC or mcd://idoc IDOC
    mcd://MIME or mcd://mime MIME

    If a JMS Message type is received, which is not valid for the Message Domain configured in the JMSType header, the node issues a warning and backs out the message either to the source JMS provider destination, or to the backout destination.

    Messages received in the MRM domain

    Messages that are received in the MRM domain must have a JMSType header field that is set in accordance with the following format (which is also used in JMS provision):
    mcd://domain/[set]/[type]/[?format=fmt]

    For details of the [type] syntax, refer to Specifying namespaces in a Message Type.

    If the JMSType field does not conform to this format, the message is handled in the BLOB domain. For example,
    mcd://MRM/SWIFTXML2005/{http://SWIFT/2005}:Document/?format=SWIFT
  3. The Message Domain property is blank (default) and the JMSType header value from the JMS input Message is also blank.

    The message domain is set according to the JMS Message Java Class as follows:

    TextMessage XML
    BytesMessage BLOB
    MapMessage JMSMap
    StreamMessage JMSStream
    ObjectMessage BLOB
Related concepts
Specifying namespaces in a Message Type
Multipart messages
Related reference
JMS message structure
JMS message types
Representation of messages across the JMS Transport
JMS input message header and property data
JMS Message payload
JMS message payload and appropriate parser
JMS message for output
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:19:41

ac24870_ This topic's URL is: