Skip to Content
Last modified by Aaron Rosenzweig on 2012/10/18 13:08
From version 22.1
edited by Kieran Kelleher
on 2009/03/25 23:42
Change comment: There is no comment for this version
To version 21.1
edited by David Holt
on 2008/11/20 19:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kieran
1 +XWiki.dholt
Content
... ... @@ -5,11 +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 -~1. Edit /etc/apache2/httpd.conf
11 -Search for "Directory /" and comment out the Order and Deny lines:
12 -
10 +Modify apache commenting out the two lines in /directory
13 13  <Directory />
14 14   Options FollowSymLinks
15 15   AllowOverride None
... ... @@ -17,22 +17,22 @@
17 17   #Deny from all
18 18  </Directory>
19 19  
20 -Then search for "ServerName" and add
18 +Then add
21 21  ServerName localhost
22 22  
23 23  Add a line that points to the WebObjects apache config file
24 24  Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
25 25  
26 -2. My apache.conf (/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf) file contained the line to load the WebObject module
27 -Confirm that apache.conf also includes:
24 +My apache.conf file contained the line to load the WebObject module
25 +Confirm that apache.conf includes:
28 28  WebObjectsConfig http:~/~/localhost:1085 10
29 29  
30 -3. 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
31 31  
32 -4. 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
33 33  644 system/wheel/everyone
34 34  
35 -5. Set your launch parameters in your application:
33 +Set your launch parameters in your application:
36 36  
37 37  --WODirectConnectEnabled false
38 38  --WOHost localhost
... ... @@ -39,10 +39,8 @@
39 39  --WOAdaptorURL http:~/~/localhost/cgi-bin/WebObjects
40 40  --WOPort 5555
41 41  
42 -6. Restart Apache
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.
43 43  
44 -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.
45 -
46 46  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.
47 47  
48 -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.
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.