Sun Java System Application Server Enterprise Edition 8.2 Installation Guide

An Overview of Application Server Installation

You can install the Application Server software from the product CD or you can download the installation binaries from

The Application Server product consists of several software components and provides different installation choices.

This section addresses the following topics:

Installation Components

You can choose not to install some of the components. Later, if you want to add a component that you initially chose not to install, you can do an incremental installation of that component, providing interdependencies among components are met.

Note –

A partial installation can be followed by any number of incremental installations. For silent mode, you can do a partial initial installation, but any subsequent installations must be done using an interactive method.

The installation program enforces component dependencies as specified for each component. Component life cycles are independent. A particular component can be installed dynamically through incremental installation without corrupting other components. However, partial uninstallation is not supported.

An installation of Application Server includes the following components:

In addition, several additional components are available for installation:

Installation Scenarios

You can choose to install components depending upon your deployment topology. The following examples show the options to select in the installer for specific types of installations.

Default Application Sever installation:

Load balancing plugin only:

Application Server instances without Domain Administration Server:

HADB without Application Server:

For more information on possible topologies, see Sun Java System Application Server Enterprise Edition 8.2 Deployment Planning Guide.

Installation Methods

The following methods of installation are available:

The installation program allows you to specify the method of installation, and allows you to create a configuration file for silent installation. The syntax is:

distribution-filename [-console] [-savestate configuration-filename] [-silent configuration-filename] [-javahome java-home-dir] [-h || -help]

Table 1–1 describes the command options.

Table 1–1 Options for Installation




Runs the installation using the command-line method. 

-silent configuration-filename

Runs the installation in silent mode. Installation parameters are read from an existing installation configuration file. This option is mutually exclusive with the savestate option.

The installation configuration file path must be explicitly provided; there is no default file path. Refer to Installing in Silent Mode for further specifics on silent mode installation and the installation configuration file.

-savestate configuration-filename

Runs the installation using either the graphical or command-line method and creates an installation configuration file based on this installation. This option is mutually exclusive with the silent option. If you do not specify this option, no installation configuration file is created. 


Sets the java-home-dir if you are using an already installed JDK.

-h || -help

Displays the usage for the installation command. 

Table 1–2 identifies the command for each installation method.

Table 1–2 Installation Commands

Installation Method 

Installation Command 

Graphical interface (default) 


Command-line interface 

./distribution-filename -console

Graphical interface for creating the configuration file, which will be used for for silent mode installation 

./distribution-filename -savestate configuration-filename

Silent mode based on an existing installation configuration file 

./distribution-filename -silent configuration-filename

Using Solaris 10 Zones for Application Server Installation

If you are installing on a Solaris 10 system, you can use the Solaris 10 Zones facility.

By default, every Solaris 10 host contains a single global zone. The global zone is both the default zone for the host and the zone used for system-wide administrative control. You can also create non-global zones. One or more applications can run in a non-global zone without interacting with the rest of the host. Each non-global zone has its own instance of an installed Solaris 10 operating system with configuration and other information unique to that non-global zone.

Use these zones (also known as Solaris containers) to create virtualized operating system environments within an instance of Solaris OS. The zones allow one or more processes to run in isolation from other activities on the host. For example, a process running in a zone is only able to send signals to other processes in the same zone, regardless of user ID and other credential information.

You can install the Application Server in the global zone or in a non-global zone.