Complete Contents
About This Guide
Chapter 1 Introduction to iPlanet Web Server
Chapter 2 Administrating iPlanet Web Servers
Chapter 3 Setting Administration Preferences
Chapter 4 Managing Users and Groups
Chapter 5 Working with Server Security
Chapter 6 Managing Server Clusters
Chapter 7 Configuring Server Preferences
Chapter 8 Understanding Log Files
Chapter 9 Using SNMP to Monitor Servers
Chapter 10 Configuring the Server for Performance
Chapter 11 Extending Your Server with Programs
Chapter 12 Working with Configuration Styles
Chapter 13 Managing Server Content
Chapter 14 Controlling Access to Your Server
Chapter 15 Configuring Web Publishing
Chapter 16 Using Search
Appendix A HyperText Transfer Protocol
Appendix B ACL File Syntax
Appendix C Internationalized iPlanet Web Server
Appendix D Server Extensions for Microsoft FrontPage
Appendix E iPlanet Web Server User Interface
Glossary
Index
Previous Next Contents Index Bookshelf


Chapter 6 Managing Server Clusters

This chapter describes the concept of clustering iPlanet Web server s and explains how you can use them to share configurations among servers.

This chapter includes the following sections:


About Clusters
A cluster ia a group of iPlanet Web Servers that can be administered from a single Administration Server. Each cluster must include one server designated as the administration server. If you have more than one cluster, you can administer all clusters from a single "master" Administration Server. The master administration server retrieves the information about all the clusters and provides the interface for managing the iPlanet Web Servers installed in their respective clusters.

Here's some of the tasks you can accomplish by organizing your servers into clusters:

By clustering your iPlanet Web Servers, you're able to specify a master Administration Server for administering all of your clusters.

Note. The individual servers can be installed on any computer in a network, but the Administration Server that you designate as the "master" contains information about all clustered servers, and must have access to each cluster's individual Administration Server.


Preliminary Guidelines for Using Server Clusters
When you configure a cluster, the master Administration Server containing the information about all clusters communicates with each individual cluster's Administration Server. Because of this, each cluster-specific administration server must have an administrative user and password that the master Administration Server can use to authenticate itself. When you log in to this master administration server and you supply a username and password, that information is sent to all remote Administration Server.

Before you can create a cluster, you must first install all of the servers you want to include in the cluster. For example, if you want three clusters of five iPlanet Web Servers per cluster, you would first need to install all of the servers on the computers where they'll run, and then you would configure one of the iPlanet Web Servers in each cluster as the Administration Server, and then you'll need to configure one single cluster's administration server as the master Administration Server for all clusters. It doesn't matter which server you choose as the master administration server.

The following list provides some guidelines for configuring groups of servers into clusters:

You can perform the following tasks for working with iPlanet Web Server clusters:


Setting up a Cluster
To set up a iPlanet Web Server cluster, perform the following steps:

  1. Install the iPlanet Web Servers on the computers you want to include in the cluster. Make sure the Administration Server for the cluster has a username and password that the master Administration Server can use for authentication. You can do this either by using the default username and password or by setting up distributed administration.
  2. Install the server that will contain the master Administration Server, making sure the username and password matches the one set in Step 1.
  3. Add a server to the cluster list.
  4. You can administer a remote server by accessing its Server Manager forms from the cluster form or by copying a configuration file from one server in the cluster to another.
Note. After changing the configuration for a remote server, restart the remote server.

For more information about how to use the Server Manager forms, see Server Manager.


Adding a Server to the Server List
When you add a server to a cluster, you specify its Administration Server and port number. If that Administration Server contains information about more than one server, all of its servers are added to the cluster. (You can remove the individual servers later.)

Note. If a remote Administration Server contains information about a cluster, the servers in the remote cluster are not added. The master Administration Server adds only those servers that are physically installed on the remote computer.

To add a remote server to the list, perform the following steps:

  1. Access the Administration Server and choose the Cluster Mgmt tab.
  2. Click the Add Server link.
  3. Choose the protocol that the remote Administration Server uses. This is the protocol used when contacting the remote Administration Server. Choose http for normal Administration Server. Choose https if the remote Administration Server is secure.
  4. Type the hostname for the remote Administration Server. If your DNS can resolve host names, you don't need to type the fully qualified domain name; otherwise type the full host and domain name. For example, type www.mozilla.com.
  5. Type the port number that the remote Administration Server uses.
  6. Click OK.
For more information, see The Add Remote Servers to Cluster Database Page.


Modifying Cluster Information
If you change an Administration Server's host name, port number, or protocol used (HTTP or HTTPS), you also need to modify the information about that Administration Server that is stored in the cluster.

To modify information about a server in a cluster, perform the following steps:

  1. Go to the master Administration Server and choose the Cluster Mgmt tab.
  2. Click the Modify Server link.
  3. Check the servers you want to modify:
    1. You can change the information for all servers in the cluster by clicking Select All.
    2. Click Reset Selection to unselect any servers you have chosen in the form.

  4. Choose the administration server protocol that the remote Administration Server server uses, if it has changed.
  5. If applicable, type the new hostname for the remote Administration Server.
  6. If applicable, type the new port number that the remote Administration Server uses.
  7. Click OK.
For more information, see The Modify Server Settings in Cluster Database Page.


Removing Servers from a Cluster
To remove a server from the cluster, perform the following steps:

  1. Go to the master Administration Server and choose the Cluster Mgmt tab.
  2. Click the Remove Server link.
  3. Check the server you want to remove. You can remove all servers of that type by clicking Select All. Click Reset Selection to unselect all servers.
  4. Click OK.
The form displays a status saying the servers are removed from the cluster database and are no longer available for cluster control. You can still access the removed servers using their Administration Server; you just can't access them from the cluster.

For more information, see The Remove Servers from Cluster Database Page.


Managing Server Clusters
To manage a cluster of servers, perform the following steps:

  1. Go to the Server Manager forms for the master Administration Server, and then choose the Cluster Mgmt tab.
  2. Click the Cluster Control link.
  3. Check the server or servers you want to change.
  4. Configure the servers using the form elements specific to the type of server you selected. Most Netscape/iPlanet servers let you start, stop, or restart the server by clicking the corresponding buttons on the form.
For more information, see The Cluster Control Page.

 

© Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.