This chapter describes how to upgrade Service Registry to Java ES 5 (Release 5): Service Registry 3.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 (Java ES Release 5 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
The following sections describe general aspects of Service Registry that affect upgrading to Java ES 5:
Release 5 Service Registry represents a minor release with respect to Java ES 2005Q4 (Release 4) Service Registry. It includes some improved functionality, updated interfaces, and selected bug fixes.
The following table shows the supported Service Registry upgrade paths to Java ES Release 5.
Table 7–1 Upgrade Paths to Java ES 5: Sun Java System Service Registry 3.1
Java ES Release |
Service Registry Release |
General Approach |
Reconfiguration |
---|---|---|---|
Release 4 |
Sun Java System Service Registry 3.0 2005Q4 |
Direct upgrade: Replace Release 4 with a fresh install and transfer registry data to Release 5. |
None |
The following table shows the type of data that could be impacted by an upgrade of Service Registry software.
Table 7–2 Service Registry Data Usage
Type of Data |
Location |
Usage |
---|---|---|
Installation Parameters |
ServiceRegistryR4-base\install\install.properties |
Configuration of Service Registry |
Trusted certificates |
ServiceRegistryR4-base\install\cacerts |
Certificates trusted by Service Registry that are not part of the Application Server installation |
Configuration data |
RegistryDomainR4-base\domains\registry\applications\j2ee-modules\soar\WEB-INF\classes\*.properties |
Configuration of Service Registry instance |
Registry/repository data |
RegistryDomainR4-base\3.0\data |
Database and user certificates |
Web interface configuration |
RegistryDomainR4-base\3.0\jaxr-ebxml |
Configuration of web interface |
Release 5 Service Registry is backwardly compatible with Release 4 Service Registry.
Service Registry dependencies on other Java ES components can affect 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–7.
Application Server. Service Registry depends on Application Server to provide a container for the Service Registry application and, in Release 5, to manage connections to the networked registry and repository database.
Java DB. Service Registry depends upon Java DB as the default database for storing services and the meta data describing them.
This section includes information about upgrading Service Registry from Release 4 to Release 5. The section covers the following topics:
When upgrading Release 4 Service Registry to Release 5, consider the following aspects of the upgrade process:
General Upgrade Approach. The upgrade is achieved by performing a fresh install of Release 5 Service Registry, migrating the Release 4 data and configuration to Release 5, and then removing Release 4 to conserve disk space.
Upgrade Dependencies. Service Registry has dependencies on a number of Java ES shared components, as listed in Table 1–7. All of these shared components are automatically upgraded to Release 5 by the Java ES installer when you perform an Service Registry upgrade.
In addition, Service Registry has a hard upgrade dependency on Application Server and Java DB.
Backward Compatibility. Release 5 Service Registry is backwardly compatible with Release 4.
Upgrade Rollback. A rollback of the Release 5 upgrade is achieved by reverting to Release 4 after restoring the saved database and configuration data.
This section describes how to perform a Java ES 4 Service Registry upgrade to Java ES 5. The section covers the following topics:
Before you upgrade Service Registry, perform the following procedures:
The Service Registry upgrade from Release 4 to Release 5 does not modify configuration data or the registry and repository database. You do not have to back up current data.
All Java ES components on a computer system and in a computing environment should be upgraded to Java ES Release 5. Service Registry has hard upgrade dependencies on a number of shared components and on Application Server.
When upgrading Service Registry dependencies, you should do so in the order below, before you upgrade Service Registry. Upgrade of shared components is normally achieved automatically by the Java ES installer.
Shared Components.Release 5 installer automatically installs all required shared components in the parallel path.
Application Server. Instructions for upgrading Application Server to Release 5 are provided in Chapter 6, Application Server
Obtain the user IDs, passwords, domain name, and port number for your Release 4 Service Registry.
Log in as administrator.
Stop the Release 4 Service Registry (Application Server) domain.
cd ServiceRegistryR4-base\install
ant -f build-install.xml appserver.domain.stop
Install Release 5 Service Registry.
Use the Configure Manually After Installation option to install Java ES 5 Service Registry. For Service Registry installation instructions, see the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.
Update the Release 5 install.properties file.
Perform post-install upgrade and configuration of the Release 5 Service Registry.
cd ServiceRegistryR5-base\install
ant -f build-install.xml upgrade
The upgrade utility creates a new Application Server domain for Service Registry, starts the Service Registry domain and deploys the Service Registry. Each Service Registry is associated with its own Application Server domain.
Stop the Release 5 Service Registry (Application Server) domain.
cd ServiceRegistryR5-base\install
ant -f build-install.xml appserver.domain.stop
Update the Release 5 configuration data files with changes made to the Release 4 configuration data files.
Start the Release 5 Service Registry (Application Server) domain.
cd ServiceRegistryR5-base\install
ant -f build-install.xml appserver.domain.start
Log in as administrator.
Stop and delete the Release 5 Service Registry (Application Server) domain.
cd ServiceRegistryR5-base\install
ant -f build-install.xml appserver.domain.stop appserver.domain.delete
Run the Release 5 uninstaller to uninstall Release 5 Service Registry.
Start the Release 4 Service Registry (Application Server) domain.
cd ServiceRegistryR4-base\install
ant -f build-install.xml appserver.domain.start