Skip to Content

Running Through Apache - Leopard Client 10.5.5 - Summary

Version 20.1 by David Holt on 2008/11/20 19:09

This needs to be in one page - especially for beginners. I summarized my steps to run applications with Apache on a brand new Leopard install on the mailing list and it was suggested that it get put on the wiki. Please refer to the following pages if you need clarification:

Development Tools-Running Through Apache
4 Getting Started

You don't need to set your host in JavaMonitor. I thought you did too, but it wasn't the case. You should be able to just run your application from Eclipse and it will "magically" use Apache when it is starting up.

The steps I took as outlined in the wiki:

Modify apache commenting out the two lines in /directory
<Directory />
    Options FollowSymLinks
    AllowOverride None
    #Order deny,allow
    #Deny from all
</Directory>

Then add
ServerName localhost

Add a line that points to the WebObjects apache config file
Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf

My apache.conf file contained the line to load the WebObject module
Confirm that apache.conf includes:
WebObjectsConfig http://localhost:1085 10

Add the WOHost localhost to the properties file in wotaskd

Change permissions of the two lauchdaemons to exactly what is written in the wiki
644 system/wheel/everyone

Set your launch parameters in your application:

WODirectConnectEnabled false
WOHost localhost
WOAdaptorURL http://localhost/cgi-bin/WebObjects
WOPort 5555

Load the LaunchDaemons. Make sure the names of the plists are the same as the module you're loading. I know this seems obvious, but it appears that the filenames have changed over time from "com.apple.webobjects.womonitor.plist" to "com.apple.womonitor.plist". The wiki calls for the loading of a module named "com.apple.webobjects.womonitor.plist" (notice the extra webobjects). You may not have loaded the modules if you used the wiki instructions and didn't notice the naming difference of the files.

If the LaunchDaemons are already loaded and you've made no changes, you should be able to start your application directly. If you've made changes and the LaunchDaemons are already loaded, you'll have to restart your machine to kick off launchd.

If that doesn't work, go back and double check every one of the settings. You'll probably find one of them has a typo or something. I am sure I did it three or four times last night before I finally got it all to work.