This section includes information about upgrading Service Registry from Java ES 5 to Java ES 5 Update 1 . The section covers the following topics:
When upgrading Release 5 Service Registry to Release 5U1, consider the following aspects of the upgrade process:
General Upgrade Approach. The upgrade is achieved by patching Release 5 Service Registry.
Upgrade Dependencies. Service Registry 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 Service Registry.
Backward Compatibility. Release 5UI Service Registry is backwardly compatible with the Release 5 version.
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:
Before you upgrade Web Server, perform the tasks described below.
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.
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.
This section discusses considerations that impact the upgrade procedure for Web Server, followed by a description of the procedure itself.
The upgrade of Service Registry software to Java ES Release 5U1 takes into account the following considerations:
In a deployment architecture in which there are multiple instances of Service Registry running on a single computer (all corresponding to the same installed Service Registry image), you only have to upgrade the Service Registry image once.
In a maintenance upgrade, you do not have to migrate schema, configuration, security or user data.
The Release 5U1 Service Registry upgrade patches for Windows are shown in the following table:
The procedure documented below applies to Service Registry instances residing locally on the computer where the upgrade is taking place.
Log in as administrator.
Stop the Service Registry (Application Server) domain.
ServiceRegistryR5–base\install\ant -f build-install.xml appserver.domain.stop
Make sure you have upgraded any Java ES components upon which Service Registry has hard upgrade dependencies (see Upgrade Service Registry Dependencies).
Obtain the required Service Registry Release 5U1 upgrade patches, based on Table 10–3.
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.
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.
Upgrade and configure the Release 5U1 Service Registry instance.
ServiceRegistryR5–base/install
ant -f build-install.xml upgrade.jes5.to.jes5u1
Start the Release 5U1 Service Registry (Application Server) domain.
ant-f build-install.xml appserver.domain.start appserver.deploy.test
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.
There are no post-upgrade tasks beyond the steps described in Upgrade Procedure and Upgrade Considerations.
Log in as administrator.
Stop the Service Registry (Application Server) domain.
ServiceRegistryR5–base/install
ant -f build-install.xml appserver.domain.stop
Double-click uniinstall_patch-id.bat to uninstall the patch.
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