Skip to Content
Last modified by Aaron Rosenzweig on 2012/10/18 13:08
From version 19.1
edited by David Holt
on 2008/11/20 19:00
Change comment: There is no comment for this version
To version 26.1
edited by Timothy Worman
on 2010/08/20 21:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Running Through Apache - Leopard Client 10.5.5 - Summary
1 +Running Through Apache - Leopard & Snow Leopard Client - Summary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dholt
1 +XWiki.tworman
Content
... ... @@ -1,44 +1,93 @@
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 -[[Development Tools-Running Through Apache]]
3 +[[Development Tools-Running Through Apache>>Development Tools-Running Through Apache]]
4 4  [[WO 5.4 Getting Started]]
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:
8 +The steps I took as outlined in the wiki pages above:
9 9  
10 -Modify apache commenting out the two lines in /directory
10 +~1. Edit /etc/apache2/httpd.conf
11 +Search for "Directory /" and comment out the Order and Deny lines:
12 +
13 +{{code}}
14 +
11 11  <Directory />
12 - Options FollowSymLinks
13 - AllowOverride None
14 - #Order deny,allow
15 - #Deny from all
16 + Options FollowSymLinks
17 + AllowOverride None
18 + #Order deny,allow
19 + #Deny from all
16 16  </Directory>
17 17  
18 -Then add
22 +{{/code}}
23 +
24 +Then search for "ServerName" and add
25 +
26 +{{code}}
27 +
19 19  ServerName localhost
20 20  
30 +{{/code}}
31 +
21 21  Add a line that points to the WebObjects apache config file
33 +
34 +{{code}}
35 +
22 22  Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
23 23  
24 -My apache.conf file contained the line to load the WebObject module
25 -Confirm that apache.conf includes:
26 -WebObjectsConfig http:~/~/localhost:1085 10
38 +{{/code}}
27 27  
28 -Add the WOHost localhost to the properties file in wotaskd
40 +2. My apache.conf (/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf) file contained the line to load the WebObject module
41 +Confirm that apache.conf also includes:
29 29  
30 -Change permissions of the two lauchdaemons to **exactly** what is written in the wiki
31 -644 system/wheel/everyone
43 +{{code}}
32 32  
33 -Set your launch parameters in your application:
45 +WebObjectsConfig [http://localhost:1085] 10
34 34  
35 ---WODirectConnectEnabled false
36 ---WOHost localhost
37 ---WOAdaptorURL http:~/~/localhost/cgi-bin/WebObjects
38 ---WOPort 5555
47 +{{/code}}
39 39  
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.
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)
41 41  
51 +4. Change permissions of the launch daemon plists for wotaskd and monitor to **exactly** what is written in the wiki
52 +
53 +{{code}}
54 +
55 +$ cd /Library/LaunchDaemons/
56 +$ chmod 644 com.apple.webobjects.womonitor.plist
57 +$ chmod 644 com.apple.webobjects.wotaskd.plist
58 +$ sudo chown root:wheel com.apple.webobjects.womonitor.plist
59 +$ sudo chown root:wheel com.apple.webobjects.wotaskd.plist
60 +
61 +{{/code}}
62 +
63 +5. Set your launch parameters in your application:
64 +
65 +{{code}}
66 +
67 +-WODirectConnectEnabled false
68 +-WOHost localhost
69 +-WOAdaptorURL [http://localhost/cgi-bin/WebObjects]
70 +-WOPort 5555
71 +
72 +{{/code}}
73 +
74 +6. Update mod//WO
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 +
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.
78 +
42 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 43  
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.
81 +I needed to change permissions on /Library/WebObjects/Configuration because I was getting this error:
82 +
83 +Don't have permission to write to Configuration Directory /Library/WebObjects/Configuration/ as this user; please change the permissions.
84 +
85 +{{code}}
86 +
87 +sudo chown _appserver:_appserveradm Configuration
88 +
89 +{{/code}}
90 +
91 +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.
92 +
93 +See this page for debugging tips:&nbsp;[[WO:Debugging wotaskd and JavaMonitor]]