Sun Java Enterprise System 5 Installation Guide for UNIX

How to Use This Chapter

The single-session examples describe typical steps for installing one or a number of Java ES product components on a single host in a single installation session. All other examples in this chapter describe situations where multiple installation sessions are performed on multiple hosts, for a variety of solutions. For the most part, the sequences in this chapter are based on the relationships among the product components as shown in Sun Java Enterprise System 5 Installation Planning Guide.

At component selection, the Java ES installer identifies incompatible versions of components as well as unmet requirements. You receive warning messages that identify the problem and tell you what you need to do. Many of these messages tell you about requirements that are not yet met. Other messages tell you that incompatible versions of some or all of the components you are trying to install are already on the local host. You can use the Java ES installer to identify components that are already on your local host. For instructions, refer to When Incompatible Components Are Installed.

Tip –

Installation goes most smoothly if any incompatible versions of Java ES components are identified and removed or upgraded before starting the installer.

The following table describes some common situations that might influence the sequence in which you should install the components, or the order in which tasks should be performed on multiple hosts or in multiple installation sessions. The left column lists the situation, and the right column explains how to handle the situation.

Table 2–1 Installation Sequence Guidelines



Monitoring is included. 

Monitoring Console cannot be run on the same host as the Java ES product components that it monitors. Therefore, Monitoring Console should be installed on another host. 

Installation-time configuration is not possible for all components. 

The following components can be installed in a Configure Now installation, but configuration cannot be done during installation: Sun Cluster components, Monitoring Console, and Service Registry. During installation, you will receive a message telling you to configure after installation. 

Upgrading components is required. 

You might receive messages asking you to remove or upgrade product components that are already on the host. On Solaris OS, some bundled components (Application Server, Message Queue, and HADB), can be upgraded during installation. For all other components, refer to the upgrading procedures in the Sun Java Enterprise System 5 Upgrade Guide for UNIX

Solaris 10 zones are used. 

In a Solaris 10 zones environment, shared components must be installed separately in the global zone before installing into a local zone. Message Queue can only be installed in the global zone, after which it is propagated to all non-global zones. Refer to Solaris 10 Zones Examples for further guidelines.

Sun Cluster software is included. (Solaris OS only) 

If Sun Cluster software is part of your deployment, you must perform a precise series of tasks before installing any Java ES product components. Java ES components that can be configured for Sun Cluster are Application Server, Directory Server, HADB, Message Queue, and Web Server. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.

Remote components are used. 

If you are using a remote product component to fulfill dependencies, the remote product component must be installed and running before installing any Java ES product components that depend on it. 

Third-party components are used. 

If you are using a third-party product as your web container, the third-party product must be installed and running before installing any Java ES product component that depends on it. 

Note: HP-UX does not support third-party web containers. For Configure Now, Linux only supports the BEA WebLogic third-party container. 

Access Manager modes 

When you are installing Access Manager with Portal Server, you can select either Realm (7.x) mode or Legacy (6.x) mode for Access Manager (ignoring the installer message that says Legacy mode is required for Portal Server). However, Portal Server supports Realm mode only if Access Manager is configured with Directory Server, with AM SDK configured for the data store.