Sun ONE Application Server 7, Enterprise Edition Installation Guide |
Chapter 2
Installing Enterprise Edition SoftwareThis chapter provides instructions for installing the Sun ONE Application Server 7, Enterprise Edition product. You can install this version of the product interactively or you can use silent mode to replicate an installation scenario on multiple machines. Refer to "Installation Roadmap" to see the full sequence of events for implementing the Sun ONE Application Server 7, Enterprise Edition product.
The following topics are addressed here:
You should be familiar with the information in "Preparing to Install" before beginning the tasks in this chapter.
For any late-breaking updates to these instructions, check the Sun ONE Application Server Release Notes. For more information about configuring your application server after installation, refer to the Sun ONE Application Server Administrator’s Guide.
The following location contains product downloads in addition to other useful information:
http://www.sun.com/software/products/appsrvr/home_appsrvr.html
About InstallationOnly one Sun ONE Application Server 7 installation can reside on a single machine. If an installation of Application Server 7 already exists on your system, the installation program will not overwrite it, but the pre-existing installation will be detected and you will not be allowed to proceed with the installation until you have removed the existing Application Server 7 software using the uninstallation program.
Note
Solaris 9 bundled installations and non-package-based evaluation installations do not affect the Enterprise Edition installation program, so they do not need to be removed from your system.
The following topics are addressed in this section:
Installation Components
In general, you are installing the basic components that provide the functionality of the Sun ONE Application Server Version 7, Enterprise Edition product. 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 dependencies are met.
Since only one installation of the same component package on the same system is allowed, the installation program tries to detect components that are already installed. If a component is already installed, installation of that component is disabled.
The installation program enforces component dependencies as specified for each component. Once component dependencies are satisfied, component life cycles are independent. A particular component can be installed or uninstalled dynamically through incremental installation and partial uninstallation mechanisms without corrupting other components.
The following installation components are included with the Sun ONE Application Server 7, Enterprise Edition product:
- Sun ONE Application Server—all of Sun ONE Appserver 7, including its graphical and command-line administrative tools, the asadmin command, and Sun ONE Message Queue 3.0.1
Note
If you want to install the Application Server and an HADB server node on the same system, select both components. Otherwise select only one of them.
The clsetup command must be run from a machine where the asadmin and the hadbm utilities are available. Instructions for using the clsetup command to create a basic cluster can be found in "Using the clsetup Command" on page 65.
- Sun ONE Application Server Administration Client—only the asadmin command
- Java 2 Software Development Kit (J2SE), Standard Edition 1.4.0_03
- Sample applications (Optional)
- High-Availability Database (HADB)—all of HADB, including the hadbm command
- HADB Management Client—only the hadbm command
- Load balancer plug-in for web servers
The load balancer plug-in is usually installed in a separate process on a separate machine. Refer to "Installing the Load Balancer Plug-in" for guidelines.
See "Installation Components" for further description of the Sun ONE Application Server components.
Installation Options
There are three ways you can perform the installation:
- Graphical method (interactive)—The installation program prompts you using a sequence of graphical screens. This is the default method.
- Command-line method (interactive)—The installation program prompts you using a sequence of command-line prompts and messages.
- Silent mode—The installation program reads installation parameters from a supplied configuration file and logs all output into a log file.
The setup command allows you to specify the method you want to use for installation, and allows you to create a configuration file for silent installation.
Note
The default installation mode is the graphical method, so if you don’t specify an option when you run setup, the installation program presents the graphical screens.
Use the following syntax when running the setup command:
Table 2-1 describes the setup command options.
Table 2-1 Options for the setup Command
Option
Description
-console
Runs the installation using the command-line method.
-silent config_file
Runs the installation in silent mode. Installation parameters are read from an existing installation configuration file. This option is mutually exclusive with the savestate option.
The installation configuration file path must be explicitly provided; there is no default file path. Refer to "Installing in Silent Mode (Non-Interactive)" for further specifics on silent mode installation and the installation configuration file.
-savestate
Runs the installation using either the graphical or command-line method and creates an installation configuration file based on this installation. This option is mutually exclusive with the silent option. If you do not specify this option, no installation configuration file will be created.
The file will be called statefile and located in install_dir.
Installation Syntax
./setup -silent config_file
Refer to "Installing in Silent Mode (Non-Interactive)" for further specifics on silent mode installation and the installation configuration file.
Installing Application Server SoftwareThis section provides instructions for installing the Sun ONE Application Server software using either the graphical-interface or command-line interface. The steps are identical for both methods. However, for the command-line interface, text-based screens are displayed instead of graphical screens.
Tip
If you are familiar with high availability concepts and installation of enterprise-level products, you may want to use the summary checklists in Appendix A, "Installation Cheatsheet."
After you have planned the topology, run the installation program on each system, selecting and installing the appropriate components based on your topology.
- Uninstall any previous versions of the Sun ONE Application Server 7 software on the machines where you are going to install the Enterprise Edition of the Application Server.
Note
If the previously-installed packages are bundled in the Solaris operating environment, they need not be removed. However, port conflicts must be resolved.
- Verify that all requirements that apply to your installation have been met. See "Installation Requirements" for information on requirements.
- Log in as root and create a temporary directory for the product distribution file.
Note
If you are installing the load balancer plug-in, your web server must already be installed on the machines where you are going to install the load balancer plug-in before you start the installation process. Refer to "High-Availability Requirements".
- Start all the processes on your system that use ports and are expected to run at the same time as the Application Server software. This allows the installation program to detect what ports are in use and avoid assigning them for other purposes.
- For a download, unzip the .gz file as follows:
gunzip sun-appserver7-sol.tar.gz
- For a download, untar the unzipped file as follows:
tar -xvf sun-appserver7-sol.tar
This process may take a little time. When the files are unpacked, you will see the sun-appserver7 directory, which contains the setup file and the pkg directory.
- Navigate to the sun-appserver7 directory.
- Select your installation method.
Refer to "Installation Options" for guidelines on selecting the correct options to use with the setup command.
When the installation starts, the Welcome page of the installation program is displayed.
- Read the Welcome page and click Next.
The License Agreement page is displayed.
- Read the License Agreement and click Yes to agree to the terms of the license (or type Yes at the command line), then click Next.
After you accept the License Agreement, the Select Installation Directory page is displayed.
- Specify the path to your Sun ONE Application Server installation directory (default is /opt/SUNWappserver7).
If you are installing only the HADB Server component, you can choose /opt as the installation directory. This will install the HADB packages into their default location, which is /opt/SUNWhadb.
- Choose from the components listed on the Component Selection page (or type Yes or press Enter to accept a component from the command line).
- Sun ONE Application Server, with graphical and command-line interfaces (J2SE and Sun ONE Message Queue are installed along with this component)
Note
If you want to install Sun ONE Application Server and an HADB server node on the same system, select them both. Otherwise, select only one of them.
- (Optional) Sample Applications
- Sun ONE Application Server Administration Client (select only this component to install standalone command-line)
- High-Availability Database
- High-Availability Database Administration Client
- Load Balancer Plug-in
Refer to "Installing the Load Balancer Plug-in" for instructions on installing this component separately.
- Sun ONE Message Queue—If the installation program detects a version of the Sun ONE Message Queue preinstalled in your system, you are presented with one of the following actions:
- If the correct version of the package-based Sun ONE Message Queue is installed, it will be reused. You can choose to exit at this point. If you don’t exit, the installation program will use the installed version and proceed to the next step.
- If there is no package-based Sun ONE Message Queue installed, you can choose to let the installation program install the Sun ONE Message Queue packages automatically.
- If an incorrect version of the package-based Sun ONE Message Queue is found, a message is displayed, asking if you want to upgrade your current version or cancel. Choose one of the following:
- For J2SE—The installation program looks in the /usr/j2se default location to detect if you have the correct version of the J2SE preinstalled in your machine.
You are presented with one of the following actions (if you have any problems in this step, refer to "J2SE Installation/Upgrade Issues"):
- If the correct version of the package-based J2SE is installed, it will be reused or you can enter the path to another correct version. The installation program proceeds to the next step.
- If there is no package-based J2SE installed, you can choose to let the installation program install the J2SE package automatically or reuse an existing J2SE installation.
- If an incorrect version of the package-based J2SE is found, a message is displayed asking if you want to upgrade your current version or cancel. Choose one of the following options:
- To have the installation program update your current J2SE version, click Upgrade (or type 1 at the command line).
- To exit the installation program, click Cancel (or type 2 at the command line).
Before continuing with the installation, you must uninstall the J2SE currently located in /usr/j2se or upgrade it to J2SE 1.4.1_03. Then restart the Application Server installation.
Note
If your J2SE requires an upgrade, you will need to reboot your machine after completing the Application Server installation.
- Specify your product configuration directory.
Accept the default (/etc/opt/SUNWappserver7) or enter the path to your Sun ONE Application Server product configuration directory.
- Click the ellipsis (...) to browse for a directory (or press Enter at the command line to accept the default installation directory).
- If the directory does not already exist, the Create New Directory? dialog is displayed.
- Click Create Directory (or type 1 at the command line). You can also click Choose New (or type 2 at the command line) to select an existing directory.
- Specify your server configuration directory.
Accept the default (/var/opt/SUNWappserver7) or enter the path to your Sun ONE Application Server Version 7, Enterprise Edition domains installation directory.
- Click the ellipsis (...) to browse for a directory (or press Enter at the command line to accept the default installation directory).
- If the directory does not already exist, the Create New Directory? dialog is displayed.
- Click Create Directory (or type 1 at the command line). You can also click Choose New (or type 2 at the command line) to select an existing directory.
If you selected Application Server for installation, the Server Configuration Information page is displayed. Skip to Step 18.
If you selected the load balancer plug-in, the Web Server Directory page is displayed. Proceed to Step 17
- If you selected the load balancer plug-in, identify your web server as follows:
Default values will be offered based on web server type. The installation program checks to see if appropriate configuration files can be found at the provided location.
Refer to "Installing the Load Balancer Plug-in" if you are installing the load balancer plug-in separately.
- If you selected the Sun ONE Application Server component, enter the following:
- HTTP Server Port—Port number to access the default server instance.
A default port number is displayed (for example 80, if that port is not in use on your machine). Change the default number if necessary. The installation program will check port numbers for validity and availability when you click Next.
- Click Next.
The installation program proceeds to verify that you have enough disk space based on the components you selected. The Checking Disk Space progress indicator bar is displayed.
- If you do not have enough disk space, an error message is displayed.
In this case, you need to exit the installation program, create enough space, and restart the installation. Information on space requirements is contained in "Platform Requirements".
- If you have enough disk space, the Ready to Install page is displayed.
- On the Ready to Install page, you have the following choices:
- Click Back if you want to return to the previous page. Disk space is rechecked if you do this.
- Click Install Now (or type 1 at the command line) to start the installation process.
- Click Cancel to exit the installation program.
An Installation progress indicator bar is displayed.
When installation finishes, the Installation Summary page is displayed.
- Check the installation outcome on the Installation Summary page. If installation failure has occurred, review the following log file:
- /var/sadm/install/logs/Sun_ONE_Application_Server_install.log
Refer to "About Logs and Messages" for additional information.
- Click Finish (or type Finish at the command line) to complete the installation.
The installation components are now installed on your systems.
- Start the server.
You can start the Sun ONE Application Server software by using the instructions on "Starting and Stopping the Server".
When the Admin Console has been started, the initial page of the Application Server graphical interface is displayed.
Note
The installation program creates an initial domain called domain1 with a single instance called server1. Refer to "Creating Domains and Instances" for instructions on creating additional domains and instances.
- If you have not already done so, add the HADB bin directory to the PATH environment variable as described in "Setting Up the User Environment".
- If you selected the HADB components, verify that you have successfully installed the HADB software by doing the following on each host:
hadbm --help
The result of this command should be a list of all commands available using the hadbm command-line utility.
You are now ready to configure your system for high availability. Proceed to "Preparing for HADB Setup" to begin this process.
Installing the Load Balancer Plug-inThis section provides instructions for installing the load balancer plug-in component separately.
To install the load balancer plug-in component, perform these steps:
- Check the system that will be hosting the web server and load balancer plug-in to see if a previously-installed load balancer plug-in or reverse proxy plug-in is present. If it is, you will need to remove it using the unistallation program.
As root, run the following command:
pkginfo SUNWaspx
On a clean system, the following message will be displayed:
ERROR: information for "SUNWaspx" was not found.
- Verify that the correct web server is present on the machines were you are going to install the load balancer plug-in. Currently supported versions include the following:
- Log in as root and create a temporary directory for the product distribution file.
- For a download, unzip the .gz file as follows:
gunzip sun-appserver7-sol.tar.gz
- For a download, untar the unzipped file as follows:
tar -xvf sun-appserver7-sol.tar
This process may take a little time. When the files are unpacked, you will see the sun-appserver7 directory, which contains the setup file and the pkg directory.
- Navigate to the sun-appserver7 installation directory.
- Select your installation method.
Refer to "Installation Options" for guidelines on selecting the correct options to use with the setup command.
When the installation starts, the Welcome page of the installation program is displayed.
- Read the License Agreement and click Yes to agree to the terms of the license (or type Yes at the command line), then click Next.
After you accept the License Agreement, the Select Installation Directory page is displayed.
- Specify the path to your Sun ONE Application Server installation directory (default is /opt/SUNWappsrver7).
- Choose the load balancer plug-in component on the Component Selection page (or type Yes or press Enter to accept the component from the command line).
If you selected the load balancer plug-in component, the Web Server Directory page displays.
- Identify your web server.
- Click Next.
The installation program proceeds to verify that you have enough disk space based on the components you selected. The Checking Disk Space progress indicator bar is displayed.
- If you do not have enough disk space, an error message is displayed.
In this case, you need to exit the installation program, create enough space, and restart the installation. Information on space requirements is contained in "Platform Requirements".
- If you have enough disk space, the Ready to Install page is displayed.
- On the Ready to Install page, you have the following choices:
- Click Back if you want to return to the previous page. Disk space is rechecked if you do this.
- Click Install Now (or type 1 at the command line) to start the installation process.
- Click Cancel to exit the installation program.
An Installation progress indicator bar is displayed.
When installation finishes, the Installation Summary page is displayed.
- Check installation outcome on the Installation Summary page. If installation failure has occurred, review the following log file:
/var/sadm/install/logs/Sun_ONE_Application_Server_install.log
Refer to "About Logs and Messages" for additional information.
- Click Finish (or type Finish at the command line) to complete the installation.
- Edit the supplied loadbalancer.xml.example file to include references to actual application server instances. This file is located in the following location:
For Sun ONE Web Server:
webserver_instance_dir/config/loadbalancer.xml.example
For Apache Web Server:
webserver_instance_dir/conf/loadbalancer.xml.example
- After you have made your modifications, save the loadbalancer.xml.example file as loadbalancer.xml in the same directory.
Installing in Silent Mode (Non-Interactive)If you choose to install the Sun ONE Application Server Version 7, Enterprise Edition software in silent mode, the installation program runs without any user input. This is made possible when the installation program accesses a text file that provides the installation program with the configuration information it needs.
The following topics are discussed in this section:
Creating the Installation Configuration File
The installation configuration file is created when you use the savestate option with the setup command to start a 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 in this section:
Syntax for Creating the Installation Configuration File
The syntax for creating an installation configuration file is as follows:
For graphical method:
For command-line method:
Refer to "Installation Options" for more detailed information.
Example Installation Configuration File
An installation configuration file looks similar to the following:
# Wizard Statefile created: Mon Jan 27 16:25:26 PST 2003
# Wizard path: /tmp/herc/sun-appserver7/./appserv.class
# Install Wizard Statefile section for Sun ONE Application Server
#
[STATE_BEGIN Sun ONE Application Server 108a4222b3a6a8ed98832d45238c7e8bb16c67a5]
defaultInstallDirectory = /opt/SUNWappserver7
currentInstallDirectory = /opt/SUNWappserver7SELECTED_COMPONENTS = Java 2 SDK, Standard Edition 1.4.1_03#Application Server#Sun ONE Message Queue 3.0.1#Sample Applications#Load Balancing Plugin#Uninstall#Startup
USE_BUNDLED_JDK = FALSE
JDK_LOCATION = /usr/j2se
JDK_INSTALLTYPE = PREINSTALLED
AS_INSTALL_DEFAULT_CONFIG_DIR = /etc/opt/SUNWappserver7
AS_INSTALL_CONFIG_DIR = /etc/opt/SUNWappserver7
AS_INSTALL_DEFAULT_VAR_DIR = /var/opt/SUNWappserver7
AS_INSTALL_VAR_DIR = /var/opt/SUNWappserver7
DOMAINS_DIR = /var/opt/SUNWappserver7/domains
WEBSERVER_INSTALL_DEFAULT_DIR = /usr/iplanet/servers
WEBSERVER_INSTALL_DIR = /opt/iplanet/servers/https-tesla.red.iplanet.com
INST_ASADMIN_USERNAME = admin
INST_ASADMIN_PASSWORD = adminadmin
INST_ASADMIN_PORT = 4848
INST_ASWEB_PORT = 81
INSTALL_STATUS = SUCCESS
[STATE_DONE Sun ONE Application Server 108a4222b3a6a8ed98832d45238c7e8bb16c67a5]Modifying the Installation Configuration File
You can modify the installation configuration file by editing the variables and values described in Table 2-2.
Installing in Silent Mode
Note
For silent mode, you can do a partial initial installation, but any incremental (subsequent) installations must be done using an interactive method.
To install the Sun ONE Application Server software in non-interactive silent mode, perform these steps:
- With a text editor, examine the current installation configuration file and verify that it contains what you want to use for your silent installation.
- Save your config_file with any name. For example:
cp statefile my_silent_config
- Copy your installation configuration file to each machine where you plan to install the Sun ONE Application Server Version 7, Enterprise Edition software.
- Copy the Sun ONE Application Server installation files to each machine where you plan to install the Application Server software.
- If you are not in the directory already, navigate to the directory where you copied the installation files and your installation configuration file.
- As superuser, start silent installation at the command line using the following command format:
./setup -silent config_file
The installation program reads the specified config_file, checks for adequate disk space, then installs the product based on the data in config_file.
When the prompt is returned, the silent installation is complete and the installation components are now installed on your systems.
- You can start the Application Server software by using the instructions on "Starting and Stopping the Server".
When the Admin Console has been started, the initial page of the Application Server graphical interface is displayed.
You are now ready to configure your system for high availability. Proceed to "Preparing for HADB Setup" to begin this process.