Apple WebObjects 3.5: Serving - Manual (Page 8)

Setting Up the Monitor Application
9
Which Copy of Monitor Should I Use?
If you have multiple machines running WebObjects, you can administer
them all from a single instance of Monitor on a single machine. It’s
recommended that you use the copy of Monitor that’s installed on the same
machine as your HTTP server and WebObjects adaptor. This is because
the main purpose of the Monitor is to maintain the public configuration file
(
WebObjects.conf ), which the WebObjects adaptor uses to find running
instances of WebObjects applications. The best way to achieve sharing of
the
WebObjects.conf file is to have your HTTP server and Monitor run on the
same machine. The alternative—having Monitor on a separate machine—
would require that the two machines share a file system through network
access.
Monitor can communicate with WebObjects applications running on
remote hosts; however to launch applications on remote hosts it uses a
lightweight daemon named
MonitorProxy . For example, the following figure
shows a WebObjects site spread across four machines. One machine
contains the HTTP server, and the other three machines contain
WebObjects applications. You would run the Monitor application on the
machine containing the HTTP server. That Monitor application would use
the
MonitorProxy daemons on the other three machines to launch applications.
All other communication goes directly between Monitor and the
WebObjects application.