Skip to Content
Last modified by Aaron Rosenzweig on 2012/10/18 13:08
From version 35.1
edited by Pascal Robert
on 2010/08/20 19:53
Change comment: There is no comment for this version
To version 38.1
edited by Pascal Robert
on 2010/08/20 19:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,7 @@
7 7  
8 8  The steps I took as outlined in the wiki pages above:
9 9  
10 -~1. 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  
13 13  {{code}}
... ... @@ -15,8 +15,8 @@
15 15  <Directory />
16 16   Options FollowSymLinks
17 17   AllowOverride None
18 - #Order deny,allow
19 - #Deny from all
18 + \#Order deny,allow
19 + \#Deny from all
20 20  </Directory>
21 21  
22 22  {{/code}}
... ... @@ -37,7 +37,7 @@
37 37  
38 38  {{/code}}
39 39  
40 -2. My apache.conf (/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf) file contained the line to load the WebObject module
40 +1. My apache.conf (/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf) file contained the line to load the WebObject module
41 41  Confirm that apache.conf also includes:
42 42  
43 43  {{code}}
... ... @@ -46,9 +46,9 @@
46 46  
47 47  {{/code}}
48 48  
49 -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)
49 +1. 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)
50 50  
51 -4. Change permissions of the launch daemon plists for wotaskd and monitor to **exactly** what is written in the wiki
51 +1. Change permissions of the launch daemon plists for wotaskd and monitor to **exactly** what is written in the wiki
52 52  
53 53  {{code}}
54 54  
... ... @@ -60,21 +60,21 @@
60 60  
61 61  {{/code}}
62 62  
63 -5. Set your launch parameters in your application:
63 +1. Set your launch parameters in your application:
64 64  
65 65  {{code}}
66 66  
67 --WODirectConnectEnabled false
68 --WOHost localhost
69 --WOAdaptorURL [http://localhost/cgi-bin/WebObjects]
70 --WOPort 5555
67 +\-WODirectConnectEnabled false
68 +\-WOHost localhost
69 +\-WOAdaptorURL [http://localhost/cgi-bin/WebObjects]
70 +\-WOPort 5555
71 71  
72 72  {{/code}}
73 73  
74 -6. Update mod//WO
74 +1. Update mod//WO
75 75  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.//
76 76  
77 -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.
77 +1. 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.
78 78  
79 79  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.
80 80