Table of Contents Previous Section

Starting Up Monitor

 To start up Monitor on Windows NT, choose Monitor from the WebObjects program group in the Start menu.

To start up Monitor on any other system, do the following:

  1. Open a command shell window.

  2. Enter these commands: 
    	> cd /NextLibrary/WOApps/Monitor.woa
	> Monitor

    The Monitor application launches in your default web browser and displays this screen:

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.

Starting Up MonitorProxy

As mentioned in the previous section, if you have a multiple machine configuration, you need to run Monitor on one machine and run MonitorProxy daemons on the other machines. You can start up MonitorProxy daemons the same way you start up Monitor:

To start up MonitorProxy on Windows NT, do the following:

  1. Navigate to the directory NeXT_ROOT/NextLibrary/WOApps/Monitor.woa in the Explorer.

  2. Double-click MonitorProxy.exe.
To start up MonitorProxy on any other system, do the following:

  1. Open a command shell window.

  2. Enter these commands: 
    	> cd $NEXT_ROOT/NextLibrary/WOApps/Monitor.woa
	> MonitorProxy
You probably want to set up your system so that MonitorProxy starts up at system boot time.

Note: If you're running Monitor on a Solaris or HP-UX machine, you must start up MonitorProxy on that machine as well. As you'll learn later, Monitor requires the local MonitorProxy to start up applications on Solaris and HP-UX.

Table of Contents Next Section