This topic describes how the WebSphere MQ message fields and properties map to JMS and are converted by the WebSphere MQ link.
The JMS API defines the set of fields and properties available on a JMS message. The message originating from WebSphere MQ is translated into a form used by the service integration bus. This content is accessed using the methods defined by the JMS javax.jms.Message class and subclasses. For example, the text body of a WebSphere MQ message received by the WebSphere MQ link engine is accessed using the getText method of the resulting javax.jms.TextMessage object. Additionally, a set of JMS provider-specific properties are present that reflect the message's underlying WebSphere MQ representation. These properties are relevant only to applications designed to be WebSphere MQ-aware.
The tables below show the mapping of MQMD V1 and V2 fields.
WebSphere MQ MQMD V1 field in original message | WebSphere Application Server JMS message field or property | Type |
---|---|---|
StrucId V1 | - | |
Version | - | |
Report | JMS_IBM_Report_COA |
s |
MsgType | JMS_IBM_MsgType | s |
Expiry | JMSExpiration | h |
Feedback | JMS_IBM_Feedback | s |
Encoding | JMS_IBM_Encoding | s |
CodedCharSetId | JMS_IBM_Character_Set | s |
Format | JMS_IBM_Format | s |
Priority | JMSPriority | h |
Persistence | JMSDeliveryMode | h |
MsgId | JMSMessageID | h |
CorrelId | JMSCorrelationID | h |
BackoutCount | JMSXDeliveryCount | p |
ReplyToQ | JMSReplyTo | h |
ReplyToQMgr | JMSReplyTo | h |
UserIdentifier | JMSXUserID | p |
AccountingToken | - | |
ApplIdentityData | - | |
PutApplType | JMS_IBM_PutApplType | s |
PutApplName | JMSXAppID | p |
PutDate | JMSTimestamp |
h |
PutTime | JMSTimestamp |
h |
ApplOriginData | - | |
Key: |
WebSphere MQ MQMD V2 field in original message | WebSphere Application Server JMS message field or property | Type |
---|---|---|
GroupId | JMSXGroupID | p |
MsgSeqNumber | JMSXGroupSeq | p |
Offset | - | |
MsgFlags | JMS_IBM_Last_Msg_In_Group | s |
OriginalLength | - | |
Key: |