Making Monitor and MonitorProxy Fail-safe
Because Monitor is a critical piece of any deployment, you should take measures to make sure that it does not fail. To help you achieve this aim, WebObjects provides a simple command-line tool, MonitorDaemon. This tool restarts Monitor or MonitorProxy when they fail. How you use MonitorDaemon depends on the WebObjects deployment platform. Using MonitorDaemon on Windows NT
When WebObjects is properly installed, the Services Control panel contains two services which use MonitorDaemon to keep Monitor and MonitorProxy running.: "Apple WebObjects Monitor" and "Apple WebObjects MonitorProxy." Use these services to keep Monitor and MonitorProxy up and running. Using MonitorDaemon on Mac OS X Server
On these platforms you can enter the MonitorDaemon tool on a shell command line (such as provided by Terminal.app), start it from a shell script, or configure it to launch Monitor or MonitorProxy automatically at boot time.
MonitorDaemon /System/Library/WebObjects/Applications/Monitor.woa/MonitorTo have Monitor launched at system boot time, you must add a startup script to /etc/startup. The scripts in /etc/startup follow a naming convention whereby the first four characters of the script filename are numbers. These numbers signify the order in which the system runs the scripts in /etc/startup. You should start Monitor and MonitorProxy near the end of the boot cycle.
You could add the following script, named 3000_Monitor, to /etc/startup to start MonitorDaemon when the system boots and have it keep Monitor running:
#!/bin/sh # # Start Monitor using MonitorDaemon for WebObjects Deployment # . /etc/rc.common # the following is one line: /System/Library/WebObjects/Applications/Monitor.woa/MonitorDaemon /System/Library/WebObjects/Applications/Monitor.woa/Monitor &