Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 2004Q2 Installation Guide 

Chapter 1

This chapter provides an overview of Sun Java™ Enterprise System and the Java Enterprise System installer.

This chapter contains the following sections:

What Is Java Enterprise System?

Java Enterprise System integrates Sun™ server-side products into a single software system that provides the integrated server software needed to support distributed enterprise applications.

To learn more about the services Java Enterprise System offers and about the technologies used to provide those services, refer to the Java Enterprise System Technical Overview (/docs/cd/E19263-01/817-5764).

For an overview of the tasks involved in integrating Java Enterprise System into your computing infrastructure, see the Java Enterprise System Documentation Roadmap (/docs/cd/E19263-01/817-5763). This roadmap also lists many documentation resources to help you accomplish these tasks.

What Is in this Release of Java Enterprise System?

Java Enterprise System 2004Q2 provides a broad spectrum of component products and shared components supporting many languages across multiple operating system and hardware platforms, as described in the following sections.

Operating Systems and Hardware Platforms

Java Enterprise System 2004Q2 supports the following combinations of operating system and hardware platform:


In addition to English, Java Enterprise System 2004Q2 includes support for the following languages:

Additional information on the languages for the Java Enterprise System installer is contained in Language Selection.

Component Products

Component products provide infrastructure services needed to support distributed enterprise applications. When you install Java Enterprise System on a particular host, you choose which component products to install on that host based on your overall deployment architecture.

Java Enterprise System 2004Q2 includes the following component products:

Communication & Collaboration Services

Web & Application Services

Directory & Identity Services

Availability Services

Administrative Services

Note that Sun Cluster, Sun Cluster Agents, and Sun Remote Services Net Connect are not available on the Linux operating system.

Shared Components

Shared components provide the local services and technology support upon which the component products depend. When you install component products, the Java Enterprise System installer automatically installs the shared components required if they are not already installed.

Java Enterprise System 2004Q2 includes these shared components:

How Do I Get the Java Enterprise System Software?

You can get the Java Enterprise System software the following ways:

How Does the Java Enterprise System Installer Work?

The Java Enterprise System common installer is an installation framework that uses the Solaris pkgadd or Linux rpm utility to transfer Java Enterprise System software to your system. The installer supports graphical and text-based interactive modes as well as a parameter-driven silent installation mode. All Java Enterprise System components are installed using this single common installer.

Benefits of the common installer include:

During installation, you can perform configuration of the component products you selected. The extent of installation-time configuration depends on which component products and which configuration type you select.

The following sections explain how the installer works:

Installer Modes

You can install Java Enterprise System interactively or by means of a reusable script. The following are the three modes in which the installer runs:

For information on choosing which mode to use for your installation, refer to Choosing an Installation Mode.

Language Selection

Java Enterprise System components are available in a number of languages. You can install the components in their translated interfaces, in addition to the English interface.

Installer Languages

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

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

Component Languages

The installer automatically installs English versions of all Java Enterprise System components. In addition, you can install component packages in any of the languages on the list. If your operating system language matches a language on the list, it is selected for installation by default, but you can change the selection.

During an installation session, the languages you choose apply to all the components you are installing. To install some components in one set of languages and other components in another set of languages, you can run the installer multiple times.

The installer cannot install additional language packages for previously-installed components. However, you can use the pkgadd or rpm utility to add languages at any time. To find out which packages to add for each component product, see Localized Solaris Packages for Component Products.

Pre-existing Software Checking

During installation, the installer surveys the machine where you are installing and identifies the following.

For software that was installed using a package-based method, you can use the installer to list the previously installed products. Instructions are contained in Identifying Component Upgrade Needs.


In surveying your machine for previous versions of Java Enterprise System component products, the installer detects these special situations:

  • The installer detects the Directory Server version that is distributed with the Solaris operating system and warns you that the Directory Server script belonging to the Solaris distribution will be renamed by the installer.
  • The installer detects the Message Queue version that is distributed with the Solaris operating system. The package names for that version are the same as the package names for the Java Enterprise System version.

Many systems already have versions of the shared components installed, such as J2SE or NSS. The Java Enterprise System installer checks the shared components installed on the machine. If it finds shared components whose version is incompatible with Java Enterprise System, it lists them. If you proceed with installation, the installer upgrades the shared components to the newer versions.

Dependency Checking

The installer does extensive cross checking of components to verify that the installation components you select will function properly. The following topics are addressed in this section:

Component Product Dependency Checking

Many components depend on the presence of other components to provide their own core functions. The Java Enterprise System installer provides dependency checking logic to ensure that those dependencies are met. For this reason, the installer might automatically select certain components as you make your selections.

For example, Identity Server needs a local or remote instance of Directory Server and a local instance of a J2EE web container, either Application Server or Web Server. Additionally, Application Server needs a local instance of Message Queue.

The installer checks the relationships between selected software and existing installed software. For example:

Component Selection Process

In general, the Java Enterprise System installer uses the following rules for governing selection and deselection of component products:

Interdependency Example

The following figure illustrates the various types of dependency relationships among component products. In the figure, unbroken lines represent dependencies that must be satisfied on the local machine. Dashed lines represent dependencies that can be satisfied remotely.

Figure 1-1  Example of Component Product Interdependencies

Diagram showing the local dependencies of Identity Server on a local web container, and of Identity Server on a local or remote Directory Server.

When you select to install Identity Server, the installer automatically selects:

Configuration Types and Parameter Setting

Many Java Enterprise System component products require some degree of installation-time configuration. The information you specify might be just a few common parameters, such as administrator user ID and password, or it might include detailed component-specific parameters. The type of configuration you choose determines how configuration will be performed for your installation.

Information on choosing your configuration type is contained in Choosing a Configuration Type.

Depending on the configuration type you selected, two types of configuration information might be required during installation:


Java Enterprise System provides an uninstallation program for removing component products that were installed on your system using the Java Enterprise System installer. The uninstaller checks product dependencies for the system 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 installing Java Enterprise System, you can find the uninstaller in /var/sadm/prod/entsys.

Full instructions for using the uninstaller are contained in Chapter 10, "Uninstalling Software".

Installation Flow

The installation flow varies depending on your deployment plan and the combination of component products you are implementing. The full set of installation tasks is contained in Installation Roadmap. You may not need to perform all these tasks.

To see some high-level examples of the types of installation you might perform, refer to Installation Procedures for Specific Deployment Needs. If one of these examples matches closely with the implementation you have planned, it can be helpful to use the steps as a guideline.

The following flow charts illustrate the main actions and decision points of a standard Java Enterprise System installation. The figure is divided into parts, for reasons of size. The left side of the figure shows the installer’s actions, and the right side of the figure shows your actions.

Figure 1-2  Installation Flow, from Start to Upgrading Components

Flow diagram showing installer operation from start through component selection and component compatibility checking.[D]

The following figure is the continuation of Figure 1-2. The ellipses (...) at the bottom of Figure 1-2 connect to the ellipses at the top of Figure 1-3.

Figure 1-3  Installation Flow, from Shared Component Compatibility Checking to End

Flow diagram showing installer operation from shared component compatibility checking through completion.[D]

Previous      Contents      Index      Next     

Copyright 2004 Sun Microsystems, Inc. All rights reserved.