Previous      Contents      Index      Next
Sun Java Enterprise System 2005Q1 Installation Guide

Chapter 1
Installation Planning Overview

Sun Java™ Enterprise System (Java ES) integrates a number of Sun server-side products into a system that provides the server software needed to support distributed enterprise applications. Because of the complex interrelationships of these products, installation requires much more planning than is required when installing a single product.

This chapter provides an overview of how to prepare for Java ES installation.

Before you can plan your installation, you must first plan the deployment. If you have not yet planned the deployment, refer to the Java Enterprise System Deployment Planning Guide (http://docs.sun.com/doc/819-0058).

This chapter contains the following sections:

How Does the Java ES Installer Work?
What Installer Behavior Might Affect Installation Planning?
What Are the Installation Planning Tasks?
Next Steps

---

How Does the Java ES Installer Work?

The Java ES installer is an installation framework that uses the Solaris pkgadd or Linux rpm utility to transfer Java ES software to your system. All components of the Java ES software are installed using this single installer.

This section contains the following subsections:

Installer Modes
Language Selection
Preexisting Component Check
Dependency Check
Configuration Options and Parameter Settings
Uninstaller

Installer Modes

You can install Java ES interactively or by means of a reusable script.

Interactive Graphical Interface.    Provides an interactive graphical wizard that leads you through the tasks of installing the Java ES software on a graphical workstation.
Interactive Text-based Interface.    Provides the same functionality as that of the graphical mode, but you are prompted for responses on a line-by-line basis in a terminal window.
Silent Mode.    Provides the option to run the installer on multiple hosts, using a generated state file to specify input.

Tip	You can run the Java ES installer without installing software. This is useful for creating state files for a silent installation or for surveying Java ES software on your existing hosts.

Language Selection

The interactive installer runs in the language specified by the operating system locale setting. The following languages are available:

English
French
German
Japanese
Korean
Spanish
Simplified Chinese
Traditional Chinese

If your operating system language is not listed, the installer runs in English.

The installer automatically installs English versions of all Java ES components. In addition, you can install component packages in any of the languages listed. If your operating system language is on the list, that language is automatically selected for component installation, but you can change the selection.

During an installation session, the language you choose applies to all the components you are installing. To install some components in one language and other components in another language, you must run the installer multiple times.

The Java ES installer cannot install additional language packages for previously-installed components. However, you can use the pkgadd or rpm utility to add language packages at any time.

Preexisting Component Check

During installation, the Java ES installer surveys the software that is already installed on the host where you are installing and identifies the following:

Compatible Java ES product components

Compatible components do not need to be reinstalled and will not be available for selection in the installer.

Incompatible Java ES product components

If the installer identifies incompatibilities between components you have selected and components that are already installed locally, you might be prompted to remove or upgrade the incompatible installed component. The installer cannot continue until these incompatibilities are resolved. After resolution, you can refresh the component selection list, and continue with installation.

Incompatible Java ES shared components

It is not uncommon for existing hosts to already have versions of Java ES shared components installed, such as J2SE or NSS. If the installer finds shared components whose version is incompatible with the version of Java ES you are installing, those shared components are listed. If you proceed with installation, the installer upgrades the shared components to compatible versions.

Dependency Check

Many components depend on the presence of other components to provide their core functions. The installer does extensive cross checking of components to verify that the components you select during installation will function properly together. For this reason, the installer might prompt you to include certain components as you make your component selections.

In general, the Java ES installer uses the following rules for handling dependencies among the Java ES components:

Selecting a Component. When you select a component for installation, the installer automatically selects all its subcomponents.

The installer also selects the components and subcomponents upon which the selected component depends. For example, if you select Application Server, the installer automatically selects Message Queue.

Deselecting a Component. If you deselect a component, the installer automatically deselects all its subcomponents.

If you deselect a component that is required locally or remotely for another selected component, the installer displays various warnings when you attempt to proceed.

Selecting a Subcomponent. If you select a subcomponent, the installer automatically selects the component to which it belongs, but not the other subcomponents.

If the selected subcomponent depends on other components or subcomponents, the others are automatically selected.

Deselecting a Subcomponent. If you deselect a subcomponent, the installer automatically deselects the component to which it belongs, but not the other subcomponents.

If you deselect a subcomponent that is required locally or remotely for another selected component, the installer displays various warnings when you attempt to proceed.

Configuration Options and Parameter Settings

Many Java ES component products require some degree of installation-time configuration. The extent of installation-time configuration you perform depends on which components you select and which installation option you choose.

The following configuration options are available in the installer:

Configure Later.    During installation, you enter only the minimum values that are necessary for installing, then perform postinstallation configuration.
Configure Now.    During installation, you configure component products that permit installation-time configuration. The information you specify might be just a few common parameters (common server settings), or it might include detailed component-specific parameters (component settings).

Common server settings are parameters that multiple components use. For example, most components require that you specify an administrative ID and password. By setting these common values, you are setting default values for all component administrative IDs and passwords.

Component settings are parameters that apply to a particular component. These settings are requested during installation only if you have selected the Configure Now option. Some of these settings are populated from the common server settings.

Uninstaller

Java ES provides an uninstallation program for removing component products that were installed on your local host using the Java ES installer. The uninstaller checks product dependencies for the host on which it is running, issuing warnings when it discovers a dependency.

The uninstaller can be run in graphical, text-based, or silent mode.

After Java ES installation is complete, the uninstaller in located in /var/sadm/prod/entsys.

---

What Installer Behavior Might Affect Installation Planning?

This section discusses the behaviors and constraints of the Java ES installer that directly affect installation planning.

Local installer. The Java ES installer installs the software on one host at a time. At a minimum, you must run the installer once on every host in your deployment. Each time you run the installer is considered an installation session.
Single Installation Session. There are few situations where you only perform a single installation session because few deployments call for putting all Java ES components on a single host. The most common single-session installations are:
Installing for evaluation
Adding a single component to an established deployment
Installing a component that is using a remote component already installed on another host
Multiple Installation Sessions. Most Java ES deployments require multiple installation sessions, at least one installation session on every host in the deployment. Sometimes multiple sessions are required on the same host.
Component Compatibility Checking. When the installer checks your host software for compatibility with the new release of Java ES, the installer can only recognize local software that has been installed using the Solaris pkgadd or Linux rpm utility.
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. If you select the option of using a component on a remote host, 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.

Similarly, the uninstaller does not prevent you from uninstalling a component that is being used by a component on a remote host. You are responsible for preventing this from inadvertently happening.

Configuration Options. Some components can be configured during installation and some cannot. After you have selected components for installation, you chose an installation configuration option:
Configure Now. Allows you to configure eligible components during installation. Only some components can be configured during installation.
Configure Later. You enter only the minimum values that are necessary for installing the packages, then you configure components individually after installation. All components can use this option.

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.

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.

---

What Are the Installation Planning Tasks?

The following table lists the installation planning tasks that are common to nearly all Java ES installations. The left column lists the high-level tasks and subtasks, and the right column lists the location of instructions for performing the tasks.

Table 1-1  Installation Planning Tasks 

Task	Location of Information
1. Develop Your Installation Sequence
Review your deployment architecture and implementation specification.	What Does My Deployment Plan Call For?
Identify particular situations that affect how you plan to install Java ES for your deployment.	What Are the Key Installation Issues?
Identify the interdependencies among the components you plan to install.	How Do Component Interdependencies Affect My Installation?
Choose whether you will configure during installation or after installation.	What Configuration Option Is Best?
Decide on the number and order of your installation sessions.	How Many Installation Sessions Are Needed?
2. Survey the Target Hosts
Check to see if the Java ES software is preinstalled or preloaded on your hosts.	Is Java ES Software Preloaded on Solaris OS?
Check for Java ES components already installed on the target hosts.	Are Incompatible Components Installed?
Verify that the host is ready for installation: system requirements, access privileges, memory and disk requirements, and so on.	Are Your Hosts Ready?
3. Gather Configuration Data
Review common server settings.	Common Server Settings
Review installation directories.	Appendix B, "Default Installation Directories"
Review port assignments.	Appendix C, "Default Port Numbers"
Identify the configuration data that will be required by the installer for the Configure Now option.	Chapter 4, "Configuration Information"

It is important to approach the installation tasks in an orderly way, using the documentation provided. Your approach should include the following:

Know how to access the documentation that is available for Java ES.
Java Enterprise System Documentation Roadmap http://docs.sun.com/doc/819-0055
Sun documentation site containing Java ES material
http://docs.sun.com/prod/entsys.05q1
Learn what Java ES is and how the Java ES components and services work.

Java Enterprise System Technical Overview
http://docs.sun.com/doc/819-0061

Plan your deployment.

Java Enterprise System Deployment Planning Guide http://docs.sun.com/doc/819-0058

Plan your installation.
Develop an installation sequence and gather the information you will need for installation. In this guide, refer to Part I, Installation Planning.
Review the Java Enterprise System Release Notes (http://docs.sun.com/doc/819-0057) for installation issues associated with your platform or particular components.
Do any upgrading necessary on your existing hosts.
Determine if existing software on your hosts is compatible with this release of Java ES. In this guide, refer to Are Incompatible Components Installed?.
Java Enterprise System Upgrade and Migration Guide http://docs.sun.com/doc/819-0062
Install Java ES software.

Install the software on your hosts, perform postinstallation configuration, and start the individual components. In this guide, refer to Part II, Installing and Configuring.

Complete your deployment.

Complete any additional tasks required to implement your deployment, such as customization or data migration. Pointers to topical Java ES documentation are contained in the following document:

Java Enterprise System Documentation Roadmap http://docs.sun.com/doc/819-0055

---

Next Steps

Now that you have an idea of the installation planning required, you are ready to develop an installation sequence based on your deployment documents. Proceed to Chapter 2, "Developing Your Installation Sequence".

Previous      Contents      Index      Next

---

Part No: 819-0056-11.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.