Websphere MB Message Set format

The description, organization, and Convention of the message format are collectively referred to as the message format model. Industry standards are: SWIFT, EDIFACT, X12, FIX, HL7, TLOG, different message organization model called message domain, need the corresponding parser to implement the parsing of message format. A message set item can contain only a single message set, which is how the message format model is organized. A message set can contain multiple message definition files, and each message definition file can contain multiple messages.

Our daily exposure to the message format is broadly divided into two types: unformatted and self-formatted. The message of the former needs to be read with the help of a predefined message format, the message body itself with the format description and delimitation, so that you can automatically distinguish the name and value of the message field and hierarchical relationship. For readability, some spaces, locators, and line breaks are often added to make the format neat.

Either message format requires the parser to convert the message from the external expression format to the WMB internal organization, the message domain (domain), where the agent-supported parser in WMB has MRM, XML, JMS, IDOC, BLOB, MIME, The corresponding internal organization takes the parser name as the message domain name, which is the root node name of the message body. MRM is the only generic message resolver that requires a format definition to work with, and other parsers parse messages based on a formatted message contract without further formatting definitions.

MRM is a generic message parser that needs to further determine its message organization format through message sets, message types, and message formats. The Kizhong message set is typically a message set item or a codename, the message type is typically a message name, and the message format is typically a format name. The message format is divided into three kinds: CWF, TDS, XML. Where CWF is a format definition for a fixed-length message, the message itself does not contain any formatting information, and the starting position and length of each field must be specified. TDS is a message element separated by a flag or delimiter and must specify the field name and delimiter recognition rules. The XML format is custom, defining both the separation of message elements and the name of the field in which the message is delimited. Because the message content contains a lot of format information, the transfer efficiency of XML will be lower than TDs, and TDs will be lower than CWF.

The JMS format refers to the message format that WebSphere MQ outputs through the JMS API interface, the message is organized in JMSMAP or Jmsstream, and in fact there is no JMS parser in WMB, and the Mqinput node interprets the JMS message with an XML parser.

The IDoc format refers to the message format sent from the SAP R3 client through the MQSeries link for R3, where the mqmq.format of the input message must be the resolving class name. Typically, the IDOC message contains MQMD, a DC (Control Structure), multiple DD (Data structures)

The BLOB format, which is unformatted, treats the message as an array of characters, which is the simplest expression of the message, but cannot be positioned and manipulated on the message domain.

The MIME format is typically used for SOAP messages with attachments, and the body of the message is divided into sections, separated by strings specified by boundary in Mime.content-type.

WMB support partial parsing, only the branch used to parse. This can greatly shorten the parsing time of most messages.