Changes for page Running Through Apache - Leopard & Snow Leopard Client - Summary
Last modified by Aaron Rosenzweig on 2012/10/18 13:08
From version 16.1
edited by David Holt
on 2008/11/20 19:28
on 2008/11/20 19:28
Change comment:
There is no comment for this version
To version 18.1
edited by David Holt
on 2008/11/20 19:00
on 2008/11/20 19:00
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,4 +1,4 @@ 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: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: 2 2 3 3 [[Development Tools-Running Through Apache]] 4 4 [[WO 5.4 Getting Started]] ... ... @@ -5,10 +5,9 @@ 5 5 6 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 7 8 -The steps I took as outlined in the wiki pages above:8 +The steps I took as outlined in the wiki: 9 9 10 -Edit /etc/apache2/httpd.conf 11 -Search for "Directory /" and comment out the Order and Deny lines: 10 +Modify apache commenting out the two lines in /directory 12 12 <Directory /> 13 13 Options FollowSymLinks 14 14 AllowOverride None ... ... @@ -23,12 +23,12 @@ 23 23 Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf 24 24 25 25 My apache.conf file contained the line to load the WebObject module 26 -Confirm that apache.conf alsoincludes:25 +Confirm that apache.conf includes: 27 27 WebObjectsConfig http:~/~/localhost:1085 10 28 28 29 -Add the "WOHost localhost"to the properties file in wotaskd(/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties)28 +Add the WOHost localhost to the properties file in wotaskd 30 30 31 -Change permissions of the two lauchdaemons to **exactly** what is written in the wiki (I think they are created by default now with WO 5.4.3, if not create the files as described in [[WO 5.4 Getting Started]])30 +Change permissions of the two lauchdaemons to **exactly** what is written in the wiki 32 32 644 system/wheel/everyone 33 33 34 34 Set your launch parameters in your application: ... ... @@ -38,8 +38,8 @@ 38 38 --WOAdaptorURL http:~/~/localhost/cgi-bin/WebObjects 39 39 --WOPort 5555 40 40 41 -Load the LaunchDaemons. Make sure the filenames 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 load the modules if you use the wiki instructionson the commandline anddon't notice the naming difference of the files.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. 42 42 43 43 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. 44 44 45 -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 before I finally got it all to work. 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.