Apple WebObjects 3.5: Serving - Manual (Page 16)

Administrative Tasks
17
which means that if you install scripted components under the document
root, you are exposing source code to outside users.
Instead, it is recommended that you install most of the application in
NeXT_ROOT
/NextLibrary/WOApps and install only the web server resources
under the document root. It is also recommended that you install the
application directly in the
/WebObjects directory rather than in a
subdirectory. If you install in a subdirectory, your application can still run
but cannot find image files unless you provide the application path on the
command line. For more information, see “Starting Up Applications From
the Command Line” in this guide.
Starting WebObjects Applications
As described previously, there are two ways to start an application: autostart
and manual. Autostarting applications occurs when the user types the
application’s URL in a web browser; the WebObjects adaptor looks for a
running instance of that application and starts one if it cannot find one.
Autostarting is not recommended for deployment, It’s convenient but when
you allow autostarting, it becomes more difficult to monitor the applications
progress. Instead, you can use the Monitor application’s interface to start
applications. (The application will sit idle until a user tries to access it.)
Another alternative is to start applications from the command line. You
might start from the command line when you need to see the debugging
messages written to standard output. This section describes how to
manually start an application using the Monitor or the command line.
Starting Applications Using Monitor
To start up a WebObjects application in the Monitor, do the following:
1. Locate the application in the list in the left frame of the browser
window.
2. Click the inspector button to the left of the application name.