Chapter 1 Installing Application Server Software

This chapter provides instructions for installing the Sun Java System Application Server Enterprise Edition software. You can install interactively or use silent mode to replicate an installation scenario on multiple machines.

If you want to use the Java Enterprise System (JES) installer to install Application Server, see the Sun Java Enterprise System 5 Installation Guide for UNIX and Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

The following topics are addressed:

• Before You Read This Book

• An Overview of Application Server Installation

• Installing Application Server Software

• Installing the Load Balancing Plugin Component

• Installing in Silent Mode

For any late-breaking updates to these instructions, check the Sun Java System Application Server Enterprise Edition 8.2 Standalone Installer Release Notes.

For more information about configuring the application server after installation, see the Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.

For troubleshooting information, see the Sun Java System Application Server Enterprise Edition 8.2 Troubleshooting Guide.

The following location contains product downloads and other useful information: http://www.sun.com/software/products/appsrvr/home_appsrvr.html

The Application Server is available in Platform, Enterprise, and Standard editions. This document covers both Standard and Enterprise Edition.

• Platform Edition is a lightweight, small footprint product intended for developer productivity and department-level production environments.

• Enterprise Edition is designed for mission-critical services and large-scale production environments. It supports horizontal scalability and service availability with a load balancing plugin and cluster management. Enterprise Edition also supports reliable session state management with the high-availability database (HADB).

• Standard Edition provides all the features of the Enterprise Edition except the session state failover feature.

Before You Read This Book

Before following the installation procedures described in this book, plan your topology using the Sun Java System Application Server Enterprise Edition 8.2 Deployment Planning 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

• Installation Scenarios

• Installation Methods

• Using Solaris 10 Zones for Application Server Installation

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.

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–2 identifies the command for each installation method.

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.

Installing Application Server Software

This section provides instructions for installing the Application Server software.

For information on supported platforms, see Hardware and Software Requirements in Sun Java System Application Server Enterprise Edition 8.2 Standalone Installer Release Notes.

As you run the installation program, make a note of the user names, passwords, and the port numbers you enter, for future reference.

To Install Application Server Software

Before You Begin

On UNIX or Linux, if you are installing as a non-root user, you must have read/write access to the following directories:

• The installation directory you select

• The home directory of the installation user

• The /var/tmp directory

• The /tmp directory

1. After you have planned the topology, navigate to the location where the installation program resides and run the installation program.

   See Table 1–2 for a list of installation commands for various installation methods. Refer Table 1–1 for installation options. If you are installing the load balancing plugin, a web server must already be installed. Refer to Installing the Load Balancing Plugin Component. For more information on planning topology, see Sun Java System Application Server Enterprise Edition 8.2 Deployment Planning Guide.

   ---

   Note –

   If you do not have execute permission for this file, use the chmod command to grant yourself execute permissions.

   ---

2. Follow the installation wizard screens to accept the license agreement.

3. Specify the path to the Application Server installation directory or accept the default installation directory.

4. Select the components to install.

   If a component is disabled, the installation program has detected it as already installed on your system.

   The following components are available for installation:

   • Node Agent – All machines that contain application server instances should have a node agent installed.

   • High Availability Database Server (Enterprise Edition only) -This component stores session information so requests can be failed over if you are using the load balancing plugin.

   • Load Balancing Plugin - Install the load balancing plugin on the machine where a web server is installed. If you do not already have a web server installed on the machine where you are installing the load balancing plugin, you cannot continue to install the load-balancer plugin. Supported web servers are listed in Web Servers in Sun Java System Application Server Enterprise Edition 8.2 Standalone Installer Release Notes.

   • 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 the instances are located on a remote machine. It includes graphical and command-line administration tools.

   • Command Line Administration Tool Only - Install the Command Line Administration tool on machines which do not contain a DAS, but from which you want to communicate with the DAS or a node agent. For example, install the command-line administration tool on machines from which you plan to remotely administer the Application Server using the command-line administration tools.

   • No Administration Tools - Use this option when installing components on a machine that already contains the administration tools, or on which no administration tools are required. For example, when installing the load balancing plugin on a machine with a web server, but no Application Server, no Application Server administration tools are required.

   • 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 included Java DB database.

