Sun Cluster 3.0 5/02 Supplement

How to Configure an iPlanet Web Server (5/02)

The following change was introduced in the Sun Cluster 3.0 5/02 update release and applies to this update and all subsequent updates to Sun Cluster 3.0 software.

This procedure describes how to configure an instance of the iPlanet Web server to be highly available. Use the NetscapeTM browser to interact with this procedure.

Consider the following points before you perform this procedure.

  1. Create a directory on the local disk of all the nodes to hold the logs, error files, and PID file that iPlanet Web Server manages.

    For iPlanet to work correctly, these files must be located on each node of the cluster, not on the cluster file system.

    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/
    

    only -

    If you anticipate large error logs and PID files, 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 https-admserv, then start the iPlanet admin server.


    # cd https-admserv
    # ./start
    

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

    The URL consists of the physical hostname and port number that the 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 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 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, PidLog, and Access Log entries to reflect the directory created in Step 1 of this section.

    • Save your changes.