Chapter 1 Installing Application Server Software

This chapter provides instructions for installing the Sun Java System Application Server software. It also has instructions for installing GlassFish^TM v2. The following topics are discussed:

• Distribution Types and Their Components

• Installing Application Server 9.1 Update 1 with MySQL Community Server

• Installing Application Server 9.1 Update 1

• Installing GlassFish v2

• Registering Your Installation of Application Server

Distribution Types and Their Components

The various distributions and their components are as follows:

• GlassFish - Includes the Application Server software, the Sun Java System Message Queue 4.1, Java DB, and ant 1.6.5. Download GlassFish from https://glassfish.dev.java.net/public/downloadsindex.html. You can run GlassFish on Solaris SPARC, Solaris x86, Linux, Windows, AIX, and Mac OS.

• Application Server 9.1 Update 1 with MySQL Community Server - Includes the Application Server software, MySQL Community Server, Java SE Development Kit (JDK) 5, Java DB, Sun Java System Message Queue 4.1.

  You can install this bundle on Solaris SPARC, Solaris x86, Linux, Windows, and Mac OS. On Mac OS systems, you need to download JDK separately because JDK is not part of the bundle for Mac OS.

• Application Server 9.1 Update 1 with HADB - Includes the Application Server software, load balancing plug-in, Java SE Development Kit (JDK) 5, Java DB, Sun Java System Message Queue 4.1, and HADB. The standalone Application Server 9.1 Update 1 is available at http://www.sun.com/download.

• Application Server 9.1 Update 1 without HADB - Includes the Application Server software, Java DB, and Sun Java System Message Queue 4.1. The standalone Application Server 9.1 Update 1 is available at http://www.sun.com/download.

• Java EE SDK : Application Server 9.1 is also part of the Java EE SDK and the Java Application Platform SDK. You can download these distributions from http://java.sun.com/javaee/downloads/index.jsp.

You can download the latest version of Sun Java System Access Manager Policy Agent 2.2 from http://www.sun.com/download. For more information on how the Access Manager Policy Agent works with the Application Server 9.1, see Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Application Server 9.0/9.1 on docs.sun.com.

Installing Application Server 9.1 Update 1 with MySQL Community Server

This section covers the following topics:

• To Install Application Server 9.1 Update 1 with MySQL Community Server

• To Install Application Server 9.1 Update 1 with MySQL Community Server in Silent Mode

• To Start MySQL

To Install Application Server 9.1 Update 1 with MySQL Community Server

Before You Begin

Use this procedure if you are using the CLI or GUI mode of the file-based installer for the Application Server 9.1 Update 1 with MySQL Community Server distribution. Verify that your system meets the requirements specified in Hardware and Software Requirements in Sun Java System Application Server 9.1 Update 1 Release Notes

Solaris and Linux installations support both root and non-root user installations. Users of Windows installations should have Power User or Administrator access. If you are installing as a non-root user on Solaris or Linux, 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. If you have downloaded a .bin file, change the permission of the distribution file so that you have execute access:

   chmod +x distribution_filename

3. Run the installation program.

   • If you are installing from a .bin file, use the following command to run the installation program :

     ./distribution_filename

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from a .zip file, unzip the file, navigate to the extracted folder, and run the following command:

     ./setup

     Use the -console option to run the installation program in command-line mode.

     On Mac OS systems, you need download JDK (version 1.5.0_12 or above) separately.

   • If you are installing from an .exe file on Windows, double-click the file.

4. Read and accept the license agreement.

5. Specify the directory where you want to install the software or accept the default installation directory.

   ---

   Caution –

   On Windows, ensure that there are no spaces within the installation directory you specify. Installation paths with embedded spaces are not supported.

   ---

6. Choose to install JDK 5 or use a pre-installed JDK 5.

