pcClusterMonitor Configuration

Note: You can ignore this section if you don't need to use a pcClusterMonitor. To find out if you need a pcClusterMonitor, you should read through "About the pcClusterMonitor" in Chapter 13 and "Determining Your Network Architecture" in Chapter 13.

Currently there are only two versions of the pcClusterMonitor. The ISAPI version and the servlet version.

Configuring the pcClusterMonitor is very similar to configuring the HTTP redirectors. For the most part, you should follow the steps outlined in the HTTP redirection installation directions (refer to "Microsoft Internet Information Services" in Chapter 12 or "J2EE Web Application Servers" in Chapter 12), making, of course appropriate substitutions of files and names.

The only other significant difference in the setup process is the configuration of the initialization parameter in the servlet, or of the configuration file in ISAPI.

In both cases, your configuration file or parameter will need to list the addresses of several servers in the cluster. It only has to be able to contact one of these servers, as it will download the addresses of the rest of the servers in the cluster from that server. Technically, you only need to set one address, but this does not ensure redundancy. The addresses should be listed in the following syntax: IP:commport,IP:commport.

ISAPI Version

The redirector file is located at dev_tools/isapi_cluster_monitor/pcClusterMonitor.dll. Its configuration file is called pcClusterMonitor.cfg in that same directory.

Your pcClusterMonitor.cfg file should contain a single line listing several servers in the cluster (e.g. 10.0.1.52:2002,10.0.1.45:2002).

Servlet Version

The jar file for the redirector servlet is located at dev_tools/isapi_cluster_monitor/pcClusterMonitor.jar.

The initialization parameter is called ClusterAddress. You should set the value of this parameter to the list of servers in the cluster monitor (e.g. 10.0.1.52:2002,10.0.1.45:2002).