The example installation sequences in this chapter are intended to provide high-level guidelines for some common Java ES installations. These are not literal procedures, but instead 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. For the most part, the sequences in this chapter are based on the relationships among the components as shown in Sun Java Enterprise System 2005Q4 Installation Planning Guide
The Calendar-Messaging Schema 1 Example is the only example based on LDAP Schema 1. All other examples in this chapter are based on Schema 2.
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
Installation goes smoothly if any incompatible versions of Java ES components are identified and removed or upgraded before starting the installer.
To upgrade components that are already on your local host, refer to Sun Java Enterprise System 2005Q4 Upgrade Guide.