---

Configuration Files

Web server adaptors obtain configuration information from wotaskd via HTTP requests. Web server adaptors default to wotaskd on localhost , or, when wotaskd cannot be found, the adaptor gets its configuration information from   NEXT_ROOT /Local/Library/WebObjects/Configuration/WebObjects.xml ( NEXT_ROOT is defined at system installation time on Windows NT systems; on Mac OS X Server and similar systems, it is always /System .) This file tells the adaptor what applications are (or should be) running and allows the adaptor to balance transactions among different instances of the same application. This configuration file isn't present on your system by default; if you need it, you'll need to create this file by hand following the format outlined in Web Server Adaptor Configuration File Format.

In general, you want one configuration file per site. That means if you have multiple machines running WebObjects, you should access all WebObjects applications through a single machine that is running the HTTP server and that contains the configuration file.

If you have multiple HTTP servers running on a single machine, they all share the configuration file. If you want each server to have its own configuration file, you can install one WebObjects.xml file in each server's configuration directory if you a using an API adaptor, or in each server's cgi-bin or scripts directory if you are using the CGI adaptor.

The Monitor application also maintains a configuration file for the purposes of crash recovery; in the event that Monitor fails for any reason, when restarted it reads the file   NEXT_ROOT /Local/Library/WebObjects/Configuration/SiteConfig.conf in order to restore its state.