Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Sun Java System Web Server Guide |
1. Installing and Configuring Oracle Solaris Cluster HA for Sun Java System Web Server
Planning the Installation and Configuration
Installing the HA for Sun Java System Web Server Packages
How to Install the HA for Sun Java System Web Server Packages
Registering and Configuring Oracle Solaris Cluster HA for Sun Java System Web Server
Setting Oracle Solaris Cluster HA for Sun Java System Web Server Extension Properties
Setting IP Addresses and Port Numbers for the Sun Java System Web Server Application
How to Register and Configure HA for Sun Java System Web Server in a Scalable Configuration
How to Configure SUNW.HAStoragePlus Resource Type
Tuning the Oracle Solaris Cluster HA for Sun Java System Web Server Fault Monitor
Operations by the Fault Monitor During a Probe
Upgrading the HA for Sun Java System Web Server Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
This section describes the steps to perform the following tasks:
Install the Sun Java System Web Server.
Enable the Sun Java System Web Server to run as Oracle Solaris Cluster HA for Sun Java System Web Server.
Note - The Sun Java System Web Server can be configured to run in a whole root or a sparse root non-global zone, if required.
Note - Oracle Solaris Cluster HA for Web Proxy Server is not supported in a Scalable configuration.
Note - You must follow certain conventions when you configure URL mappings for the Web server. For example, to preserve availability when setting the CGI directory, you must locate the mapped directories on the cluster file system. In this example, you map your CGI directory to /global/pathname/cgi-bin.
In situations where the CGI programs access “back-end” servers, such as an RDBMS, ensure that the Oracle Solaris Cluster software also controls the “back-end” server. If the server is an RDBMS that the Oracle Solaris Cluster software supports, use one of the highly available RDBMS packages. Alternatively, you can use the APIs documented in the Solaris Cluster Data Services Developer's Guide for Solaris OS to put the server under Oracle Solaris Cluster control.
To perform this procedure, you need the following information about your configuration.
The server root directory (the path to the application binaries). You can install the binaries on the local disks or on the cluster file system. For a discussion of the advantages and disadvantages of each location, see Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide.
The logical hostname (for failover services) or shared address (for scalable services) that clients use to access the data service. You must configure these addresses, and they must be online.
Note - If you run Oracle Solaris Cluster HA for Sun Java System Web Server and another HTTP server and they use the same network resources, configure them to listen on different ports. Otherwise, a port conflict might occur between the two servers.
If you are installing the Sun Java System Web Server on Solaris 8, execute the setup command for Sun Java System Web Server from the install directory on the CD.
If you are installing the Sun Java System Web Server packaged with Solaris 9, follow the instructions on the installation CD.
Note - If you are installing the Sun Java System Web Server packaged with Solaris 9, do not enable the auto start of the web server at system restart.
You can specify a location on the cluster file system or on local disks for the location of the install. If you choose to install on local disks, install the web server on all the cluster nodes that are potential primaries of the network resource (logical hostname or shared address) that the next step specifies.
A full logical hostname is of the format network-resource.domainname, such as schost-1.sun.com.
Note - For Oracle Solaris Cluster HA for Sun Java System Web Server to fail over correctly, you must use either the logical hostname or shared address resource name (rather than the physical hostname) here and everywhere else that you are asked.
Note the port number that the Sun Java System install script selects for the administration server. You might want to use this default value later when you use the administration server to configure an instance of the Sun Java System Web Server. Otherwise, you can specify a different port number when you configure the Sun Java System server instance.
Follow the guidelines for your system.
When a message displays that the admin server will be started, your installation is ready for configuration.
This procedure describes how to configure an instance of the Sun Java System Web server to be highly available. Use the Netscape browser to interact with this procedure.
Consider the following points before you perform this procedure.
Before you start, ensure that you have installed the browser on a machine that can access the network on which the cluster resides. You can install the browser on a cluster node or on the administrative workstation for the cluster.
Oracle Solaris Cluster HA for Sun Java System Web Server now supports Sun Java System Proxy Server. For Sun Java System Proxy Server installation and configuration information, see Chapter 1, Installing Sun Java System Web Proxy Server, in Sun Java System Web Proxy Server 4.0.13 Installation and Migration Guide.
Your configuration files can reside on either a local file system or on the cluster file system.
Any certificates that are installed for the secure instances must be installed from all cluster nodes. This installation involves running the admin console on each node. Thus, if a cluster has nodes n1, n2, n3, and n4, the installation steps are as follows.
Run the admin server on node n1.
From your Web browser, connect to the admin server as http://n1.domain:port—for example, http://n1.eng.sun.com:8888—or whatever you specified as the admin server port. The port is typically 8888.
Install the certificate.
Stop the admin server on node n1 and run the admin server from node n2.
From the Web browser, connect to the new admin server as http://n2.domain:port, for example, http://n2.eng.sun.com:8888.
Repeat these steps for nodes n3 and n4.
After you have considered the preceding points, complete the following steps.
For the scalable configuration to work correctly, these files must be located on each node of the cluster, not on the cluster file system. Use shared storage only if you will configure Sun Java System Web Server as a failover data service.
Choose a location on the local disk that is the same for all the nodes in the cluster. Use the mkdir -p command to create the directory. Make nobody the owner of this directory.
The following example shows how to complete this step.
phys-schost-1# mkdir -p /var/pathname/http-instance/logs/
Note - If you anticipate large error logs, do not put them in a directory under /var because they will overwhelm this directory. Rather, create a directory in a partition with adequate space to handle large files.
# cd admin-server # ./startserv
The URL consists of the logical hostname and port number that the Sun Java System installation script established in Step 4 of the server installation procedure, for example, n1.eng.sun.com:8888. When you perform Step 2 of this procedure, the ./start command displays the admin URL.
When prompted, use the user ID and password you specified in Step 6 of the server installation procedure to log in to the Sun Java System administration server interface.
Verify that the server name is correct.
Verify that the server user is set as superuser.
Change the bind address field to one of the following addresses.
A logical hostname or shared address if you use DNS as your name service
The IP address associated with the logical hostname or shared address if you use NIS as your name service
Update the ErrorLog and Access Log entries to reflect the directory created in Step 1 of this section.
Save your changes.
Note - Because this file contains the NSS database password, protect the file with the appropriate permissions.
<pkcs11> <enabled>true</enabled> <token> <name>internal</name> <pin>admin123</pin> </token> </pkcs11>