5. Choose to install the Java 2 SDK, or use a preinstalled Java 2 SDK.

   If you choose to install the Java 2 SDK, a private copy is installed. The default Java 2 SDK installation path for all platforms is install-dir/jdk.

   ---

   Note –

   The Application Server software is certified to work with Java 2 SDK from Sun Microsystems. Third-party Java 2 SDK development kits, even with appropriate version number, are not supported.

   ---

6. If you selected the load balancing plugin component, identify your web server and its installation directory. For instructions on how to install the load balancing component, refer Installing the Load Balancing Plugin Component

   ---

   Note –

   If you are using a Web Server 7.0 installation, you need to provide Web Server 7.0 administration-specific information. For more details, refer Installing the Load Balancing Plugin Component.

   ---

7. In the Administration Configuration page (or at the command line), enter the following (and you proceed to Step 9):

   • Administration User Name - Name of the user who administers the server

   • Password - Administration user’s password to access the Domain Administration Server (8-character minimum)

   • Master Password - SSL certificate database password, used in operations such as Domain Administration Server startup

   • Administration Port - Port number to access the Domain Administration Server

   • HTTP Port - Port number to access the default server instance

   • HTTPS Port - Secure port number to access the default server instance

   ---

   Note –

   The installation program automatically detects ports in use and suggests unused ports for the default settings.

   The default ports are:

   • Administration Server - The default is 4849

   • HTTP server - The default is 8080

   • HTTPS sever - The default is 8181

   In addition, five other ports are automatically assigned. You can change the automatically assigned values after installation using the Admin Console. The default ports assigned are:

   • Sun Java System Message Queue - The default is 7676

   • IIOP - The default is 3700 for IIOP, and 3820 and 3890 for IIOP/SSL

   • JMX - The default is 8686

   If these default port numbers are in use, the installation program assigns random port numbers from the dynamic port range. This number may not be the next available port number.

   ---

8. Alternatively, if you are installing the node agent but not the Domain Administration Server, enter the following:

   • Admin Host Name - Host name of the Domain Administration Server

   • Admin User Name - Name of the user who administers the Domain Administration Server

   • Password - Domain Administration Server administration user’s password (8-character minimum)

   • Master Password - Domain Administration Server's SSL certificate database password, used in operations such as node agent startup

   • Admin Port - Port number to access the Domain Administration Server

   • Node Agent Name - Defaults to the system host name

   ---

   Note –

   In most cases, you must not change the node agent name, because node agent names must be unique within each server domain.

   ---

9. In the Installation Options page, select the options that you want.

   If you select the “Upgrade from Previous Version” checkbox, the upgrade process begins after installation is completed. Upgrades from 7.x Enterprise Edition, 8.0 Platform Edition, 8.1 Platform Edition, 8.1 Enterprise Edition, and 8.2 Platform Edition are supported. For information about upgrading, see Chapter 2, Upgrading an Application Server Installation, in Sun Java System Application Server Enterprise Edition 8.2 Upgrade and Migration Guide.

10. The installation program verifies the available disk space on your machine.

    If you do not have enough disk space, an error message is displayed. See the Platform Requirements in Sun Java System Application Server Enterprise Edition 8.2 Standalone Installer Release Notes to identify the minimum disk space required.

11. In the Ready to Install page, verify the information on what is to be installed, and click Install Now to start the installation (or enter yes at the command line).

12. When the installation is complete, read the installation summary page to determine the status of the installation. If the installation is successful, click Finish.

    Review the installation log files. For a list of these log files and their locations, see Installation Log Files.

13. Start the server.

    See the Sun Java System Application Server Enterprise Edition 8.2 Quick Start Guide in the install-dir/docs-ee directory or online for information about starting the server.

14. If you selected the HADB components:

    1. Verify that you have successfully installed the HADB on each host by typing: hadbm --help

       A list of all commands available using the hadbm utility is displayed. The hadbm utility is located at install-dir/hadb/4/bin.

    2. Configure your system for high availability. See the Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide for information.

