---

Deploying on Multiple Hosts

Creating a deployment environment sometimes involves more than one HTTP server and many WebObjects application instances running on each server. To make several hosts available to Monitor, a daemon (or, on NT, a service) called wotaskd must be running on each host. With wotaskd running the Monitor application can remotely administer a host machine. When WebObjects is installed on a particular host, wotaskd is automatically configured to run whenever that host machine is restarted.

Although there is no technical reason why you cannot have multiple copies of Monitor running, because Monitor maintains some information locally it is possible for multiple Monitors managing a common set of hosts to get out of sync. Thus, there ought to be only one copy of Monitor running at a time managing a given set of hosts.

The following diagram depicts one possible WebObjects deployment scenario:

Machine 1 acts as the web server and load balancer between all the application servers running on Machines 2, 3, and 4. Monitor should be running on the same host as the web server and the WebObjects adaptor, and is responsible for maintaining the WebObjects.conf file.

Adding a Host to Monitor