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

Hide last authors
David Holt 20.1 1 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:
David Avendasora 14.1 2
David Holt 16.1 3 [[Development Tools-Running Through Apache]]
David Avendasora 14.1 4 [[WO 5.4 Getting Started]]
5
6 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.
7
David Holt 18.1 8 The steps I took as outlined in the wiki:
David Avendasora 14.1 9
David Holt 18.1 10 Modify apache commenting out the two lines in /directory
David Avendasora 14.1 11 <Directory />
David Holt 16.1 12 Options FollowSymLinks
13 AllowOverride None
14 #Order deny,allow
15 #Deny from all
David Avendasora 14.1 16 </Directory>
17
David Holt 16.1 18 Then add
David Avendasora 14.1 19 ServerName localhost
20
21 Add a line that points to the WebObjects apache config file
22 Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
23
David Holt 16.1 24 My apache.conf file contained the line to load the WebObject module
David Holt 18.1 25 Confirm that apache.conf includes:
David Holt 16.1 26 WebObjectsConfig http:~/~/localhost:1085 10
David Avendasora 14.1 27
David Holt 18.1 28 Add the WOHost localhost to the properties file in wotaskd
David Avendasora 14.1 29
David Holt 18.1 30 Change permissions of the two lauchdaemons to **exactly** what is written in the wiki
David Holt 16.1 31 644 system/wheel/everyone
David Avendasora 14.1 32
David Holt 16.1 33 Set your launch parameters in your application:
David Avendasora 14.1 34
David Holt 16.1 35 --WODirectConnectEnabled false
36 --WOHost localhost
37 --WOAdaptorURL http:~/~/localhost/cgi-bin/WebObjects
38 --WOPort 5555
David Avendasora 14.1 39
David Holt 18.1 40 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.
David Avendasora 14.1 41
42 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.
43
David Holt 18.1 44 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.