Installing the Load Balancing Plugin Component

Use this procedure to install the load balancing plugin component without installing the other Application Server components.

To Install the Load Balancing Plugin Component

1. Check the system hosting the web server and load balancing plugin to see if a previously installed load balancing plugin or reverse proxy plugin is present. If it is, remove it using the uninstallation program.

2. Verify that the supported web server is installed on the machines where you are going to install the load balancing plugin.

   ---

   Note –

   You must install the web server and the load balancing plugin using the same user account.

   ---

   See Web Servers in Sun Java System Application Server Enterprise Edition 8.2 Standalone Installer Release Notes to identify currently supported web server versions. Some web servers require additional configuration to run with the Application Server load balancing plugin. For more information, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.

3. On the installer's Component Selection page, select Load Balancing Plugin and No Administration Tools.

4. Identify your web server and the web server instance path.

5. If you are installing the load balancing plugin on Web Server 7.0, the installer displays the Sun Java System Web Server 7.0 information page. Enter the following:

   • Web Server Administrator User - Name of the user who administers the web server.

   • Web Server Administrator Password - Password to access the Web Server administration server.

   • Web Server Host Name - Name of the web server host.

   • Web Server Administration Port - Port number to access the Web Server administration server. The default port is 8989.

   ---

   Note –

   • Ensure that you enter valid values for these fields related to Web Server 7.0 administration server. The installer does not validate these values.

   • After you install load balancing plugin on Windows for Sun Java Systems Web Server 7.0, you need to reboot the machine, so that the installer updates the system PATH environment variable to add the path to the plugin libraries.

   • You cannot perform a silent installation of the load balancing plugin on Web Server 7.0.

   ---

   The Installation Summary page is displayed indicating the installation status.

   Review the installation log files. For a list of these log files and their locations, see Installation Log Files.

Installing in Silent Mode

Silent mode installation runs without any user input. This mode uses a configuration file for installation information. The following topics are discussed:

• Creating the Installation Configuration File

• Modifying the Installation Configuration File

• Using the Installation Configuration File to Install in Silent Mode

Creating the Installation Configuration File

The installation configuration file is created when you use the savestate option with the setup command to start an interactive installation. During the interactive installation, your input is collected and stored in the configuration file you specified. This forms the template for silent installation, which you can use later to install the product on one or more machines. If needed, you can modify the installation configuration file.

The following topics are addressed:

• Creating the Installation Configuration File on Solaris and Linux

• Creating the Installation Configuration File on Windows

• Installation Configuration File Example

You cannot use the silent installation procedure to install the load balancing plugin on Web Server 7.0.

Creating the Installation Configuration File on Solaris and Linux

To create an installation configuration file on Solaris or Linux:

1. Navigate to the location of the installation file.

2. Create the configuration file. For the graphical method, the syntax for creating the configuration file is: ./distribution-filename -savestate configuration-filename

   For the command-line method, the syntax is: ./distribution-filename -console -savestate configuration-filename

If you do not include a path to the installation configuration file, the file is created in the directory where you are running the installation program. You must have write permissions for the directory where the installation configuration file is created, otherwise the installer will not be able to create the installation configuration file after the installation is complete.

Creating the Installation Configuration File on Windows

To create the installation configuration file on the Windows platform, start the installation program from the command line. Change to the directory where the installation file resides.

For the graphical method the syntax is: distribution-filename -savestate configuration-filename

For the command-line method, the syntax is: distribution-filename -console -savestate configuration-filename.

If you do not include a path to the installation configuration file, the file is created in the directory where you are running the installation program.

Installation Configuration File Example

Example 1–1 Installation Configuration File

#
# Wizard Statefile created: Tue Mar 28 16:37:05 PST 2006
#              Wizard path: /var/tmp/sjsasAAAH7aarp/appserv.class
#

