Message Queue Upgrade

This section describes how to perform a Message Queue upgrade from Java ES 4 to Java ES 5. This section contains the following sections:

• Pre-Upgrade Tasks

• To Upgrade Message Queue

• Post-Upgrade Tasks

• To Roll Back the Upgrade

Pre-Upgrade Tasks

Before you upgrade Message Queue, perform the procedures described in the following sections.

Upgrading Message Queue Dependencies

All Java ES 4 components on a computer system and in a computing environment should be upgraded to Java ES 5. However, because Message Queue does not require upgrading the Java ES 4 components upon on which it depends, this task is optional.

However, if you choose to upgrade all Message Queue dependencies, they should be upgraded in the following order, all before you upgrade Message Queue. You can skip any items that might already have been upgraded.

• Shared Components. Release 5 installer automatically installs all required shared components in the parallel path..

• Directory Server (optional). Instructions for upgrading Directory Server to Java ES 5 are provided in Chapter 2, Directory Server.

• Web Container Software (optional). Instructions for upgrading Web Server or Application Server are provided in Chapter 4, Web Server and Chapter 6, Application Server respectively.

To Verify Current Version Information

Start the Message Queue broker with -version option.

imqbrokerd -version

The outputs that indicate the Message Queue version are:

Release 5

Sun Java System Message Queue 3.7 UR1

Release 4

Sun Java System Message Queue 3 2005Q4 Version: 3.6 SP3

To Upgrade Message Queue

Before You Begin

Back up application data in a production environment before performing an upgrade. For Message Queue data locations, refer Table 5–2.

1. Stop any running Java ES 4 Message Queue instances.

   If Message Queue is being used in an Application Server environment, shut down Application Server, as well.

2. Stop any running brokers.

3. Install the Java ES 5 Message Queue.

   For Java ES 5 Message Queue installation instructions, see the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

4. (Optional) Migrate the Release 4 Message Queue data, as listed in Table 5–2, to the Release 5 Message Queue installation location.

   You need to perform this step only if you wish to preserve any Message Queue broker data from Release 4.

5. (Optional) Uninstall Release 4 Message Queue.

   ---

   Note –

   Uninstall of Release 4 Message Queue is optional because Java ES versions 4 and 5 can coexist on a system.

   ---

To Verify Message Queue Upgrade

Start the Message Queue broker with -version option.

imqbrokerd -version

The outputs that indicate the Message Queue version are:

Release 5

Sun Java System Message Queue 3.7 UR1

Release 4

Sun Java System Message Queue 3 2005Q4 Version: 3.6 SP3

Post-Upgrade Tasks

If you have upgraded the web container and are using the Message Queue HTTP tunneling servlet, you may need to redeploy the servlet in the new web container. Otherwise, you do not need to redeploy the servlet after upgrading Message Queue. For more information about HTTP support, see the Sun Java System Message Queue 3.7 UR1 Administration Guide.

To Roll Back the Upgrade

1. Stop any running Release 5 Message Queue instances.

   If Message Queue is being used in an Application Server environment, shut down Application Server as well.

2. Stop any running brokers.

3. Migrate back the Release 4 Message Queue data, as listed in Table 5–2, to the Release 4 Message Queue installation location.

4. Start the Release 4 Message Queue.