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.