Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Installation Guide

About the Application Server Installation

The Application Server product is made up of a number of software components and provides different installation choices. Among the choices for installation are:

You can install from the product CD or from the download site.
You can install from the command-line interface or the graphical interface.
You can install interactively or in silent mode.

This section addresses the following topics:

Installation Components

In general, you are installing the basic components that provide the functionality of the Application Server product. 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 dependencies 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. Once component dependencies are satisfied, 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.

The following installation components are included with the Application Server Enterprise Edition product:

Application Server—Application Server software, including its command-line administrative tools, and Sun Java^TM System Message Queue software.

Sun Java System Message Queue software is automatically installed with the Application Server software here: install_dir/imq.
Domain Administration Server—Application Server software, including the Admin Console, its graphical administrative tool.
Application Server Administration Client—asadmin utility.

Select the Administration Client component to install the command-line utility separately on a machine where the Application Server is not installed. When you install the Application Server or the Domain Administration Server, the Administration Client is also installed.
Java 2 Software Development Kit—During installation, you can choose to reuse a Java 2 SDK that is already installed on your system as long as the Java 2 SDK version is correct. The default installation location for each distribution is install_dir/jdk.

Refer to the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Update 2 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 with Java 2 SDK from Sun Microsystems. Third-party Java development kits, even with appropriate version numbers, are not supported.
PointBase database server.
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 at: install_dir/samples/index.html.

The following additional components are included with the Application Server product:

High-Availability Database Server (Enterprise Edition)—By default, the HADB Server is installed at: install_dir/hadb.

To install the Application Server and an HADB server node on the same system, select both components.

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.1 2005Q2 High Availability Administration Guide.
Load balancer plug-in—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.1 2005Q2 Update 2 Release Notes.

For additional information on this component and supported web servers, refer to Installing the Load Balancer Plug-in Component and Chapter 4, Configuring Load Balancing and Failover, in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide.

Installation Methods

Three methods of installation are available:

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

./bundle_filename
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:

./bundle_filename -console

Use the command-line interface when installing:
- On a 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 setup command allows you to specify the method of installation, and allows you to create a configuration file for silent installation. The syntax is:

bundle_filename [-console] [-savestate config_file] [-silent config_file] [-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` `config_file`	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` `config_file`	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`	`java_home_dir`
`-h \|\| -help`	Displays the available command-line arguments 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)	`./bundle_filename`
Command-line interface	`./bundle_filename` `-console`
Graphical interface for creating configuration file for silent mode installation	`./bundle_filename` `-savestate` `config_file`
Silent mode based on an existing installation configuration file	`./bundle_filename` `-silent` `config_file`
Display available Command-line arguments for the setup command	`./bundle_filename` `-help`