IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Retained publications with headers in MQRFH format

Retained publications in MQRFH format might lose data when migrated to WebSphere® MQ.

IBM® Integration Bus applications that communicate with one another using publish/subscribe can do so regardless of the message format that they use. IBM Integration Bus delivers the message in the format of the subscription and provides automatic conversion to ensure that a subscriber receives messages in the requested format.

IBM Integration Bus applications generally use the MQRFH2 message header, but it is possible that an application might have used the MQRFH format.

The migration of publish/subscribe information from WebSphere Message Broker to WebSphere MQ requests messages in MQRFH2 format. It is rare for IBM Integration Bus client applications to use messages in MQRFH format. However, if an application does use retained messages in MQRFH format, it is possible that some truncation of data might occur upon migration. In particular, data passed using the MQPSStringData and MQPSIntData name/value pairs is not migrated.

The migration function checks for two conditions in the data that is returned from the broker:
  1. That there is at least one retained message stored in the broker
  2. That there is at least one MQRFH subscription
If both these conditions are true, the migration function displays a warning message and writes a warning message in the migration log stating that MQRFH retained publications have been migrated with a possible loss of data.

MQRFH2 retained publications are migrated correctly.

Parent topic: Migrating publish/subscribe information to WebSphere MQ
bq13120_.htm | Last updated Friday, 21 July 2017