This chapter describes how to upgrade Service Registry from Java ES 5 (Release 5) to Java ES 5 Update 1 (Release 5U1): Service Registry 3.1 Update 1.
This chapter covers the following topics
File locations in this chapter are specified with respect to directory paths referred to as ServiceRegistryR4-base and RegistryDomainR4-base (Java ES Release 4 Service Registry), and ServiceRegistryR5-base and RegistryDomainR5-base (Release 5 and 5U1 Service Registry). At least part of these paths might have been specified as installation directories when Service Registry was installed. If not, the Java ES installer assigned a default value. The default values of these directory paths are:
C:\Sun\ServiceRegistry
C:\Sun\ServiceRegistry
C:\Program Files\Sun\JavaES5\srvc-registry
C:\Program Files\Sun\JavaES5\srvc-registry
This section describes the following general aspects of Service Registry that impact upgrading to Java ES 5 Update 1 :
Release 5U1 Service Registry represents a maintenance release that fixes bugs in Release 5 Service Registry. Release 5 Service Registry was a minor feature release with respect to Release 4 Service Registry. It included some improved functionality, updated interfaces, and selected bug fixes.
The following table shows the supported Service Registry upgrade paths to Java ES 5.
Table 10–1 Upgrade Paths to Java ES 5 Update 1: Sun Java System Service Registry 3.1u1
Java ES Release |
Service Registry Release |
General Approach |
Reconfiguration |
---|---|---|---|
Release 5 |
Sun Java System Service Registry 3.1 |
Maintenance upgrade. Apply patches. |
None |
Release 4 |
Direct upgrade of Service Registry from Release 4 to Release 5U1 is not supported. This upgrade path is supported by first upgrading Release 4 Service Registry to Release 5 Service Registry and then upgrading Release 5 to Release 5U1. The information about upgrading Release 4 to Release 5 is documented in Sun Java ES 5 Upgrade Guide for Microsoft Windows. |
The following table shows the type of Service Registry data.
Table 10–2 Service Registry Data Usage
Type of Data |
Location |
Usage |
---|---|---|
Installation Parameters |
ServiceRegistryR-base\install\install.properties |
Configuration of Service Registry |
Trusted certificates |
ServiceRegistryR-base\install\cacerts |
Certificates trusted by Service Registry that are not part of the Application Server installation |
Configuration data |
RegistryDomainR-base\domains\registry\applications\j2ee-modules\soar\WEB-INF\classes\*.properties |
Configuration of Service Registry instance |
Registry/repository data |
RegistryDomainR-base\3.1\data |
Database and user certificates |
Web interface configuration |
RegistryDomainR-base\3.1\jaxr-ebxml |
Configuration of web interface |
Release 5U1 Service Registry is backwardly compatible with Release 5 Service Registry.
Service Registry dependencies on other Java ES components can impact the procedure for upgrading and reconfiguring Service Registry software. Changes in Service Registry interfaces or functions, for example, could require upgraded version of components upon which Service Registry depends. The need to upgrade such components depends upon the specific upgrade path.
Service Registry has dependencies on the following Java ES components:
Shared Components. Service Registry has dependencies on specific Java ES shared components, as listed in Table 1–8.
Application Server. Service Registry depends on Application Server to provide a container for the Service Registry application and, in Release 5 and 5U1, to manage connections to the networked registry and repository database.
Java DB. Service Registry has a mandatory dependency on Java DB as the default database for storing services and the meta data describing them.
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