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

Release 5 Service Registry Upgrade

This section describes how to perform an upgrade of Service Registry from Java ES Release 5 to Release 5U1. This section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Web Server, perform the tasks described below.

Upgrade Service Registry 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 Service Registry has hard upgrade dependencies on Application Server and Java DB, so these should be upgraded before upgrading Service Registry. Service Registry also requires that Windows Installer patch (126910–02) is already applied.

Backing Up Service Registry Data

The Service Registry upgrade from Release 5 to Release 5U1 does not modify the Release 5 configuration data. You do not need to back up current data.

Upgrading Release 5 Service Registry

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

Upgrade Considerations

The upgrade of Service Registry software to Java ES Release 5U1 takes into account the following considerations:

Table 10–3 Patches1 to Upgrade Service Registry 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.]

Service Registry core 

125443–09 

Service Registry Localization 

The localized patch files are delivered within the core patch. 

Upgrade Procedure

The procedure documented below applies to Service Registry instances residing locally on the computer where the upgrade is taking place.

ProcedureTo Upgrade Service Registry to Java ES 5 Update 1

  1. Log in as administrator.

  2. Stop the Service Registry (Application Server) domain.

    ServiceRegistryR5–base\install\ant -f build-install.xml appserver.domain.stop

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

  4. Obtain the required Service Registry Release 5U1 upgrade patches, based on Table 10–3.

  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.


    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. Upgrade and configure the Release 5U1 Service Registry instance.

    ServiceRegistryR5–base/install

    ant -f build-install.xml upgrade.jes5.to.jes5u1

  9. Start the Release 5U1 Service Registry (Application Server) domain.

    ant-f build-install.xml appserver.domain.start appserver.deploy.test

Verifying the Upgrade

You can verify successful upgrade of Service Registry with the help of the utility ListJavaESPatches.exe as described in the procedure to upgrade Service Registry. See Upgrade Procedure.

Post-Upgrade Tasks

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure and Upgrade Considerations.

Rolling Back the Upgrade

  1. Log in as administrator.

  2. Stop the Service Registry (Application Server) domain.

    ServiceRegistryR5–base/install

    ant -f build-install.xml appserver.domain.stop

  3. Double-click uniinstall_patch-id.bat to uninstall the patch.

  4. Execute the following command.

    ant -f build-install.xml appserver.domain.start appserver.undeploy appserver.deploy appserver.deploy.fix install.l10n appserver.domain.stop appserver.domain.start appserver.deploy.test