Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Service for Oracle iPlanet Web Server Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Installing and Configuring Oracle iPlanet Web Server Software

This section describes the steps to perform the following tasks:

- Install the Oracle iPlanet Web Server software.

- Enable the Oracle iPlanet Web Server software to run as HA for Oracle iPlanet Web Server.

Note - HA for Oracle iPlanet 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 Oracle Solaris Cluster Data Services Developer’s Guide to put the server under Oracle Solaris Cluster control.

## How to Install Oracle iPlanet Web Server

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 HA for Oracle iPlanet 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, assume a role that provides `solaris.cluster.admin` RBAC authorization.
2. Start the installation.
3. When prompted, enter the location where the Oracle iPlanet 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 Oracle iPlanet Web Server depends and the appropriate DNS domain name.

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

   Note - For HA for Oracle iPlanet 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 Oracle iPlanet 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 Oracle iPlanet Web Server. Otherwise, you can specify a different port number when you configure the Oracle iPlanet 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.

## How to Configure Oracle iPlanet Web Server

This procedure describes how to configure an instance of the Oracle iPlanet Web Server to be highly available. Use a 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.

- HA for Oracle iPlanet Web Server supports HA for Oracle iPlanet Web Proxy Server. For Oracle iPlanet Web Proxy Server installation and configuration information, see your Oracle iPlanet Web Proxy Server installation documentation.

- Your configuration files can reside on either a local file system or on the cluster file system.

- Any certificates that are installed for SSL–based 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.

  1. Run the admin server on node `n1`.

  2. From your Web browser, connect to the admin server as `http://n1.`domain:port. For example, `http://n1.example.com:8888`, or whatever you specified as the admin server port. The port is typically `8888`.

  3. Install the certificate.

  4. Stop the admin server on node `n1` and run the admin server from node `n2`.

  5. From the Web browser, connect to the new admin server as `http://n2``.`domain`:`port, for example, `http://n2.example.com:8888`.

  6. Repeat these steps for nodes `n3` and `n4`.

  After you have considered the preceding points, complete the following steps.

1. If you will configure Oracle iPlanet 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 Oracle iPlanet 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 Oracle iPlanet 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 browser.
3. On one of the cluster nodes, go to the directory `admin-server`, then start the Oracle iPlanet admin server.

       # cd admin-server
       # ./startserv

4. Enter the URL of the Oracle iPlanet admin server in the Netscape browser.

   The URL consists of the logical hostname and port number that the Oracle iPlanet installation script established in Step 4 of the server installation procedure, for example, `n1.example.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 Oracle iPlanet 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 the `root` role.

   - 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 Error Log and Access Log entries to reflect the directory created in Step 1 of this procedure.

   - Save your changes.

6. Store the key password.

   Choose one of the following methods.

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

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

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

Copyright © 2009, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |