Monitoring application activity – Apple WebObjects 3.5: Serving User Manual
Page 21
Serving WebObjects
22
essarily improve performance or allow the application to serve more requests at
sustained high loads. For more information, see “Increasing the Listen Queue
Depth” in this guide.
ApplicationName
Specifies the application name, which is the directory path relative to
/WebObjects
. This argument is required when you use the
-d
option to
specify the document root.
Examples
The following example starts the scripted application TimeOff on Windows
NT:
> cd
\Examples\WebScript\TimeOff.woa
> WODefaultApp.exe Examples/WebScript/TimeOff
The following example starts a compiled WebObjects example application on
Mach, assigning it the default HTTP (CGI) adaptor and specifying port and
instance numbers for that adaptor. Because an instance number is specified, if a
Monitor is running on that machine, it can display application activity and shut
down the application.
> HelloWorldCompiled -d /NextLibrary/WebServer/htdocs -a WODefaultAdaptor
-n 1 -p 3000 -q 50 Examples/ObjC/HelloWorldCompiled
Notes
The web server uses the
URLs, so you should use forward slashes as opposed to a backslashes when
specifying these arguments.
As a convenience, you might create a shell script that starts WebObjects
applications when the server machine is booted. You also might create another
shell script that you can run at the command line to start applications.
Monitoring Application Activity
There are several ways you can obtain information about the applications
running on your server. You can use the Monitor application, analyze logs kept
by the application and the adaptor, and check the application’s statistics page.
Using the Monitor to Obtain Application Information
The Monitor application can provide you with information about all of your
running WebObjects applications.