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.

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.