7. In the Administration Configuration page (or when prompted 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).

   • Choose whether you want to be prompted for the Admin User Name and Password.

   • Admin Port – Administration port number for initial server instance. The default value is 4848.

   • HTTP Port - Port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • HTTPS Port - Secure port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • ---

     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 4848

     • 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. In the Installation Options page, select the options that you want. Installation Options are:

   • Upgrade from Previous Version: Select this option to upgrade from configuration data from an earlier installation of Application Server.

     ---

     Note –

     If you are running the installer in command-line mode, you need to run the asupgrade command manually.

     ---

   • Enable Updatecenter Client: Select this option to enable Updatecenter to check for available updates and collect system data.

   • Create Desktop Shortcut to the AutoDeploy directory: Select this option to automatically deploy items dragged to this directory. You see this option only if you are using Windows.

   • Add bin Directory to PATH: Select this option to add install-dir/bin to the PATH variable for simplifying the process of running the server and tools from the command line. You see this option only if you are using Windows.

   • Create a Windows Service for Application Server: Select this option to create a Windows Service for starting and stopping Application Server.

     ---

     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.

     ---

   • Create a Windows Service for MySQL Community Server: Select this option to create a Windows Service for MySQL, with startup type configured as manual.

9. In the MySQL Configuration panel, choose the size of your machine.

   This installation creates a preconfigured options or configuration file to be used for MySQL Community Server. The parameters in this options file depend on the size of your machine.

   • SMALL: Select this option for a system with 64 MB memory or lesser and does not run MySQL regularly. Ensure that mysqld daemon does not use many resources.

   • MEDIUM: Select this option for a system that has 32 MB - 64 MB memory and runs MySQL regularly. Select this option for a system with a maximum of 128 MB and if you are using MySQL with other software (such as a web server).

   • LARGE: Select this option for a system with 512 MB or lesser and runs mainly MySQL.

   • HEAVY: Select this option for a system with 4 GB of memory and runs mainly MySQL using InnoDB-only tables and performs complex queries with few connections.

   • HUGE: Select this option for a system with memory of 1 GB - 2 GB and runs mainly MySQL.

   After installation, the MySQL options file, mysql.ini, is created at install-dir/mysql. Refer http://dev.mysql.com/doc/refman/5.0/en/option-files.html for more information on the MySQL options file. Ensure that you read this option file and change values as appropriate and as documented at http://www.mysql.com, prior to server startup.

10. On the Ready to Install page, click Install Now.

11. After installation completes, use the Registration Options screen for registering your installation of application server. For instructions, see To Register Your Installation of Application Server.

Next Steps

After installing Application Server 9.1 Update 1 with MySQL Community Server, start the application server using the instructions at Starting the Server in Sun Java System Application Server 9.1 Quick Start Guide.

The MySQL installation is located at install-dir/mysql. Set up MySQL using the instructions at To Set Up MySQL, if you are using Solaris, Linux, or Mac OS. Start MySQL using the instructions at To Start MySQL.

Troubleshooting

For solutions to installation problems, see Chapter 3, Installation Problems, in Sun Java System Application Server 9.1 Troubleshooting Guide.

To Install Application Server 9.1 Update 1 with MySQL Community Server in Silent Mode

You can use this procedure only with theApplication Server 9.1 Update 1 with MySQL Community Server installer. 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.

On Solaris and Linux, for the graphical interface the syntax is:

./distribution_filename -savestate configuration_filename

On Solaris and Linux, for the command-line interface, the syntax is:

./distribution_filename -console -savestate configuration_filename

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

On Windows, 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.

Example 1–1 Installation Configuration File Example

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

#
# Wizard Statefile created: Fri Mar 21 11:42:36 IST 2008
#              Wizard path: /var/tmp/sjsasAAAvXaW4p/appserv.class
#

