This section includes information about upgrading Message Queue from Java ES 5 to Java ES 5 Update 1 . The section covers the following topics:
When upgrading Release 5 Message Queue to Release 5U1, consider the following aspects of the upgrade process:
General Upgrade Approach. The upgrade is achieved by patching Release 5 Message Queue.
Upgrade Dependencies. Message Queue has dependencies on a number of Java ES shared components, (see Table 1–8), none of which need to be upgraded when you perform a maintenance upgrade of Message Queue. However, Message Queue requires that Windows Installer patch (126910–02) is already applied.
Backward Compatibility. Release 5U1 Message Queue is backwardly compatible with the Release 5 version.
Upgrade Rollback. You can do a rollback of the Release 5 upgrade by reverting to the previous version, which is left intact by the upgrade.
This section describes how to perform an upgrade of Message Queue from Java ES 5 to Java ES 5 Update 1. The section covers the following topics:
Before you upgrade Message Queue, perform the tasks described below.
Verify the current version of Message Queue before you upgrade.
Start the Message Queue broker with -version option.
imqbrokerd -version
The outputs that indicate the Message Queue version are:
The outputs that indicate the Message Queue version are:
Sun Java System Message Queue 3.7 UR2
Sun Java System Message Queue 3.7 UR1
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Release 5U1 Message Queue has no hard upgrade dependencies, so upgrade of shared components is optional.
It is always a good practice to back up application data in a production environment before performing an upgrade. Note the location of the persistent store for the dynamic application data indicated in Table 8–2.
This section discusses considerations that impact the upgrade procedure for Message Queue, followed by a description of the procedure itself.
The upgrade of Message Queue software to Java ES 5 Update 1 takes into account the following considerations:
In a deployment architecture in which there are multiple instances of Message Queue running on a single computer (all corresponding to the same installed Message Queue image), you only have to upgrade the Message Queue image once.
In a maintenance upgrade, you do not have to migrate configuration, security and user data.
The Release 5U1 Message Queue upgrade patches for Windows OS are shown in the following table:
The procedure documented below applies to Message Queue instances residing locally on the computer where the upgrade is taking place. Back up application data in a production environment before performing an upgrade. For Message Queue data locations, refer Table 8–2.
Stop any Message Queue client applications that are running.
In default Java ES 5 installation these are the Application Server instances.
Stop any Message Queue brokers that are running.
Make sure you have upgraded any Java ES components upon which Message Queue has hard upgrade dependencies (see Upgrade Message Queue Dependencies.
Obtain the required Message Queue Release 5U1 upgrade patches, based on Table 8–3.
To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to \workingDirectory.
Install the patch.
Installation is generally performed by running patch-id.exe, however, be sure to consult the README.patch-id file in the patch directory for installation instructions and for limitations when updating the Windows 2000 service registry.
If you are prompted to restart the system, select No. Wait till the patch installation process is completed and then restart and re-login as the same user to complete the patch installation.
Verify the patch log file.
The log file is found at: %TEMP%\SUNJAVAES_<patch-id>.log
Verify the patch installation with the utility ListJavaESPatches.exe.
Run ListJavaESPatches.exe and check that the output includes the patch id of the patch that you have installed in Step 5. For more information, see Identifying Installed Java ES Patches.
Start the Message Broker or Service from Service Control Panel.
Alternatively, you can start the Message Broker from the command line:
net start MQ3.7UR1_Broker
Due to a limitation of the Windows Patching System, the service name MQ3.7UR1_Broker does not get updated during the application of the patch.
You can verify successful upgrade of Message Queue as follows:
Start the Message Queue broker with -version option.
MessageQueue-base\bin\imqbrokerd.exe -version
The messages that indicate the Java ES release version are:
Sun Java System Message Queue 3.7 UR2
Sun Java System Message Queue 3.7 UR1
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.
Stop any running Release 5U1 Message Queue brokers and Message Queue service from Service Control Panel.
Execute Uninstall_patch-id.bat
Start the Message Queue broker or service from Service Control Panel.
Start the Release 5 Message Queue.
Verify the Message Queue version with the following command.imqbrokerd -version