Apple WebObjects 3.5: Serving - Manual (Page 15)

Serving WebObjects
16
Load Balancing
Increasing the Listen Queue Depth
Installing and Configuring NSAPI Adaptors
Installing and Configuring the ISAPI Adaptor
Starting Up Multiple Monitor Instances
Installing Applications
You can use the developer application Project Builder to deploy WebObjects
applications. When an application is ready to be deployed, do the following in
Project Builder:
1. Click the inspector button to open the Build Attributes Inspector. In the
Install in field, type $(NEXT_ROOT)/NextLibrary/WOApps .
If you’re installing a framework, type $(NEXT_ROOT)/NextLibrary/Frameworks
2. If your project contains web server resources, go to the Makefile.preamble file
under Supporting Files. Uncomment the following macro:
INSTALLDIR_WEBSERVER
3. In the Project Build panel, click the checkmark button to bring up the Build
Options panel.
4. Choose install as the build target, and close the Build Options panel.
5. Click the Build button to start the build and installation process.
Assuming that your application is named MyApp.woa , this procedure installs these
directories:
NeXT_ROOT /NextLibrary/WOApps/MyApp.woa
MyApp[.exe]
Resources/
WebServerResources/
/WebObjects/MyApp.woa
WebServerResources/
As discussed previously in the section “Adaptor Modes,” when the client tries
to contact an application, the adaptor first looks for a public configuration file
that names the application, then for a private configuration file that names the
application, and then for an executable in
/WebObjects and
NeXT_ROOT /NextLibrary/WOApps . Thus, you can install the entire directory under
/WebObjects , but doing so presents a security problem if you have
scripted components. Any client can access any file under the document root,