Java ES Component Dependencies

One of the most important considerations in an upgrade plan is the dependencies between the various Java ES components in your deployed system. The sequence in which you perform the component upgrades is affected by the nature of the dependencies between them.

• Dependencies on Shared Components

• Dependencies On Product Components

Each of these factors is discussed briefly in the following sections.

Dependencies on Shared Components

Table 1–7 shows the dependencies of Release 5 product components on Java ES shared components. The abbreviations for product components in the table are taken from Table 1–1. The abbreviations for shared components are spelled out in Table 1–2.

Within the matrix of the following table hard upgrade dependencies for Release 4 to Release 5 upgrades are marked “H,” and soft upgrade dependencies are marked “S.”

Table 1–7 Shared Component Dependencies of Java ES 5 Product Components

Shared Component	AM	AS	DPS	DS	MQ	SR	WS	WPS
ANT		S				H
ACL	S					H
BDB	S
Common Agent Container	H	H	H	H
ICU		S	H	H			S	S
J2SE	S	S	H	H	S	H	S	S
JAF	S	S				H
JATO	S	S
JavaHelp	S	S			S		S
JavaMail	S	S				H	S
JAXB	S	S					S
JAXP	S	S				H	S
JAXR	S	S				H	S
JAX-RPC	S	S				H	S
JAXWS							S
JCAPI
JDMK	H	S	H	H			S
JSS	S						S	S
KTSE							S	S
LDAP C SDK	H			H			S	S
LDAP J SDK	S
MA Core	S
MFWK	H
NSPR	S	S	H	H	H		H	S
NSS	S	S		H	H		H	S
SAAJ	S	S				H
SASL				H			S	S
SJWC	S	S	H	H
WSCL	S	S				H	S
XWSS						H

Dependencies On Product Components

Dependencies on product components fall into two general categories: runtime dependencies and configuration dependencies.

• Runtime Dependencies. The functioning of a software system is based on the interactions between its deployed components. The infrastructure dependencies between Java ES components are discussed in the Java Enterprise System 5 Technical Overview. If a Release 5 product component has a hard upgrade dependency on another product component, the dependent component con only be successfully upgraded and used if the component upon which it depends is also upgraded.

• Configuration Dependencies. In some cases a Java ES component must be installed, configured, and running in order for another component to be configured. For example, a Directory Server user directory must be running for an Access Manager service to be registered. Component upgrade procedures often involve reconfiguration of upgraded components or migration of configuration data. Configuration dependencies can impact the sequence of upgrade procedures.

For runtime dependencies, the relationship between product components can be of the following three types:

• Mandatory. The component cannot operate without the supporting component.

• Optional. The component can operate without the supporting component, but a subset of its functionality requires the supporting component.

• Co-dependency. Both components can operate without the support of the other, but the components together can provide certain enhanced functionality or performance.

The following table shows the dependencies between the Java ES product components listed in Table 1–1. The information can be used to determine the hard upgrade dependencies that impact your upgrade plan.

The first column alphabetically lists Release 5 product components, the second column shows other Java ES components upon which a Release 5 component has a dependency relationship, the third column provides the Java ES release versions that support the Release 5 dependency, the fourth column characterizes the dependency relationship, and the last column indicates special characteristics of the dependency, such as whether the supporting component must be local as opposed to remote or whether other third-party products can support the dependency.

If a product component you are upgrading to Release 5 has a dependency on Release 5 of a supporting component then the supporting component represents a hard upgrade dependency: the supporting component must also be upgraded to Release 5.

Table 1–8 Java ES Product Component Dependencies

Product Components	Dependencies	Nature of Dependencies	Must be Local
Access Manager	Directory Sever	Mandatory: Stores configuration data and enable lookup of user data
	Java 2 Enterprise Edition (J2EETM) web container: Application Server Web Server	Mandatory: Provides web container runtime services	Yes
Access Manager SDK	Access Manager	Mandatory: Provides Access Manager services
	J2EE web container:  Application Server Web Server	Mandatory: Provides web container runtime services	Yes
Access Manager Distributed Authentication	Access Manager	Mandatory: Provides Access Manager services
	J2EE web container:  Application Server Web Server	Mandatory: Provides web container runtime services	Yes
Access Manager Session Failover	Access Manager	Mandatory: Provides Access Manager services
	J2EE web container:  Application Server Web Server	Mandatory: Provides web container runtime services	Yes
Application Server	Message Queue	Mandatory: Provides reliable asynchronous messaging	Yes
	Web Server	Optional: Provides load balancing between instances	Yes
	High Availability Session Store	Mandatory: Stores session state needed to support failover between instances	Yes
Directory Proxy Server	Directory Server	Co-dependency: Results in improved security and performance for directory requests. Supplies data to Directory Proxy Server	No
Directory Server	Directory Proxy Server	Co-dependency: Results in improved security and performance for directory requests. Distributes load and caches data to Directory Server
Message Queue	Directory Server	Optional: Stores administered objects and persistent data
	J2EE web container:  Application Server Web Server	Optional: Supports HTTP transport between client and Message Queue broker
Service Registry	Application Server	Mandatory: Provides container runtime services	Yes
	Java DB	Mandatory: Provides default database for string services and related meta data	Yes
	Service Registry Client	Mandatory: Provides required client libraries	Yes
Web Proxy Server	Directory Server	Optional: Provides LDAP-based authentication
	Web Server	Co-dependency: Results in improved security and performance for HTTP requests. Supplies data to Web Proxy Server	Yes
Web Server	Directory Server	Optional: Provides LDAP-based authentication
	Web Proxy Server	Co-dependency: Results in improved security and performance for HTTP requests. Distributes load and caches data from Web Server