Sun Java Enterprise System 5 Update 1 Upgrade Guide for Microsoft Windows

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.

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

Dependencies on Shared Components

Table 1–8 shows the dependencies of Release 5U1 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. The hard upgrade dependencies for Release 5 to Release 5U1 upgrades are marked “H,” and soft upgrade dependencies are marked “S.”

Within the matrix of the following table

Table 1–8 Shared Component Dependencies of Release 5U1 Product Components


Shared Component	AM	AS	DPS	DS	DS Console	HADB	JAVADB	MQ	MC	PS	PSRA	SR	WPS	WS
ANT		S							S	H	H	H
ACL	S											H
BDB	S
C AC	H	S	H	H	H				S
FIS
ICU		S	H	H						S			S	S
IM-SDK										S
Java SE	S	S	H	H	H	S	H	S	S	H	S	H	S	S
JAF	S	S								S	S	H
JATO	S	S							S	S
JavaHelp^TM	S	S						S	S					S
JavaMail^TM	S	S								S	S	H	S
JAXB	S	S												S
JAXP	S	S								S	S	H		S
JAXR	S	S										H		S
JAX-RPC	S	S										H		S
JAXWS														S
JCAPI
JDMK	H	S	H	H	H				S					S
JSS	S									S	S		S	S
JSTL
KTSE										S			S	S
LDAP C SDK	H		H	H									S	S
LDAP J SDK	S
MA Core	S
MFWK	H			H					H
NSPR	S	S	H	H				H	S	S	S		S	H
NSS	S	S	H	H				H	S	S	S		S	H
SAAJ	S	S								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 5U1 product component has a hard upgrade dependency on another product component, the dependent component can only be successfully upgraded and used as intended 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 used 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 5U1 product components, the second column shows other Java ES components upon which a Release 5U1 component has a dependency relationship, the third column provides the Java ES release versions that support the Release 5U1 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 or whether other third-party products can support the dependency.

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

Table 1–9 Java ES Product Component Dependencies


Product Components	Dependency [ For each product component, dependencies are listed in the order that they would normally be upgraded.]	Java ES Release	Nature of Dependency	Characteristics
Access Manager	Directory Server	4–5 & 5U1	Mandatory: Stores configuration data and enable lookup of user data
	Java 2 Enterprise Edition (J2EE^TM) web container:		Mandatory: Provides web container runtime services	Local only Also supported: -Weblogic [BEA Weblogic Server] -WebSphere [IBM WebSphere Application Server]
	Web Server	4–5 & 5U1
	Application Server	4–5 & 5U1
Access Manager SDK	Access Manager	4–5	Mandatory: Provides Access Manager services
	J2EE web container:		Mandatory: Provides web container runtime services	Local only Also supported: –Weblogic -WebSphere
	Application Server	4–5 & 5U1
	Web Server	4–5 & 5U1
Access Manager Distributed Authentication	Access Manager	4–5	Mandatory: Provides Access Manager services
	J2EE web container:		Mandatory: Provides web container runtime services	Local only Also supported: -Weblogic -WebSphere
	Application Server	4–5 & 5U1
	Web Server	4–5 & 5U1
Access Manager Session Failover	Access Manager	5	Mandatory: Provides Access Manager services
	J2EE web container:		Mandatory: Provides web container runtime services	Local only Also supported: -Weblogic -WebSphere
	Application Server	4–5 & 5U1
	Web Server	4–5 & 5U1
	Message Queue	4–5 & 5U1	Mandatory:Provides reliable asynchronous messaging
Application Server	Message Queue	5 & 5U1	Mandatory: Provides reliable asynchronous messaging	Local only
	High Availability Session Store	5	Mandatory: Stores session state needed to support failover between instances	Local only
	Java DB	5 & 5U1	Mandatory: Stores session state needed to support failover between instances	Local only
	Web Server	4–5 & 5U1	Optional: Provides load balancing between instances	Yes
Directory Proxy Server	Directory Server	4–5 & 5U1	Co-dependency: Results in improved security and performance for directory requests. Supplies data to Directory Proxy Server
Directory Server	Directory Proxy Server	4–5 & 5U1	Co-dependency: Results in improved security and performance for directory requests. Distributes load and caches data to Directory Server
High Availability Session Store (HADB)	None
Java DB	None
Message Queue	Directory Server	4–5 & 5U1	Optional: Stores administered objects and user data
	J2EE web container:		Optional: Supports HTTP transport between client and Message Queue broker
	Application Server	4–5 & 5U1
	Web Server	4–5 & 5U1
	Java DB	5 & 5U1	Optional: Stores persistent messages.	Local only
Monitoring Console	None
Portal Server	Directory Server	4–5 & 5U1	Mandatory: Stores and enables lookup of user profiles
	J2EE Web Container:		Mandatory: Provides web container runtime services	Local only
	Application Server	4–5 & 5U1
	Web Server	4–5 & 5U1
	Access Manager or Access Manager SDK	4–5	Mandatory: Provides authentication and authorization services, single sign-on	Local only (If Access Manager is remote, Access Manager SDK must be used locally
	Portal Server Secure Remote Access	5	Optional: Provides secure remote access through the Gateway, Rewriter Proxy, and Netlet Proxy components
	Server Registry Client	5 & 5U1	Mandatory: Provides libraries needed for compilation
	Java DB	5 & 5U1	Optional: Provides support for several portlet applications
Portal Server Secure Remote Access Gateway	Portal Server	5	Mandatory: Supports Gateway functionality
	Access Manager or Access Manager SDK	4–5	Mandatory: Provides authentication and authorization services, single sign-on	Local only (If Access Manager is remote, Access Manager SDK must be used locally)
	Directory Server	4–5 & 5U1	Mandatory: Stores and enables lookup of user data
Rewriter Proxy	Portal Server	5	Mandatory: Supports Rewriter Proxy functionality
Netlet Proxy	Portal Server	5	Mandatory: Supports Netlet Proxy functionality
Service Registry Deployment	Application Server	5 & 5U1	Mandatory: Provides container runtime services	Local only
	Java DB	5 & 5U1	Mandatory: Provides default database for storing services and related meta data	Local only
	Service Registry Client	5U1	Mandatory: Provides required client libraries	Local only
Web Proxy Server	Directory Server	4–5 & 5U1	Optional: Provides LDAP-based authentication
Web Proxy Server	Web Server	4–5 & 5U1	Co-dependency: Results in improved security and performance for HTTP requests. Supplies data to Web Proxy Server	Also supported: -Weblogic –WebSphere
Web Server	Directory Server	4–5 & 5U1	Optional: Provides LDAP-based authentication
Web Server	Web Proxy Server	4–5 & 5U1	Co-dependency: Results in improved security and performance for HTTP requests. Distributes load and caches data from Web Server