test

Sun Cluster Data Service for Sun Java System Web Server Guide for Solaris OS

Installing and Configuring a Sun Java System Web Server

This section describes the steps to perform the following tasks:

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 –

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 Sun Cluster software also controls the “back-end” server. If the server is an RDBMS that the Sun Cluster software supports, use one of the highly available RDBMS packages. Alternatively, you can use the APIs documented in the Sun Cluster Data Services Developer's Guide for Solaris OS to put the server under Sun Cluster control.

ProcedureHow to Install a Sun Java System Web Server

To perform this procedure, you need the following information about your configuration.

Note –

If you run Sun 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.

  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.admin RBAC authorization.

  2. Start the installation.

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

  3. When prompted, enter the location where the Sun Java System Web Server binaries will be installed.

    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.

  4. When prompted for a machine name, enter the logical hostname on which the Sun Java System Web Server depends and the appropriate DNS domain name.

    A full logical hostname is of the format network-resource.domainname, such as schost-1.sun.com.

    Note –

    For Sun 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.

  5. Select Run Admin Server as Root when 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.

  6. Type a Server Administrator ID and a chosen password when you are asked.

    Follow the guidelines for your system.

    When a message displays that the admin server will be started, your installation is ready for configuration.

ProcedureHow to Configure a Sun Java System Web Server

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.

  1. If you will configure Sun Java System Web Server as a scalable data service, create a directory on the local disk of all the nodes to hold the logs and error files that Sun Java System Web Server manages.

    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.

  2. From the administrative workstation or a cluster node, start the Netscape browser.

  3. On one of the cluster nodes, go to the directory admin-server, then start the Sun Java System admin server.


    # cd admin-server
# ./startserv

  4. Enter the URL of the Sun Java System admin server in the Netscape browser.

    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.

  5. Using the administration server where possible and manual changes otherwise, complete the following:

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

  6. Create a file that contains the secure key password you need to start this instance, and place this file under the server root directory. Name this file keypass.

    Note –

    Because this file contains the NSS database password, protect the file with the appropriate permissions.

  7. If you do not want to save the password in the keypass file, add the following to the server.xml file located in the server root directory.

    <pkcs11>
		<enabled>true</enabled>
			<token>
				<name>internal</name>
				<pin>admin123</pin>
			</token>
</pkcs11>