Normalized Message properties are either General, available to all participating JBI components, or protocol/binding specific, used by a particular binding component. The following General NM properties are available to all binding components.
Table 1 General Normalized Message Properties
Property Name |
Type |
Description and Use |
---|---|---|
org.glassfish.openesb.messaging.groupid |
java.lang.String |
Uniquely identifies a message with the group to which a message belongs. For example, it applies the RM sequence group number for SOAP messages, or a time stamped file name (where the file record message comes from). This property is optional. |
org.glassfish.openesb.messaging.messageid |
java.lang.String |
Uniquely identifies a message. For batch processing this might be a record number (for example, a particular record in a file), or a GUID. This property is mandatory. |
org.glassfish.openesb.messaging.lastrecord |
java.lang.String |
The value is a string representation of boolean ("true" or "false"). This property can be used to signal the last record in a group, e.g. the last record in a RM sequence for SOAP messages, or the last record in a file when multiple record processing is turned on for File BC. This property is optional. |
org.glassfish.openesb.exchange.endpointname |
java.lang.String |
The value a string representation of the endpoint name set on the exchange. This represents the endpoint name of the "owner" of the message, and could be made available by JBI runtime. |
Binding components each have their own protocol specific Normalized Message properties. These include inbound and outbound specific, as well as general NM properties for each binding component.
For a list of binding component specific NM properties, refer to the following: