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 http://www.sun.com/software/products/appsrvr/index.xml.

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:

Domain Administration Server and Administration Tool – The Domain Administration Server (DAS) acts as a central repository for applications and configuration information for server instances, even if they are located on a remote machine. It includes graphical and command-line administration tools, a bundled Java DB database, and Sun Java^TM System Message Queue software. Sun Java System Message Queue software is automatically installed at the following location: install-dir/imq.
Node Agent – The node agent communicates between application server instances and the Domain Administration Sever. All machines that contain application server instances must have a node agent installed.

In addition, several additional components are available for installation:

Java 2 Software Development Kit (SDK) – During installation, you can choose to reuse a preinstalled, supported version of Java 2 SDK. The installation location is install-dir/jdk.

Refer to the Sun Java System Application Server Enterprise Edition 8.2 Standalone Installer Release Notes to identify which version of the Java 2 SDK is supported.

Note –
The Sun Java System Application Server product is certified to work only with Java 2 SDK from Sun Microsystems. Third-party Java development kits, even with appropriate version numbers, are not supported.
Sample applications – Samples come with the source, schema, Ant build scripts, and EAR files. Any existing data associated with the database-related samples is available in the database. These sample applications are categorized as:
- Technology samples – Introduce various technical aspects of the Java 2 Platform, Enterprise Edition (J2EE^TM) specification as well as the value-added features of the Application Server platform
- Interoperability samples – Provide more detailed views on how these technologies come together on the Application Server platform
By default, the sample applications are installed at: install-dir/samples. More information about samples is at: install-dir/samples/index.html.
High-Availability Database Server (Enterprise Edition) – HADB is installed at: install-dir/hadb.

For more information on this component, refer to Chapter 2, Installing and Setting Up High Availability Database, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.
Load balancing plugin – This component is dependent on a pre-installed Web server. Supported Web servers are listed in Web Servers in Sun Java System Application Server Enterprise Edition 8.2 Standalone Installer Release Notes. For information on configuring web servers for use with the load balancing plugin, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.

If you are installing only the load balancing plugin, see Installing the Load Balancing Plugin Component.

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:

Node agent
Domain Administration Server (includes administration tool)
Samples

Load balancing plugin only:

Load balancing plugin
No administration tools

Application Server instances without Domain Administration Server:

Node agent
No administration tools

HADB without Application Server:

HADB
No administration tools

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:

Graphical (interactive) – The installation program prompts you using a sequence of graphical screens. This method is the default when you invoke the installation program without options:

./distribution-filename

On Windows, if you double-click the .exe file, you run the installer in graphical mode.

The distribution-filename changes depending upon the version and platform, in the format sjas_ee-version-platform.type. For example, for the Linux Application Server distribution, the file is sjsas_ee-8_2-linux.bin, and for Windows, the file is sjsas_ee-8_2-windows.exe.
Command line (interactive) – The installation program prompts you using a sequence of command-line prompts and messages. To activate the interactive command-line mode, invoke the installation program using the console option:

./distribution-filename -console

Use the command-line interface when installing:
- On remote servers, using the Telnet terminal emulation protocol
- On “headless” systems without display devices
- In hardened Solaris environments
Silent mode – The installation program reads installation parameters from a supplied configuration file. See Installing in Silent Mode for more information on generating the configuration file.

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


Option	Description
`-console`	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.
`-javahome`	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)	`./distribution-filename`
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.