This topic shows the message changes that can occur when using the WebSphere message migration utility.
User properties set on the message by an application are also unaltered.
The JMS message types provide header fields which can change as a result of migration:
Header field name | State after migration |
---|---|
JMSMessageID | Unchanged |
JMSCorrelationID | Unchanged |
JMSDeliveryMode | Unchanged |
JMSPriority | Unchanged |
JMSTimestamp | Unchanged |
JMSExpiration | Unchanged |
JMSRedelivered | Can be reset as a result of the migration process. |
JMSType | Unchanged |
JMSDestination | The name of the destination is unaltered. Other properties of the destination are mapped to their WebSphere Application Server Version 6 equivalents, where possible. |
JMSReplyTo | The name of the reply destination is unaltered, and
assumed to exist on the WebSphere Application Server Version 6 bus to
which the messages are being migrated. Note:
|
JMSX properties can also change as a result of migration.
JMSX property name | State after migration |
---|---|
JMSXUserID | Unchanged |
JMSXAppID | Unchanged |
JMSXDeliveryCount | Can be reset as a result of the migration process. |
JMSXGroupID | Unchanged |
JMSXGroupSeq | Unchanged |
JMSXProducerTXID | Not supported by service integration bus. |
JMSXConsumerTXID | Not supported by service integration bus. |
JMSXRcvTimestamp | Not supported by service integration bus. |
JMSXState | Not supported by service integration bus. |
The following JMS_IBM properties do not change as a result of migration.
JMS_IBM property name | State after migration |
---|---|
JMS_IBM_Report_* | Unchanged |
JMS_IBM_MsgType | Unchanged |
JMS_IBM_Feedback | Unchanged |
JMS_IBM_Format | Unchanged |
JMS_IBM_PutApplType | Unchanged |
JMS_IBM_Encoding | Unchanged |
JMS_IBM_Character_Set | Unchanged |
JMS_IBM_PutDate | Unchanged |
JMS_IBM_PutTime | Unchanged |
JMS_IBM_Last_Msg_In_Group | Unchanged |