#
# Install Wizard Statefile section for Sun Java System Application Server
#
#
[STATE_BEGIN Sun Java System Application Server 
b146d7a741e40985b9d99975a81c9741253346b6]
defaultInstallDirectory = /SUNWappserver
currentInstallDirectory = /space/programs/as91ee/temp
JDK_LOCATION = /space/programs/as9/jdk5/jdk
INST_ASADMIN_USERNAME = admin
INST_ASADMIN_PASSWORD = ngghybgbednrreyatoqzvanqzva
INST_MASTER_PASSWORD = pgyrcyuakieqyuqlkurvunatrvg
INST_ASADMIN_PORT = 44517
INST_ASWEB_PORT = 44514
INST_HTTPS_PORT = 44520
STORE_ADMIN_AUTH = TRUE
ADMIN_PASSWORD_ENCRYPTED = TRUE
INST_JMS_PORT = 44532
INST_ORB_PORT = 44529
INST_ORB_SSL_PORT = 44535
INST_ORB_MUTUALAUTH_PORT = 44538
INST_JMX_PORT = 44541
CREATE_DESKTOP_SHORTCUT = FALSE
UPDATE_PATH = FALSE
CREATE_UPDATE_ICON = 
CREATE_WINDOWS_SERVICE = FALSE
CREATE_MYSQL_WINDOWS_SERVICE = FALSE
CREATE_DAS = TRUE
[STATE_DONE Sun Java System Application Server 
b146d7a741e40985b9d99975a81c9741253346b6]

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 needed. 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.

Next Steps

After installing Application Server 9.1 Update 1 with MySQL Community Server, start the application server using the instructions at Starting the Server in Sun Java System Application Server 9.1 Quick Start Guide.

The MySQL installation is located at install-dir/mysql. Set up MySQL using the instructions at To Set Up MySQL, if you are using Solaris, Linux, or Mac OS. Start MySQL using the instructions at To Start MySQL.

Troubleshooting

For solutions to installation problems, see Chapter 3, Installation Problems, in Sun Java System Application Server 9.1 Troubleshooting Guide.

To Start MySQL

This section covers the following topics:

• To Set Up MySQL

• To Start or Stop MySQL

To Set Up MySQL

You need to perform these steps only if you are using Solaris or Linux platforms.

1. Create a MySQL user account.

   Refer to your operating system manual for instructions on how to create a user account. It is recommended that you create an operating system user account called mysql and group called dba for performing MySQL operations. Ensure that install-dir/mysql and its subdirectories including the data directory are owned by this user account.

2. Initialize the grant tables.

   On Solaris, at the command prompt, you can use the following commands to initialize grant tables:

   1. cd install-dir/mysql.

   2. sh scripts/mysql_install_db --no-defaults --basedir=install-dir/mysql --datadir=install-dir/mysql/data

See Also

See http://dev.mysql.com/doc/refman/5.0/en/index.html for detailed post-installation instructions for setting up MySQL.

To Start or Stop MySQL

Before You Begin

On Solaris, Linux, or Mac OS, ensure that you have completed the steps at To Set Up MySQL. Ensure that you read this option file and change values as appropriate and as documented at http://www.mysql.com, prior to server startup.

1. To start MySQL:

   • On Solaris, Linux, or Mac OS, use the following command: Start: ./bin/mysqld_safe --defaults-file=install-dir/mysql/mysql.ini --user=user

   • On Windows, you can do one of the following:

     • Click Programs > Sun Microsystems > Sun Java SystemApplication Server 9.1 Update 1 with MySQL Community Server > Start MySQL 5.0 Database.

     • If you created a Windows service, start the ASMySQL service through the Control Panel.

2. To stop MySQL:

   • On Solaris, Linux, or Mac OS, use the following command: Stop: bin/mysqladmin -u root shutdown -p

   • On Windows, you can do one of the following:

     • Click Programs > Sun Microsystems > Sun Java SystemApplication Server 9.1 Update 1 with MySQL Community Server > Stop MySQL 5.0 Database.

     • If you created a Windows service, stop the ASMySQL service through the Control Panel.

Installing Application Server 9.1 Update 1

