Chapter 1 Installing Application Server Software

This chapter provides instructions for installing the Sun Java System Application Server Platform Edition software in the Application Server distribution. The following topics are discussed:

• Distribution Types and Their Components

• Installing the Software

• Installing in Silent Mode

Solaris and Linux installations support both root and non-root user installations. Users of Windows installations should have Power User or Administrator access.

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

• Platform Edition is Java Platform, Enterprise Edition (Java EE) 5 compatible, 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 continuity with a load balancer plug-in 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 for the session state failover.

Distribution Types and Their Components

The Application Server product distribution includes the following components:

• Application Server software, including administrative tools and utilities

• Sun Java System Message Queue

• Java DB

Use the following instructions to install all distributions.

Installing the Software

After you have verified that your system meets the requirements specified in Hardware and Software Requirements in Sun Java System Application Server Platform Edition 9 Release Notes, use either of the following procedures to install the Application Server product.

If you are installing on a Solaris 10 system, Application Server can be installed either in the global zone or a non-global zone. For more information on zones, see the Solaris 10 documentation.

To Install on Solaris or Linux

Before You Begin

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. Navigate to the directory where you downloaded the distribution file.

2. Change the permission of the distribution file so that you have execute access:

   chmod +x distribution_filename

   The distribution file name changes depending upon the distribution, version, and platform, in the format sjas_pe-version-platform.bin or java_ee_sdk-version-platform.bin. For example, for the Linux Application Server distribution, the file is sjsas_pe-9_0-linux.bin. For the Linux Java EE SDK distribution, the file is java_ee_sdk-5-linux.bin or java_ee_sdk-5–soa_kit-preview-linux.bin.

3. Run the installation program.

   • To run the installation program that uses a graphical interface, at the command prompt, type the name of the distribution file:

     ./distribution_filename

   • To run the installation program that uses the command-line interface, at the command prompt, type the name of the distribution file followed by the -console option:

     ./distribution_filename -console

4. In the Administration Configuration page (or at the command line), enter the following:

   • Admin User Name – Name of the user who administers the server.

   • Password – Admin user’s password to access the Admin Server (8-character minimum).

   • Prompt or Don't Prompt for Administrator User Name – The user name can be stored in a preferences file so that you do not have to provide it to perform administrative tasks.

   • Admin Port – Administration port number for initial server instance.

   • HTTP Port – Port number to access the default server instance.

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

5. Enter the directory where you want to install the software.

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

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

7. In the Java EE SDK SOA Starter Kit Preview distribution, choose whether to install Project Open ESB Starter Kit as an add-on.

   Project Open ESB Starter Kit implements an enterprise service bus (ESB) runtime that incorporates the JSR 208 specification for Java Business Integration (JBI) and other open standards. Open ESB Starter Kit allows you to integrate web services and enterprise applications as loosely coupled composite applications within a service-oriented architecture (SOA).

   Open ESB Starter Kit includes a Business Process Execution Language (BPEL) service engine, a Java EE service engine, an HTTP SOAP binding component, and examples that demonstrate using the BPEL service engine. Additional components, tools, and documentation are available for download. Refer to http://java.sun.com/integration/openesb/starterkit.jsp for more information on the Open ESB Starter Kit and the additional components, tools, and documentation that are available.

8. On the Ready to Install page click Install Now.

9. After the installation completes, set the PATH environment variable to include the Application Server install-dir/bin directory.

10. Verify the installation by following the instructions in the Sun Java System Application Server Platform Edition 9 Quick Start Guide, located in install-dir/docs/QuickStart.html or on docs.sun.com.

    If you have problems with your installation, or with starting the server, see the Sun Java System Application Server Platform Edition 9 Troubleshooting Guide.

To Install on Windows

1. Navigate to the directory where you downloaded the .exe file.

2. Double-click the .exe file to start the installation program.

   The executable file name changes depending upon the distribution and version, in the format sjas_pe-version-windows.exe or java_ee_sdk-version-windows.exe. For example, for the Application Server distribution, the file is sjsas_pe-9_0-windows.exe. For the Java EE SDK distribution, the file is java_ee_sdk-5-windows.exe or java_ee_sdk-5-soa_kit-preview-windows.exe.

3. Follow the instructions on the wizard screens of the installation program.

