Sun Java Enterprise System 5 Installation Guide for Microsoft Windows

How to Use This Chapter

The example installation sequences in this chapter provide high-level guidelines for some common Java ES installations. These procedures provide the sequential steps required to implement particular deployment scenarios.

The single-session examples describe typical steps for installing one or a number of Java ES components on a single host in a single installation session. An evaluation example is included. The remaining examples describe situations where multiple installation sessions are performed on multiple hosts, for a variety of solutions. The sequences in this chapter are based on the relationships among the Java ES 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. Warning messages identify the problem and tell you what you need to do. These message also tell you about incompatible versions of some or all of the components that are already installed on the local host. You can also use the Java ES installer to identify already installed components.

Tip –

Remove or upgrade any incompatible versions of Java ES components before starting the installer.

Table 2–1 Installation Sequence Guidelines


Installation Guideline Topic	Description
Monitoring	Monitoring Console cannot be run on the same host as Java ES components that it monitors. Therefore, Monitoring Console should be installed on another host in a separate installation session.
Installation-time configuration	The following components can be installed in a Configure Automatically During installation, but configuration cannot be performed during installation: Monitoring Console and Service Registry.
Remote component	If you are using a remote Java ES component to fulfill dependencies, the remote Java ES component must be installed and running before installing any Java ES components that depend on the remote component.

Access Manager modes	You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Portal Server. Access Manager Realm (7.x) installation type can only be used if you are not installing Portal Server.