If you are using the Sun Java System Application Server 9.1 file-based installation, use one of the following procedures:

• To Install Application Server 9.1 Update 1 without HADB

• To Install Application Server 9.1 Update 1 with HADB

• To Install Application Server 9.1 Update 1 in Silent Mode

To Install Application Server 9.1 Update 1 without HADB

Before You Begin

Use this procedure if you are using the GUI or CLI mode of the file-based installer for the Application Server 9.1 distribution that does not include HADB. Verify that your system meets the requirements specified in Hardware and Software Requirements in Sun Java System Application Server 9.1 Update 1 Release Notes.

Solaris and Linux installations support both root and non-root user installations. Users of Windows installations should have Power User or Administrator access. If you are installing as a non-root user on Solaris or Linux, 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

• The web server installation directory and the web server instance directory, if applicable.

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

2. If you have downloaded a .bin file, change the permission of the distribution file so that you have execute access:

   chmod +x distribution_filename

3. Run the installation program.

   • If you are installing from a .bin file, use the following command to run the installation program :

     ./distribution_filename

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from a .zip file, unzip the file, navigate to the extracted folder, and run the following command:

     ./setup

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from an .exe file on Windows, double-click the file.

4. Specify the directory where you want to install the software or accept the default installation directory.

5. Choose to install JDK 5 or use a pre-installed JDK 5.

6. In the Administration Configuration page (or when prompted 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).

   • Choose whether you want to be prompted for the Admin User Name and Password.

   • Admin Port – Administration port number for initial server instance. The default value is 4848.

   • HTTP Port - Port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • HTTPS Port - Secure port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • ---

     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 4848

     • 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.

     ---

7. In the Installation Options page, select the options that you want. Installation Options are:

   • Upgrade from Previous Version: Select this option to upgrade from configuration data from an earlier installation of Application Server.

     ---

     Note –

     If you are running the installer in command-line mode, you need to run the asupgrade command manually.

     ---

   • Enable Updatecenter Client: Select this option to enable Updatecenter to check for available updates and collect system data.

   • Create Desktop Shortcut to the AutoDeploy directory: Select this option to automatically deploy items dragged to this directory. You see this option only if you are using Windows.

   • Add bin Directory to PATH: Select this option to add install-dir/bin to the PATH variable for simplifying the process of running the server and tools from the command line. You see this option only if you are using Windows.

   • Create Windows Service: Select this option to create a Windows service to start and stop Application Server,

     ---

     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.

     ---

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

   ---

   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.

   ---

9. After installation completes, use the Registration Options screen for registering you installation of application server. For instructions, see To Register Your Installation of Application Server.

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

    If you have problems with your installation, see the known issues and limitations in Installation in Sun Java System Application Server 9.1 Update 1 Release Notes.

See Also

The Application Server 9.1 Update 1 bundle without HADB does not include the load balancing plug-in. You can download and install the load balancing plug-in separately. For instructions, see To Install the Load Balancing Plug-in (standalone).

To Install Application Server 9.1 Update 1 with HADB

Before You Begin

Use this procedure if you are using the GUI or CLI mode of the file-based installer for the Application Server 9.1 distribution that includes HADB. Verify that your system meets the requirements specified in Hardware and Software Requirements in Sun Java System Application Server 9.1 Update 1 Release Notes.

Solaris and Linux installations support both root and non-root user installations. Users of Windows installations should have Power User or Administrator access. If you are installing as a non-root user on Solaris or Linux, 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

• The web server installation directory and the web server instance directory, if applicable.

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

2. If you have downloaded a .bin file, change the permission of the distribution file so that you have execute access:

   chmod +x distribution_filename

3. Run the installation program.

   • If you are installing from a .bin file, use the following command to run the installation program :

     ./distribution_filename

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from a .zip file, unzip the file, navigate to the extracted folder, and run the following command:

     ./setup

     Use the -console option to run the installation program in command-line mode.

   • If you are installing from an .exe file on Windows, double-click the file.