4. In the Admin Configuration page (or at the command line), enter the following:

   • Admin User Name – Name of the user who administers the server.

   • Password – Admin user’s password to access the Admin Server (8-character minimum).

   • Prompt or Don't Prompt for Administrator User Name – The user name can be stored in a preferences file so that you do not have to provide it to perform administrative tasks.

   • Admin Port – Administration port number for initial server instance.

   • HTTP Port – Port number to access the default server instance.

   • HTTPS Port – Secure port number to access the initial server instance.

5. Enter the directory where you want to install Application Server.

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

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

   ---

   Note –

   To create a Windows service, the sc.exe utility must be available on the system. Windows 2000 users may need to install the Windows 2000 Resource Kit to get this utility. For other supported Windows versions, the utility is included in the operating system.

   ---

7. In the Java EE SDK SOA Starter Kit Preview distribution, choose whether to install Project Open ESB Starter Kit as an add-on.

   Project Open ESB Starter Kit implements an enterprise service bus (ESB) runtime that incorporates the JSR 208 specification for Java Business Integration (JBI) and other open standards. Open ESB Starter Kit allows you to integrate web services and enterprise applications as loosely coupled composite applications within a service-oriented architecture (SOA).

   Open ESB Starter Kit includes a Business Process Execution Language (BPEL) service engine, a Java EE service engine, an HTTP SOAP binding component, and examples that demonstrate using the BPEL service engine. Additional components, tools, and documentation are available for download. Refer to http://java.sun.com/integration/openesb/starterkit.jsp for more information on the Open ESB Starter Kit and the additional components, tools, and documentation that are available.

8. On the Ready to Install page choose Install Now.

9. After the installation completes, if you did not select the corresponding option on the Installation Options screen, set the PATH environment variable to include the Application Server install-dir/bin directory.

10. Verify the installation by following the instructions of the Sun Java System Application Server Platform Edition 9 Quick Start Guide, located in install-dir/docs/QuickStart.html or on docs.sun.com.

    If you have problems with your installation, or with starting the server, see Sun Java System Application Server Platform Edition 9 Troubleshooting Guide.

Installing in Silent Mode

Silent mode installation is non-interactive. You must first provide a configuration file for information that the installer needs. 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 when starting an interactive installation. During the interactive installation, your input is collected and stored in the configuration file you specified. This file 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.

Creating the Installation Configuration File on Solaris and Linux

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.

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 executable 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

The following example shows an installation configuration file created by running the installation program with the savestate option.

Example 1–1 Installation Configuration File

#
# Wizard Statefile created: Tue Apr 04 17:08:17 PDT 2006
#              Wizard path: /var/tmp/java_AAAocaG3p/appserv.class
#

#
# Install Wizard Statefile section for J2EE 1.4 SDK
#
#
[STATE_BEGIN J2EE 1.4 SDK b2e8342ca21cf327c40510acc9b263256d0eac49]
defaultInstallDirectory = /opt/SUNWappserver
currentInstallDirectory = /opt/SUNWappserver
INST_ASADMIN_USERNAME = admin
INST_ASADMIN_PASSWORD = nmdgvyigxssrgokyuhqzvanqzva
INST_MASTER_PASSWORD = pohuxqmnjckmaxhiwyqgunatrvg
INST_ASADMIN_PORT = 4848
INST_ASWEB_PORT = 8080
INST_HTTPS_PORT = 8181
STORE_ADMIN_AUTH = TRUE
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
CREATE_DESKTOP_SHORTCUT = FALSE
UPDATE_PATH = FALSE
SELECTED_ADDONS = 
[STATE_DONE J2EE 1.4 SDK b2e8342ca21cf327c40510acc9b263256d0eac49]

Modifying the Installation Configuration File

You can modify the installation configuration file by editing the variables and values described in the following table. This table has four columns showing variable names, valid values (if applicable), contents, and comments.

Using the Installation Configuration File to Install in Silent Mode

After creating the configuration file, use it to install Application Server in silent mode as many times as you want. Use the following procedure:

To Install in Silent Mode

1. Review the installation configuration file and verify that it contains the values to use for your silent installation.

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

3. Copy the Application Server distribution file to each machine where you plan to install the software.

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

5. Start silent installation at the command line using one of the following command formats:

   • On Solaris or Linux:

     ./distribution_filename -silent configuration_filename

   • On Windows:

     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 the prompt is returned, the silent installation is complete and the installation components are installed on your systems.

6. Start the Application Server software by using the instructions in the Sun Java System Application Server Platform Edition 9 Administration Guide.