This section provides instructions for installing the Application Server software.
After you have planned the topology, run the installation program.
For more information on planning topology, see Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Deployment Planning Guide.
To run the installation program that uses the graphical interface, at the command prompt, type:
./bundle_filename
To run the installation program that uses the command-line interface, at the command prompt, type:
./bundle_filename -console
If you are installing the load balancer plug-in, your web server must already be installed. Refer to Installing the Load Balancer Plug-in Component.
Follow the installation wizard screens to accept the license agreement.
Specify the path to the Application Server installation directory or accept the default installation directory.
Select the components to install.
If a component is disabled, the installation program has detected it as already installed on your system.
If you do not already have your web server installed on the machine where you are installing the load balancer plug-in, you cannot continue to install the load-balancer plug-in.
Choose to install the Java 2 SDK, or use a preinstalled Java 2 SDK.
If the correct version of the Java 2 SDK is installed, it is reused or you can enter the path to another correct version.
If no Java 2 SDK is installed, you can choose to let the installation program install the Java 2 SDK package automatically.
If you choose to install the Java 2 SDK, a private copy is installed in install_dir.
The default Java 2 SDK installation path for all platforms is install_dir/jdk.
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.
The default server domain directory is: install_dir/domains.
If you selected the load balancer plug-in component, identify your web server and its installation directory.
In the Admin Configuration page (or at the command line), enter the following:
Password—Admin user’s password to access the Admin Server (8-character minimum)
Master Password—SSL certificate database password, used in operations such as Domain Administration Server startup
Admin Port—Port number to access the Domain Administration Server
HTTPS Port—Secure port number to access the default server instance
The installation program automatically detects ports in use and suggests unused ports for the default settings.
The default ports are 4849 for the Admin Server, 8080 for the HTTP Server, and 8181 for the HTTPS Server.
In the Node Agent Configuration page, if you are installing the Node Agent only, and not the Domain Administration Server, enter the following:
Admin User Name—Name of the user who administers the server
Admin Password—Admin user’s password (8-character minimum)
Master Password—SSL certificate database password, used in operations such as Node Agent startup
Admin Host Name—Host name of the Domain Administration Server
Admin Port—Port number to access the default server instance
Node Agent Name—Defaults to the system host name
The admin user name, admin password, master password, admin host name and admin port parameters should correspond to the location and authentication information of the Domain Administration Server, which is used to administer node agent and server instances on this system.
If the Domain Administration Server is already installed on hostname.com using these values:
Admin User Name: admin
Admin Password: adminadmin
Master Password: masterpassword
Host Name: hostname
Admin Port: 4849
Enter these same values while installing Application Server on another system.
Because node agent names must be unique within each server domain, it is recommended that you do not change the node agent name.
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. For information about upgrading, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Upgrade and Migration Guide.
The installation program verifies the available disk space on your machine.
If you do not have enough disk space, an error message is displayed. Consult the Platform Requirements in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Update 2 Release Notes to identify the minimum disk space required.
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).
When the installation is complete, read the installation summary page to determine the status of the installation. If the installation is successful, click Finish.
If the installation is unsuccessful, consult the log files located 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
ForLinux 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
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
Start the server.
See the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide in the install_dir/docs-ee directory or online for information about starting the server.
If you selected the HADB components:
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.
Configure your system for high availability. See the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide for information.