Sun Java Enterprise System 5 Update 1 Upgrade Guide for Microsoft Windows

Release 5 Message Queue 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:

Pre-Upgrade Tasks

Before you upgrade Message Queue, perform the tasks described below.

Verify Current Version Information

Verify the current version of Message Queue before you upgrade.

ProcedureTo Verify Current Version Information

  1. Start the Message Queue broker with -version option.

    imqbrokerd -version

    The outputs that indicate the Message Queue version are:

  2. The outputs that indicate the Message Queue version are:

    Release 5U1

    Sun Java System Message Queue 3.7 UR2

    Release 5

    Sun Java System Message Queue 3.7 UR1

Upgrade Message Queue Dependencies

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.

Back Up Message Queue Data

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.

Upgrading Release 5 Message Queue

This section discusses considerations that impact the upgrade procedure for Message Queue, followed by a description of the procedure itself.

Upgrade Considerations

The upgrade of Message Queue software to Java ES 5 Update 1 takes into account the following considerations:

Table 8–3 Patches to Upgrade Message Queue on Windows

Description 

Patch ID [Patch revision numbers are the minimum required for upgrade to Release 5U1. If newer revisions become available, use the newer ones instead of those shown in the table.]

Message Queue core and C-API 

125066–03 

Upgrade Procedure

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.

ProcedureTo Upgrade Message Queue to Java ES 5 Update 1

  1. Stop any Message Queue client applications that are running.

    In default Java ES 5 installation these are the Application Server instances.

  2. Stop any Message Queue brokers that are running.

    1. Choose Start > Settings > Control Panel.

    2. Select Administrative Tools.

    3. Select Services.

    4. 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.

      • Enter the following command.

        imqcmd shutdown bkr [ -b hostName:port ]

        The system prompts you to provide the user name and the password. The default user name is set to admin and the default password is also set to admin.

  3. Make sure you have upgraded any Java ES components upon which Message Queue has hard upgrade dependencies (see Upgrade Message Queue Dependencies.

  4. 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.

  5. 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.


    Note –

    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.


  6. Verify the patch log file.

    The log file is found at: %TEMP%\SUNJAVAES_<patch-id>.log

  7. 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.

  8. 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


    Note –

    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.


Verifying the Upgrade

You can verify successful upgrade of Message Queue as follows:

  1. Start the Message Queue broker with -version option.

    MessageQueue-base\bin\imqbrokerd.exe -version

The messages that indicate the Java ES release version are:

Release 5U1

Sun Java System Message Queue 3.7 UR2

Release 5

Sun Java System Message Queue 3.7 UR1

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.

Rolling Back the Upgrade

  1. Stop any running Release 5U1 Message Queue brokers and Message Queue service from Service Control Panel.

  2. Execute Uninstall_patch-id.bat

  3. Start the Message Queue broker or service from Service Control Panel.

  4. Start the Release 5 Message Queue.

  5. Verify the Message Queue version with the following command.imqbrokerd -version