Skip to Content
Last modified by Aaron Rosenzweig on 2012/10/18 13:08
From version 17.1
edited by David Holt
on 2008/11/20 19:28
Change comment: There is no comment for this version
To version 30.1
edited by Ramsey Gurley
on 2009/10/24 15:03
Change comment: Apache development

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dholt
1 +XWiki.ramsey
Content
... ... @@ -7,8 +7,9 @@
7 7  
8 8  The steps I took as outlined in the wiki pages above:
9 9  
10 -Edit /etc/apache2/httpd.conf
10 +~1. Edit /etc/apache2/httpd.conf
11 11  Search for "Directory /" and comment out the Order and Deny lines:
12 +
12 12  <Directory />
13 13   Options FollowSymLinks
14 14   AllowOverride None
... ... @@ -16,22 +16,22 @@
16 16   #Deny from all
17 17  </Directory>
18 18  
19 -Then add
20 +Then search for "ServerName" and add
20 20  ServerName localhost
21 21  
22 22  Add a line that points to the WebObjects apache config file
23 23  Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
24 24  
25 -My apache.conf file contained the line to load the WebObject module
26 +2. My apache.conf (/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf) file contained the line to load the WebObject module
26 26  Confirm that apache.conf also 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)
30 +3. Add the launchd plist files necessary to start monitor and wotaskd during system startup to your /System/Library/LaunchDaemons/ directory. If you are using WO 5.4.x you can probably find the plists at /Developer/Examples/JavaWebObjects/Deployment/launchd/ If you cannot find them there, you can find instructions to produce them here: [[WO 5.4 Getting Started]] If you do not specify WOHost in your plist, you will need to add the "WOHost=localhost" to the properties file in wotaskd (/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties)
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]])
32 +4. Change permissions of the launch daemon plists for wotaskd and monitor to **exactly** what is written in the wiki
32 32  644 system/wheel/everyone
33 33  
34 -Set your launch parameters in your application:
35 +5. Set your launch parameters in your application:
35 35  
36 36  --WODirectConnectEnabled false
37 37  --WOHost localhost
... ... @@ -38,8 +38,11 @@
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 instructions on the command line and don't notice the naming difference of the files.
42 +6. Update mod//WO
43 +You will need to replace your mod//WebObjects.so located at /System/Library/WebObjects/Adaptors/Apache2.2/mod//WebObjects.so with the appropriate version of [[mod//WebObjects//>>http://webobjects.mdimension.com/wonder/mod_WebObjects/Apache2.2/macosx/]] This will allow you to use SSL and solves a lot of problems where pages return **No instance available** errors. Make note of the original file's permissions and duplicate them on the replacement. Once you do this, restart Apache.//
42 42  
45 +7. 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 instructions on the command line and don't notice the naming difference of the files.
46 +
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.
49 +Steps 8, 9, 10. 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.