test

Sun Java Enterprise System 5 Installation Guide for UNIX

How the Java ES Installer Works

Sun Java Enterprise System (Java ES) integrates a number of Sun server-side products to support distributed enterprise applications. In this document, these products are referred to as the Java ES product components. A collection of supporting software, called the shared components, is also included. The Java ES installer installs the Java ES product components and shared components in various combinations, one host at a time. Because of the complex interrelationships of the components, installation requires more preinstallation and postinstallation effort than is required to install a single product component.

The Java ES installer adds component packages (Solaris OS), RPMs (Linux), or Depots (HP-UX) on the local host. To uninstall a product component, an uninstallation utility with an unconfiguration interface is provided. During the course of operation, log records are generated and saved into files.

This section contains the following subsections:

Java ES Installation Utilities

The installation utility (installer) is located in the platform directory where you are installing Java ES, for example, /jes5install/Solaris_sparc. You will see a Product directory, a text file called release_info, and the executable installer script. This is the location for invoking the installer unless your installer has been patched.

There is another directory that contains a packaged version of the installer that is used for patching. The patch installation script (install) is located in the following directory along with the Log Viewer utility (viewlog):

If there is a bug in the installer, Sun can fix the installer and create a patch for the installer package. After the patch is applied, the packaged version of the installer should thereafter be used for the release, thus launching the version of the installer that contains the fixes from the patch.

Note –

You only use the patch utility if your deployment is using a patched version of the Java ES installer.

After installation, the Java ES uninstallation utility (uninstall) is located here:

Syntax and examples for the Java ES installation utilities are contained in Appendix B, Installation Commands.

Java ES Components Used in This Release

The Java ES software consists of a collection of Sun server-side products and their supporting shared components that work together to support distributed applications across a network. The Java ES 5 release presents the following selectable components, many of which have selectable subcomponents.

Any alternate or abbreviated names used in this guide are in parentheses following the component name and version.

Note –

HP-UX does not support Sun Cluster components, Directory Preparation Tool, HADB, or third-party web containers. Linux does not support Sun Cluster components, and only supports the BEA WebLogic third-party container for Configure Now.

Note –

The Directory Preparation Tool is only used with Communications products, and is included with Directory Server in the Java ES release as a convenience. Information on the Directory Preparation Tool can be found in Chapter 8, Directory Preparation Tool (comm_dssetup.pl), in Sun Java Communications Suite 5 Installation Guide.

To see the full list of services and subcomponents as displayed in the Java ES installer, refer to Appendix A, Java ES Components for This Release. This appendix also lists the shared components that are provided with this release.

Available Installer Modes

The Java ES installer is an installation framework that uses the Solaris pkgadd, Linux rpm, or HP-UX swinstall utility to transfer Java ES software to your system. You can install Java ES interactively or by means of a reusable script.

Tip –

You can run the Java ES installer without installing software. This is useful for surveying existing Java ES software on your hosts.

How Language Selection Works

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

If your operating system language is not listed, the installer runs in English. The installer automatically installs English versions of all Java ES components. By default, multilingual packages are selected when components are selected for installation.

The installer cannot install additional language packages for previously-installed components. However, you can use the pkgadd, rpm, or swinstall utilities to install localization packages at any time. Language packages are list in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX.

How the Installer Checks for Preexisting Components

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

How the Installer Checks Component Dependencies

Many product components depend on the presence of other components to provide their core functions. The installer does extensive cross checking of product 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 product components as you make your selections.

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

How the Installer Checks for System Readiness

After the components you have selected are found to be acceptable for installation and you have indicated their target installation directories, the Java ES installer performs a system check to determine if your host meets the requirements for the components you selected.

The installer checks for disk space, memory, swap space, operating system, patches and operating system resources based on the selected components and the installation directories provided. The following messages inform you about the state of your host:

How the Installer Handles Configuration and Parameter Setting

Many Java ES product components are eligible for some degree of installation-time configuration. The extent of installation-time configuration you are required to perform depends on which product components you select and which installation type you choose.

Note –

The following components cannot be configured by the Java ES installer, and, therefore, must the configured after installation: Directory Proxy Server, Java DB, Monitoring Console, Service Registry, and Sun Cluster components.

The following configuration types are available in the installer:

It is important to keep track of the configuration information values as you proceed through installation-time configuration or postinstallation configuration. Many of the product components rely on the specifics of other component configuration parameters in order to function correctly. At the end of a Configure Now installation, you can view the configuration parameters that were specified by examining the Installation Summary.

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

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

How Upgrading Works

The Java ES installer automatically upgrades shared components for the selected product components to match the level required for the release of Java ES. If you want to upgrade shared components manually, you must exit the installer, upgrade the shared component, then return to the installer. Shared components can also be installed or upgraded in a dedicated installation session that installs only shared components, enabling them to be synchronized to the current release. If you choose to install the Shared Components item, all required shared components for the Java ES release are installed or upgraded.

