|
||
|
|
Chapter 6 Managing Server Clusters
This chapter describes the concept of clustering Netscape Enterprise Servers and explains how you can use them to share configurations among servers.
This chapter includes the following sections:
- About Clusters
![]()
- Guidelines for Using Server Clusters
![]()
- Setting Up a Cluster
![]()
- Adding a Server to a Cluster
![]()
- Modifying Server Information
![]()
- Removing Servers from a Cluster
![]()
- Controlling Server Clusters
![]()
- Adding Variables
![]()
A cluster is a group of Enterprise 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 Enterprise Servers installed in their respective clusters.
Here are some of the tasks you can accomplish by organizing your servers into clusters:
- Create a central place for administering all Enterprise Servers
![]()
- Share one or more configuration files between servers
![]()
- Start and stop all servers from one "master" Administration Server
![]()
- View the access and error logs for the servers you selected
![]()
By clustering your Enterprise Servers, you're able to specify a master Administration Server for administering all of your clusters.
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. The administration server for each cluster must be given the same administration user name and password that the master Administration Server will have.
Before you can create a cluster, all of the servers you want to include in the cluster must be installed. For example, if you want three clusters of five Enterprise Servers per cluster, you would need to:
- Install all of the servers on the computers where they'll run using the same administration user name and password as the master Administration Server.
![]()
- Configure one of the Enterprise Servers in each cluster as the Administration Server.
![]()
- 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:
- Install all of the servers you want to include in a particular cluster prior to creating any clusters.
![]()
- Make sure all servers in a cluster are version 6.1 Enterprise Servers.
![]()
- Make sure all cluster-specific Administration Servers have the same userid and password as the master administration server. You can use distributed administration to set up multiple administrators on each Administration Server.
![]()
- Install servers on any computer in a network, as long as all computers in the cluster are Windows NT/Windows 2000 or UNIX.
![]()
- You can designate any cluster-specific Administration Server as the master administration server.
![]()
- Make sure the master Administration Server has access to each cluster-specific Administration Server. The master Administration Server retrieves information about all installed Enterprise Servers.
![]()
- Make sure all Administration Servers are Enterprise Server version 6.1 and use the same protocol, HTTP or HTTPS. Only Enterprise Server 6.1 servers are supported for addition to clusters.
![]()
- If you change the protocol of one Administration Server in a cluster, you must change the protocols for all Administration Servers. Then use the Modify Server interface to modify the individual servers in the cluster.
![]()
To set up a Enterprise Server cluster, perform the following steps:
- Install the Enterprise 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.
- Install the server that will contain the master Administration Server, making sure the username and password matches the one set in Step 1.
![]()
- Add a server to the cluster list.
![]()
- 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.
![]()
After changing the configuration for a remote server, restart the remote server.
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 individual servers later.
To add a remote server to a cluster, perform the following steps:
- Make sure the master Administration Server is tuned on.
![]()
- Access the Administration Server and choose the Cluster Mgmt tab.
![]()
- Click the Add Server link.
![]()
- Choose the protocol that the remote Administration Server uses.
![]()
- Enter the fully qualified domain name as it appears in the
magnus.conffile of the remote server in the Admin Server Hostname field.![]()
- For example:
mktg.example.com
- Enter the port number for the remote Administration Server.
![]()
- Click OK.
![]()
- Your master Administration Server now attempts to contact the remote server. This can take a few minutes. You will receive a message confirming the server is added to the cluster.
- Click OK.
![]()
Use the Modify Server option only to update slave administration port information, after it has been changed on the slave server. If you change the port number of a remote Administration Server in your cluster, you also need to modify the information about that Administration Server stored in the cluster. Any other changes to the slave administration server require you to delete the server, and then add it back into the cluster after the changes have been made.
The remote administration servers will not be affected by modification to the master cluster database, unless their files have been transferred through Cluster Control.
To modify information about a server in a cluster, perform the following steps:
- Go to the master Administration Server and choose the Cluster Mgmt tab.
![]()
- Click the Modify Server link.
![]()
- All servers appear listed by their unique server identifier.
- Select the server or server to modify by:
![]()
- Click Reset to undo all selections.
- Enter the new port number.
![]()
- Click OK.
![]()
Removing Servers from a Cluster
To remove a server from the cluster, perform the following steps:
- Go to the master Administration Server and choose the Cluster Mgmt tab.
![]()
- Click the Remove Server link.
![]()
- Select the remote server or servers to modify by:
![]()
- Click Reset Selection to undo all selections.
- Click OK.
![]()
A message appears confirming that the server is removed from the cluster. You can no longer access the removed server through the cluster; you can only access it now through it's own Administration Server.
Enterprise Server 6.1 allows you to control the remote servers in your cluster by:
- Starting and stopping them
![]()
- Viewing their access and error logs
![]()
- Transferring configuration files to them.
![]()
To control servers within your cluster, perform the following steps:
- Go to the Server Manager for the master Administration Server, and choose the Cluster Mgmt tab.
![]()
- Click the Cluster Control link.
![]()
- Select the server or servers to control by:
![]()
- Click Reset Selection to undo all selections.
- Select Start or Stop remote servers from the drop down menu.
![]()
- Select View Access or View Error log records from the drop down menu and enter the number of lines you wish to view.
![]()
- To transfer configuration files:
![]()
Variables are used when servers in a cluster need to be configured with different values. These values might be macros to define slaves using different port numbers, or plug-ins to define different
shlibpaths.Adding variables affects only the master cluster database. The remote administration servers will not be affected unless their files have been transferred through Cluster Control. When variables are defined, the Administration Server can no longer run independently.
To add variables for a remote server within your cluster, perform the following steps:
- From the master Administration Server, and choose the Cluster Mgmt tab.
![]()
- Click the Add Variables link.
![]()
- Check the specific server you wish to add variables for.
![]()
- In the Name field enter the type of variable you are adding.
![]()
- For example: `Port'.
- In the Value field enter the value you are adding.
![]()
- For example: if `Port' is entered in the name field, the value would be the port number.
- Click OK.
![]()
- A message appears confirming that the server variable has been added.
- Click OK.
![]()
The variable must also be added to the server's configuration file you are transferring to the slave. For example:
SERVERPORT $Portif port was the variable added.You can set variables with different values for each slave in the configuration file.
Once added, variables can also be edited and deleted using the drop-down Option list in the Add Variables page.
© 2001 Sun Microsystems, Inc. Portions copyright 1999, 2002 Netscape Communications Corporation. All rights reserved.
Last Updated August 02, 2002