4. Specify the directory where you want to install the software or accept the default installation directory.

5. Select the components to install. If you are using a Application Server bundle without HADB, you will not see this screen.

   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 -This component stores session information so requests can be failed over if you are using the load balancing plug-in.

   • Load Balancing Plug-in - Install the load balancing plug-in 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 plug-in, you cannot continue to install the load balancer plug-in. Supported web servers are Sun Java System Web Server 6.1 and above (including 7.0), Apache 2.0.x, and IIS 5.0 and above.

   • 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 plug-in 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.

   ---

   Note –

   Before you run incremental installation of Application Server 9.1 Update 1 components, ensure that server processes are stopped if Domain Administration Server or Node Agent component is pre-installed on the machine

   ---

6. Choose to install JDK 5 or use a pre-installed JDK 5.

7. If you selected the load balancing plug-in component:

   1. Select the Web Server you have installed. Ensure that you have installed a supported web server. For a list of supported web servers, see Web Servers in Sun Java System Application Server 9.1 Update 1 Release Notes.

   2. If you have Sun Java System Web Server, provide the install-dir and the instance-dir. If you have Apache web server or IIS, provide the install-dir.

   3. If you have created a DAS certificate for the Apache web server , automatically import the certificate by providing the Certificate file location.

      The Certificate file location is the location of the DAS certificate file. Ensure that you provide the path to certificate file inclusive of the name of the certificate file.

      Automatic import of DAS certificate is supported only for Apache web server. If you are using Apache web server, install Application Server without the load balancing plug-in. After installing Application Server, create and export a DAS certificate by using the certutil utility, and run the Application Server installer again to install the load balancing plug-in. For instructions on how to create and export DAS certificate for Apache web server, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server 9.1 High Availability Administration Guide

      If you are using Sun Java System Web Server or IIS, you will need to manually import the DAS certificate. You need to install load balancer without a DAS certificate. After installing the load balancing plug-in, you can create a DAS certificate and manually import it. For instructions, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server 9.1 High Availability Administration Guide.

8. If you are installing the load balancing plug-in 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 plug-in 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 plug-in libraries.

   ---

   The Installation Summary page is displayed indicating the installation status.

9. In the Administration Configuration page (or when prompted 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).

   • Master Password — The master password (8-character minimum).

   • Choose whether you want to be prompted for the Admin User Name and Password.

   • Admin Port – Administration port number for initial server instance. The default value is 4848.

   • HTTP Port - Port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • HTTPS Port - Secure port number to access the default server instance. You need to provide this value only if you had selected to install DAS.

   • Node agent name — A name for the node agent. You need to provide this value only if you had selected the Node Agent option.

   • ---

     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 4848

     • 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.

     ---

10. In the Installation Options page, select the options that you want. Installation Options are:

    • Upgrade from Previous Version: Select this option to upgrade from configuration data from an earlier installation of Application Server.

      ---

      Note –

      If you are running the installer in command-line mode, you need to run the asupgrade command manually.

      ---

    • Enable Updatecenter Client: Select this option to enable Updatecenter to check for available updates and collect system data.

    • Create Desktop Shortcut to the AutoDeploy directory: Select this option to automatically deploy items dragged to this directory. You see this option only if you are using Windows.

    • Add bin Directory to PATH: Select this option to add install-dir/bin to the PATH variable for simplifying the process of running the server and tools from the command line. You see this option only if you are using Windows.

    • Create Windows Service: Select this option to create a Windows service to start and stop Application Server,

      ---

      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.

      ---

11. On the Ready to Install page, click Install Now.

12. After installation completes, use the Registration Options screen for registering you installation of application server. For instructions, see To Register Your Installation of Application Server.

13. Verify the installation by following the procedures in the Sun Java System Application Server 9.1 Quick Start Guide, located in install-dir/docs/QuickStart.html or on docs.sun.com.

    If you have problems with your installation, see the known issues and limitations in Installation in Sun Java System Application Server 9.1 Update 1 Release Notes.