Note –

If the installer is run in a non-global Solaris zone with a sparse root file system, the Shared Component item is not available for selection.

On Solaris OS, some product components are already installed with the operating system. In this case, you can upgrade these product components using the Java ES installer. In a graphical installation session, if upgradable product components are detected on your host, the Status column of the Choose Software Components page indicates Upgradable. For the text-based installer, a separate list displays the upgradable product components. The components that can be upgraded by the installer are listed in the following table, along with explanation on any Solaris zones issues that might apply.

Table 1–1 Upgrade Support Within the Java ES Installer

Component 

Situation Where the Java ES Installer Can Upgrade 

Solaris Zones Issues 

Application Server 

Application Server 7.0 bundled with Solaris 9 

Application Server 8.0 bundled with Solaris 10 

Application Server 8.1.0 installed with Java ES 3 (2005Q1) 

Application Server 8.1.2 installed with Java ES 4 (2005Q4) 

Before Application Server can be installed into a non-global sparse-root zone, the bundled version must be removed from the global zone. 

Upgrading Application Server in the global zone will replace the existing version in the global zone and any versions in whole root or sparse root zones. 

HADB 

HADB installed with Java ES 2005Q1 (release 3) 

HADB installed with Java ES 2005Q4 (release 4) 

 

Message Queue 

Message Queue bundled with Solaris 9 

Message Queue bundled with Solaris 10 

Message Queue installed with Java ES 3 (2005Q1) 

Message Queue installed with Java ES 4 (2005Q4) 

Message Queue can only be installed in the global zone, or in a whole root non-global zone. 

From the global zone, Message Queue always propagates to non-global zones. 

If the installer identifies incompatible versions of product components that cannot be upgraded by the installer, you will receive messages saying that certain product components must be removed or manually upgraded before you can continue with installation. Such upgrading is fully documented in the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

How Logging Works

During the course of installation or uninstallation, log records are generated for the operations that occur. These records are saved into a single file in a format called Unified Logging Format (ULF). The Java ES installer Log Viewer utility (viewlog) provides a user-friendly interface for examining these log records. After Java ES installation is complete, the Log Viewer is located here:

After uninstallation, the viewlog utility is removed. The ULF logs themselves are not removed, and are located here:

For instructions on using the Java ES logs and Log Viewer, refer to Examining Installation Log Files.

How Java ES Reporter Works

Java ES Reporter is a command-line utility that performs anonymous product registration after a successful interactive Java ES installation session. Immediately after the Java ES components are installed, the Reporter installation starts. On the command line, you are prompted to enter the URL or IP address of a proxy that Reporter will use to access Sun through the internet. The installation proceeds silently and no further action is required.

If you do not want to install Reporter, you can specify the -noreporter option to the installer command when you start the Java ES installation session. To install only Reporter (after using the –noreporter option, or after a silent Java ES installation), there is another option available (-reporter) on UNIX platforms. The Reporter options for the Java ES installer are explained in installer or install Command.

After Reporter is installed, you can enable or disable Reporter by editing a configuration file. These instructions are contained in Java ES Reporter Postinstallation Configuration.

Because Reporter is not a Java ES component of the installer, it cannot be uninstalled using the Java ES uninstaller. Instructions for uninstalling Reporter are contained in Uninstalling Java ES Reporter.

How Uninstalling Works

Java ES provides an uninstallation utility (uninstall) for removing component products that were installed on the local host using the Java ES installer. The Java ES uninstaller checks product dependencies for the host on which it is running, issuing warnings when it discovers a dependency. For some product components, certain files remain after uninstallation and might need to be removed manually. For uninstallation specifics on each product component, refer to Reviewing Uninstallation Behavior for Java ES Product Components.

The uninstaller can be run in graphical, text-based, or silent mode. After Java ES installation is complete, the uninstaller is located here:

After uninstallation, the uninstall utility is removed from the host. For instructions on using the uninstaller, refer to Chapter 8, Uninstalling.

Shared components cannot be removed using the Java ES uninstaller. Shared components are upgraded by the Java ES installer when you install a later version of Java ES. Some shared component can be manually upgraded using procedures in the Sun Java Enterprise System 5 Upgrade Guide for UNIX. Instructions for uninstalling Java ES Reporter are contained in Uninstalling Java ES Reporter.

An installed version of Sun Cluster software cannot be removed using the Java ES uninstaller. For information on uninstalling Sun Cluster software, refer to Uninstalling Sun Cluster Software and Sun Cluster Software and Sun Cluster Geographic Edition Uninstallation Behavior.