#
# Install Wizard Statefile section for J2EE 1.4 SDK
#
#
[STATE_BEGIN J2EE 1.4 SDK 2860414c861c7b95a1287502663618e16472fc40]
defaultInstallDirectory = /SUNWappserver
currentInstallDirectory = /export/SUNWappserver
SELECTED_COMPONENTS = Domain Admin Server#Node Agent#High Availability 
Database Administration Client#Sample Applications#
USE_BUNDLED_JDK = TRUE
JDK_LOCATION = /usr/j2se
WEBSERVER_INSTALL_DIR = 
PLUGIN_TYPE = 
INST_ASADMIN_USERNAME = admin
INST_ASADMIN_PASSWORD = ngvismlhimdgfgqrrkqzvanqzva
INST_MASTER_PASSWORD = nwgxqgvrqhmeusidvuqzvanqzva
INST_ASADMIN_PORT = 4849
INST_ASWEB_PORT = 8080
INST_HTTPS_PORT = 8181
STORE_ADMIN_AUTH = FALSE
ADMIN_PASSWORD_ENCRYPTED = TRUE
INST_JMS_PORT = 7676
INST_ORB_PORT = 3700
INST_ORB_SSL_PORT = 3820
INST_ORB_MUTUALAUTH_PORT = 3920
INST_JMX_PORT = 8686
INST_DAS_HOSTNAME = localhost
INST_ASADMIN_USERNAME = admin
INST_ASADMIN_PASSWORD = ngvismlhimdgfgqrrkqzvanqzva
INST_ASADMIN_PORT = 4849
INST_MASTER_PASSWORD = nwgxqgvrqhmeusidvuqzvanqzva
CREATE_SAMPLES_DOMAIN = FALSE
CREATE_DESKTOP_SHORTCUT = FALSE
UPDATE_PATH = FALSE
[STATE_DONE J2EE 1.4 SDK 2860414c861c7b95a1287502663618e16472fc40]

Modifying the Installation Configuration File

You can modify the installation configuration file by editing the variables and values described in the following table.

You cannot reuse the configuration file created for a particular distribution on other distributions, editions, or versions of the Application Server software.

To view the results of the silent installation, refer to the log files.

Using the Installation Configuration File to Install in Silent Mode

To Install in Silent Mode

1. Review configuration file and verify that it contains what you want to use for your silent installation.

2. Copy your installation configuration file to each machine where you plan to install the Application Server software.

3. Copy the Application Server installation files to each machine where you plan to install the Application Server software.

4. Navigate to the directory where you copied the installation files and your installation configuration file.

5. Start silent installation at the command line using the following command format:

   ./distribution-filename -silent configuration-filename

   The installation program reads the specified configuration-filename, checks for adequate disk space, then installs the product based on the data in configuration-filename .

   When you return to the shell prompt, the silent installation is complete and the installation components are installed on your systems.

   Review the installation log files. For a list of these log files and their locations, see Installation Log Files.

6. Start the server.

   You can start the Application Server software by using the instructions in the Chapter 1, Getting Started, in Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.

   When the Admin Console is started, the initial page of the Application Server graphical interface is displayed.

   You are now ready to configure your system for high availability. To begin this process, see the Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide for information.

Installation Log Files

You can review the installation log files at:

• For Solaris SPARC and x86 root user: /var/sadm/install/logs/Install_Application_Server_8EE_timestamp.log

• For Solaris SPARC and x86 non-root user: /var/tmp/Install_Application_Server_8EE_timestamp.log

• For Linux root and non-root user: /var/tmp/Install_Application_Server_8EE_timestamp.log

• For Windows root and non-root user: %TEMP%\\Install_Application_Server_8EE_timestamp.log

You can review the low-level log files at:

• Solaris (root installation): /var/sadm/install/logs/Sun_Java_System_Application_Server_Enterprise_Edition_install.Btimestamp

• Solaris (non-root installation): /var/tmp/Sun_Java_System_Application_Server_Enterprise_Edition_install.Btimestamp

• Linux: /var/tmp/Sun_Java_System_Application_Server_Enterprise_Edition_install.Btimestamp

• Windows: %TEMP%\\Sun_Java_System_Application_Server_Enterprise_Edition_install.Btimestamp