Next Steps

If you have installed load balancing plug-in, you need to configure Web Server for load balancing. For detailed instructions on configuring Web Server for load balancing, see Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server 9.1 High Availability Administration Guide.

To Install Application Server 9.1 Update 1 in Silent Mode

You can use this procedure only with the Sun Java System Application Server 9.1 Update 1 installer. GlassFish v2 does not offer Silent Mode installation. Silent mode installation is non-interactive. You cannot use the Silent Mode if you are installing the load balancing plug-in on Web Server 7.0. 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.

On Solaris and Linux, for the graphical interface the syntax is:

./distribution_filename -savestate configuration_filename

On Solaris and Linux, for the command-line interface, the syntax is:

./distribution_filename -console -savestate configuration_filename

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

On Windows, 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.

Example 1–2 Installation Configuration File Example

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

#
# Wizard Statefile created: Mon Apr 30 11:42:36 IST 2007
#              Wizard path: /var/tmp/sjsasAAAvXaW4p/appserv.class
#

#
# Install Wizard Statefile section for Sun Java System Application Server
#
#
[STATE_BEGIN Sun Java System Application Server 
b146d7a741e40985b9d99975a81c9741253346b6]
defaultInstallDirectory = /SUNWappserver
currentInstallDirectory = /space/programs/as9ee/temp
JDK_LOCATION = /space/programs/as9/jdk5/jdk
INST_ASADMIN_USERNAME = admin1
INST_ASADMIN_PASSWORD = ngghybgbednrreyatoqzvanqzva
INST_MASTER_PASSWORD = pgyrcyuakieqyuqlkurvunatrvg
INST_ASADMIN_PORT = 44517
INST_ASWEB_PORT = 44514
INST_HTTPS_PORT = 44520
STORE_ADMIN_AUTH = TRUE
ADMIN_PASSWORD_ENCRYPTED = TRUE
INST_JMS_PORT = 44532
INST_ORB_PORT = 44529
INST_ORB_SSL_PORT = 44535
INST_ORB_MUTUALAUTH_PORT = 44538
INST_JMX_PORT = 44541
CREATE_DESKTOP_SHORTCUT = FALSE
UPDATE_PATH = FALSE
CREATE_UPDATE_ICON = 
CREATE_WINDOWS_SERVICE = FALSE
CREATE_DAS = TRUE
[STATE_DONE Sun Java System Application Server 
b146d7a741e40985b9d99975a81c9741253346b6]

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 needed. 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 .

Installing GlassFish v2

This section provides instructions for installing GlassFish v2 distribution and for installing the load balancing plug-in for GlassFish v2. This distribution does not support upgrades or patching.

• To Install GlassFish Application Server

• To Install the Load Balancing Plug-in (standalone)

To Install GlassFish Application Server

Before You Begin

Get JDK (Java SE Development Kit) 5 or higher from http://java.sun.com/javase/, if you are using Solaris, Linux, or Windows.

If you are using Mac OS X, you need to download JDK 5 (supported on Mac OS X 1.4 or later) from http://www.apple.com/support/downloads/java2se50release3.html and make JDK 5 the default JVM.

If you are using AIX, download JDK 5 from: http://www.ibm.com/developerworks/java/jdk/aix/service.html.

1. Download the GlassFish v2 distribution https://glassfish.dev.java.net/public/downloadsindex.html.

2. Set the environment variable JAVA_HOME to point to the directory in which JDK 5 is installed.

3. Run the following command:

   java -Xmx256m -jar <filename>.jar

4. Set ANT_HOME to point to the ant 1.6.5 installation, which is at <downloaded-dir>/glassfish/lib/ant directory.

5. Navigate to the glassfish directory:

   cd glassfish

