Overview of Service Registry Upgrade

The following sections describe general aspects of Service Registry that affect upgrading to Java ES 5:

• About Java ES 5 Service Registry

• Service Registry Upgrade Roadmap

• Service Registry Data

• Service Registry Compatibility Issues

• Service Registry Dependencies

About Java ES 5 Service Registry

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.

Service Registry Upgrade Roadmap

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

Service Registry Data

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

Service Registry Compatibility Issues

Release 5 Service Registry is backwardly compatible with Release 4 Service Registry.

Service Registry Dependencies

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.