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:
Message Queue core and C-API
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.
Choose Start > Settings > Control Panel.
Select Administrative Tools.
Select Message Queue Broker from the Services list.
You can use one of the following methods to stop the service:
Right-click and select Stop.
Click the Stop Service icon.
Select Stop from the Action Menu.
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.