Java ES Installer Behavior
This section describes some behaviors of the Java ES installer that affect installation planning.
The Installer is Local
The Java ES installer installs component software on one computer at a time. For most solutions, this means the installer runs more than once. The installation plan must indicate how many times to run the installer. This section describe how to analyze a deployment architecture and determine how many times the installer is run to install and configure a solution.
A few solutions are installed on one computer only, and the installation plans for these solutions provide procedures for running the installer runs only once. The solutions that require running the installer only once are the following:
-
A number of component are installed on one computer to evaluate Java ES features
-
One component instance is added to an established solution. This includes adding component instances that have dependencies on existing components.
Most solutions are distributed across several computers. Installation plans for these solutions must describe running the installer multiple times to install and configure the complete solution. To analyze these solutions, use the following guidelines:
-
Most combinations of components on a computer can be installed by running the installer once. This is particularly true if the installer runs in configure now mode, because in configure now mode, the installer can install both a web container and the component that runs in the web container. In these cases, the installation plan describes running the installer once on the computer and selecting all of the components specified for the computer.
Tip –Some components cannot be configured by the installer, even in configure now mode. When these components are installed on a computer, the configuration process is completed by running a configuration wizard for each component. When these components are installed in combination with components that are configured by the installer, the installer runs first. After the installer runs, the process is completed by running the configuration wizards for those components not configured by the installer. In these cases, the installation plan must describe running the installer and the correct sequence for running the configuration wizards.
-
Some combinations of components can only be installed by running the installer more than once on a computer. These combinations include the following:
-
Some component combinations that include a web container. If Web Server or Application Server is installed in configure later mode, an instance of Web Server or Application Server must be configured and verified before the component that runs in the web server can be installed. If the solution uses third-party web containers, the web container must be installed with its own installer, started, and verified, before the Java ES components are installed. The installation plan must describe running the installer multiple times on each computer.
-
Component combinations that use Sun Cluster software. If the components installed into the cluster are installed on a cluster file system, the Sun Cluster software must be installed and the cluster file system created before other components can be installed in the cluster nodes. The installation plan must describe running the installer multiple times on each computer.
-
The purpose of this section is to introduce the idea that installation plans must sometimes describe running the installer and the configuration wizards on one computer, or running the installer multiple times on one computer. For more information on the actual installation procedures for different component combinations, see Developing an Installation Plan.
Installer Operating Modes
The installer runs in two different modes, known as configure now and configure later. The modes differ in the following ways:
-
In configure now mode, the installer configures runnable instances of some, but not all, components. The components configured in configure now mode can be started and verified as soon as the installer completes. Runnable instances of the remaining components are created after the installer runs, by running component product configuration wizards. For components configured by the installer, the installer requires input of the configuration values, and the installation plan lists the configuration values as part of the instructions for running the installer. For components configured after the installer runs, the configuration values are required input for the configuration wizards, and the configuration values are listed as part of the instructions for running the configuration wizards.
Tip –A significant feature of configure now mode is its ability to install a web container and components that run in the web container at the same time. The installer automatically deploys the components to the web container.
-
In configure later mode, the installer copies component software files to the computer but does not create runnable instances. Instances are created after the installer runs, by running the component product configuration wizards. The configuration values are required input for the configuration wizards, and the configuration values are listed as part of the instructions for running the configuration wizards.
The selected configuration option applies to an entire installation session. If you need to select different configuration options for some components, you might need to run additional installation sessions.
Installer Compatibility Checking
The installer performs some dependency and compatibility checking. Can only check what is installed locally. For example, if your solution is using a remote Directory Server instance, the installer cannot check whether the remote Directory Server is compatible with the Access Manager you are installing. If you are installing and configuring an all-new solution. It might be an issue if you are adding a new component to an established solution, or building a Sun Java System around existing components. For example, if you are already using Directory Server, and you are building a solution using Access Manager, Messaging Server, Calendar Server, and Communications Express around the existing Directory Server, compatibility among the components becomes an issue.
-
Component Dependency Checking. The Java ES installer will prevent you from omitting components that are required by other components you have selected for installation, but only on the local host. In a distributed solution, the installer does not check the remote host to verify that the remote component is there. You are responsible for verifying that the remote component is compatible and in the proper running state.
-
Upgrading. The Java ES installer does not perform any component upgrading except when Application Server and Message Queue have already been installed with the Solaris OS. In this case, the installer asks if you want to upgrade Application Server and Message Queue during installation.
The Java ES installer does perform upgrade of shared components. For more information of this topic, see Surveying Existing Hosts in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.
Other Installation Issues
This section lists a number of specific issues that occur in some solutions with references to detailed information.
Table 3–3 Installation Issues to Consider|
Solution Requires |
Guidelines or Instructions |
|---|---|
|
Using Solaris 10 zones |
If you will be installing into Solaris 10 zones, refer to Solaris 10 Zones in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX. |
|
Using Directory Server encryption |
Configuring LDAPS (SSL over LDAP) on the Directory Server instance Note: If Directory Server encryption is a requirement, Administration Server must be installed when Directory Server is installed. |
|
Third-party web containers (BEA WebLogic Server or IBM WebSphere Application Server) can be used with Portal Server and Access Manager. These containers must be installed and running before installing any Java ES components that depend on them. To use a third-party web container for Access Manager SDK, you must configure Access Manager SDK manually after installation. See Access Manager SDK With Container Configuration Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX Note: Portal Server can only use third-party web containers on Solaris OS. Note: Access Manager and Portal Server should use the same type of web container. |
|
|
The Apache Web Server can be used with the Application Server load balancing plugin. In this case, the Apache Web Server must be installed and running before installing any Java ES components that depend on it. For additional information, refer to Installation Prerequisites in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX. |
|
|
An installation example based on LDAP Schema 1 is described in Calendar-Messaging Schema 1 Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX. For a Schema 1 deployment, you cannot use Access Manager. |
|
|
Procedures for setting up single sign-on, can be found in the Chapter 8, Configuring and Using Single Sign-On, in Sun Java Enterprise System 2005Q1 Deployment Example Series: Evaluation Scenario. Access Manager is required for single sign-on. |
|
|
Configuring High availability using HADB |
An example of setting up HADB for high availability is contained in Web and Application Services Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX. |
|
Application Serverload balancing |
An example that includes using the Application Server load balancing plugin is contained inWeb and Application Services Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX. |
|
Non-root ownership |
If non-root ownership will be required for Application Server or Web Server, refer to one of the following examples: |
- © 2010, Oracle Corporation and/or its affiliates