Sun Java System Message Queue 4.3 Installation Guide

Broker Compatibility

A Message Queue 4.3 message broker will interoperate with one from Versions 3.0.x, 3.5, 3.6, or 3.7, and is able to migrate data from Versions 3.6 or 3.7. However, some changes have been made in broker properties and the persistent store schema. The degree of compatibility depends on the earlier Message Queue version from which you are upgrading:

When upgrading from Message Queue 3.6 or 3.7 to Message Queue 4.3, you can choose either of two approaches to handling the older versions’ instance configuration ( files:

Any persistent Message Queue 3.6 or 3.7 data (messages, destinations, and durable subscriptions) is automatically converted to Message Queue 4.3 data when starting up a Message Queue 4.3 broker for the first time. For example, existing destinations will be converted to Message Queue 4.3 destinations, preserving existing attributes and using default values for new attributes.

For Message Queue 3.6, the automatic upgrade leaves the original data intact in its original location. You can delete this data in either of the following ways:

If you mix Message Queue 3.5, 3.6, or 3.7 brokers together with Message Queue 4.3 brokers in a cluster, you should consider the following issues:

Note –

When upgrading a broker cluster from versions 3.x to versions 4.x, it is recommended that you shut down all client applications and all brokers in the cluster, perform the Message Queue upgrades, check any data migrations, and then restart the cluster and client applications. It is not recommended that you attempt a rolling upgrade in which you successively upgrade brokers while maintaining messaging operations.