Component Dependencies
Some Java ES components cannot be installed and configured unless other components are installed and configured first. Dependencies occur for several reasons:
-
Some components cannot function unless certain other components are installed and configured. For example, the Communications Express interface needs data supplied by messaging and/or calendar services. The configuration procedure for Communications Express requires input of URLs that enable Communications Express to interoperate with already functioning messaging and calendar services. Because of this dependency, Messaging Server and/or Calendar Server must be installed and configured before Communications Express is installed and configured.
-
A number of components require an LDAP directory for authentication and authorization. The installation and configuration procedures for instances of these components require input of URLs for the LDAP directory service. Because of this dependency, Directory Server (or some other identity repository) must be installed before the components that use the LDAP directory service.
-
Some components modify the configuration of an existing component. For example, installing and configuring Access Manager modifies the LDAP directory schema. If your solution uses Access Manager, your installation plan must specify that an LDAP directory is installed and configured before Access Manager is installed.
-
A number of Java ES components are web applications. These components must be deployed into web containers to function. A web container must be installed and running before the components are installed and configured. You can use Web Server, Application Server, or some third-party web containers, but a web container must be present on the computer when you install the web application component.
Tip –If the solution uses Web Server or Application Server, the Java ES installer can install the web container and the web application component at the same time and automatically deploy the web application component to the web container.
-
Components may be installed in a high-availability cluster provided by Sun Cluster software. The Sun Cluster software must be installed and running before the other components are installed and configured. Additionally, the Sun Cluster Agents for the other components must be installed and configured.
Notice that some of these dependencies are solution-wide and some are local. You consider system-wide dependencies and local dependencies differently when you develop your installation plan. The difference is described in the following example:
The dependency of Access Manager on Directory Server is a system-wide dependency. When you install Access Manager, you supply a URL for a directory service provided by one or more instances of Directory Server. Once Directory Server is installed and configured, the directory service is available to all components in the solution. This type of dependency determines the solution-wide sequence for installing and configuring component instances: Directory Server is installed and configured before Access Manager. In your installation plan, solution-wide dependencies determine the overall sequence of installation and configuration steps.
The dependency of Access Manager on a web container is a local dependency. To satisfy this dependency, a web container must be installed on the computer that runs Access Manager. This web container, however, does not provide services for the entire solution. In a distributed solution, web containers are typically installed on multiple computers. Each web container supports a different component locally. Therefore, in a distributed solution there is no single location for web container installation, and there is no single point in the installation sequence for installing the web container.
To develop an installation plan for a solution, you analyze the deployment architecture that describes a solution and identify dependencies among the components. Your plan must install and configure components in a sequence that satisfies all of the dependencies. In general, you develop the overall installation sequence from the solution-wide dependencies. Then you consider the local dependencies that might exist on each computer.
The component dependencies are listed in Table 3–1. For more information about working with these dependencies, see the descriptions of the individual components in Developing an Installation Plan.
Table 3–1 Java ES Component Dependencies|
Dependencies |
Nature of Dependency |
Must be Local? |
|
|---|---|---|---|
|
Directory Server |
To store configuration data; to store and enable lookup of user data |
No |
|
|
J2EE web container, one of: -Application Server -Web Server -BEA WebLogic Server -IBM WebSphere Application Server |
Access Manager must be deployed to one of these web containers |
Yes |
|
|
Access Manager |
To provide Access Manager services |
No |
|
|
J2EE web container, one of: -Application Server -Web Server -BEA WebLogic Server -IBM WebSphere Application Server |
Access Manager SDK must be deployed to one of these web containers |
Yes |
|
|
Directory Server |
To provide a configuration directory |
No |
|
|
To provide reliable asynchronous messaging |
Yes |
||
|
To provide load balancing between Application Server instances |
Yes |
||
|
To store session state, which supports failover between Application Server instances |
Yes |
||
|
To store user data used for authentication and authorization |
No |
||
|
Prepares the LDAP directory for use with Calendar Server |
No |
||
|
Required if your solution uses single sign-on |
No |
||
|
To provide email notifications |
No |
||
|
To mange LDAP schema; to provision users of calendar services |
No |
||
|
-Application Server -Web Server |
Communications Express must be deployed to a web container |
Yes |
|
|
To store user data, such as address books |
No |
||
|
To prepare the LDAP directory for Communications Express |
No |
||
|
To provide authentication and authorization services and single sign-on; a local Access Manager SDK provides access to remote Access Manager |
Yes |
||
|
To provide underlying messaging service |
No |
||
|
To provide underlying calendar service |
No |
||
|
J2EE web container, one of: -Application Server -Web Server |
Delegated Administrator must be deployed to one of these web containers |
Yes |
|
|
Directory Server |
To store the LDAP data that Delegated Administrator works with |
No |
|
|
Directory Preparation Tool |
To prepare the LDAP directory for Delegated Administrator |
No |
|
|
Either Access Manager or Access Manager SDK |
To provide Access Manager services; a local Access Manager SDK provides access to a remote Access Manager |
Yes |
|
|
Directory Server |
Directory Preparation Tool prepares the directory for use with Java ES communications components |
Yes |
|
|
Administration Server |
To configure Directory Proxy Server |
No |
|
|
Directory Server |
To provide underlying LDAP directory services |
No |
|
|
Administration Server |
To configure Directory Server |
No |
|
|
High Availability Session Store |
None | ||
|
Directory Server |
To store user, conference room, and news channel data |
No |
|
|
Access Manager or Access Manager SDK (optional) |
To provide Access Manager services; a local Access Manager SDK provides access to a remote Access Manager |
Yes |
|
|
J2EE Web Container, one of: -Application Server -Web Server (required for delivery of Instant Messenger client resources) |
To support distribution and downloading of Instant Messenger client resources. |
Yes |
|
|
Calendar Server (optional, if calendar pop-ups feature is used) |
To support Calendar Server pop-ups |
No |
|
|
Messaging Server (optional, if offline delivery of instant messages is used) |
To support offline delivery of instant messages as email messages |
No |
|
|
Message Queue |
None | ||
|
Directory Server |
To store configuration data; To store and lookup user data for authentication and authorization |
No |
|
|
Administration Server |
To store configuration data in Directory Server configuration directory |
Yes |
|
|
Directory Preparation Tool |
To prepare the LDAP directory for Messaging Server |
No |
|
|
Access Manager (if your solution uses single sign-on) |
To provide single sign-on authentication and authorization service |
No |
|
|
Delegated Administrator (optional) |
To manage user and group data; to manage the directory schema |
No |
|
|
-Application Server -Web Server -BEA WebLogic Server -IBM WebSphere Application Server |
Portal Server must be deployed to one of these web containers |
Yes |
|
|
Directory Server |
To store user data used for authentication and authorization |
No |
|
|
Access Manager or Access Manager SDK |
To provide Access Manager services; a local Access Manager SDK provides access to a remote Access Manager |
Yes |
|
|
Communications Express |
To provide messaging and calendar channels for the portal desktop |
No |
|
|
Portal Server |
To provide the underlying portal service. |
Yes |
|
|
Either Access Manager or Access Manager SDK |
To provide Access Manager services; a local Access Manager SDK provides access to a remote Access Manager |
Yes |
|
|
Service Registry |
Application Server |
Yes |
|
|
Sun Cluster Software |
None | ||
|
Sun Cluster |
To recognize components installed on Sun Cluster nodes |
Yes |
|
|
Web Server |
To provide remote access to web applications |
Yes |
|
|
Web Server |
None |
- © 2010, Oracle Corporation and/or its affiliates