6. If you do not want clustering capabilities, run the following command:

   ant -f setup.xml

   • If you want to use GlassFish with clustering, change the command to:

     ant -f setup-cluster.xml

7. Use the Admin Console or Update Center to register your installation of GlassFish. Start GlassFish using the instructions at Starting the Server in Sun Java System Application Server 9.1 Quick Start Guide.

To Install the Load Balancing Plug-in (standalone)

Use the procedures in this section if the load balancing plug-in is not part of the Application Server distribution you are using. If you are using the Sun Java System Application Server 9.1 (bundle with HADB), see To Install Application Server 9.1 Update 1 with HADB for instructions for installing the load balancing plug-in.

The load balancing plug-in is not currently bundled with the GlassFish v2Application Server. If you want load balancing capabilities, you can download the load balancing plug-in from the following locations:

• Solaris (SPARC): http://download.java.net/javaee5/external/SunOS/aslb/jars/

• Solaris (x86): http://download.java.net/javaee5/external/SunOS_X86/aslb/jars/

• Linux: http://download.java.net/javaee5/external/Linux/aslb/jars/

• Windows: http://download.java.net/javaee5/external/WINNT/aslb/jars/

• Mac OS: http://download.java.net/javaee5/external/Darwin/aslb/jars/

• AIX: http://download.java.net/javaee5/external/AIX/aslb/jars/

1. Before you install the load balancer plug-in, ensure that you have installed a supported web server. For a list of supported web servers, see Web Servers in Sun Java System Application Server 9.1 Update 1 Release Notes.

2. Create the lbplugin directory within <glassfish_install_dir>/lib.

3. Unjar this file in the lbplugin directory. Run the following command: jar -xvf <lbplugin>.jar.

4. Unzip the following two files: SUNWaslb.zip and SUNWaspx.zip in the same directory. Delete the zip files.

5. Change permissions on all shared libraries within lbplugin directory. Run the following command: chmod -R 755 ${glassfish.home}/lib/lbplugin/lib.

6. Create a configuration for the load balancer. See Setting up Load Balancing in Sun Java System Application Server 9.1 Quick Start Guide.

7. Restart the Web Server after creating a configuration for the load balancer.

Next Steps

You need to configure Web Server for load balancing. For detailed instructions on manually configuring Web Server for load balancing, see Configuring Sun Java System Web Server in Sun Java System Application Server 9.1 High Availability Administration Guide.

Registering Your Installation of Application Server

This section explains how to register your installation of Application Server 9.1 with Sun Connection.

To Register Your Installation of Application Server

To register your installation of Sun Java System Application Server 9.1 Update 1 with Sun Connection, you must have a Sun Online Account. If you do not have a Sun Online Account, the Application Server installer enables you to create an account while registering Application Server.

If you create a Sun Online Account while registering Application Server 9.1 Update 1, you are prompted only for the required information. You can provide additional, optional information by updating your Sun Online Account.

1. In the Product Registration screen, provide the required information as follows:

   • If you already have a Sun Online Account, provide the required information as follows:

     1. Select the I Already Have a Sun Online Account option.

     2. In the User Name field, type the user name that you specified when registered for your Sun Online Account.

     3. In the Password field, type that you specified when registered for your Sun Online Account.

     4. Click Register.

   • If you do not have a Sun Online Account, provide the required information as follows:

     1. Select the I Don't Have a Sun Online Account option.

     2. In the Email Address field, type your email address.

        Your email address will be your Sun Online Account user name.

     3. In the Password field, type the password to use for your Sun Online Account.

        The password is case sensitive and must be 6 – 10 characters long.

     4. In the Retype Password field, retype the password that you typed in the preceding step.

     5. In the First Name field, type your first name.

     6. In the Last Name field, type your last name.

     7. In the Company Name field, type the name of your company.

     8. From the drop down list, select the country or territory where you reside.

     9. Click Register.

   • Choose the Skip Registration option if you want to register later through the Admin Console or through the Update Center.