Skip to Content
Version 37.1 by David Holt on 2010/07/26 16:30
Hide last authors
David Holt 20.1 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:
David Avendasora 14.1 2
David Holt 32.1 3 [[Development Tools-Running Through Apache>>Development Tools-Running Through Apache]]
David Avendasora 14.1 4 [[WO 5.4 Getting Started]]
5
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
Kieran Kelleher 22.1 8 The steps I took as outlined in the wiki pages above:
David Avendasora 14.1 9
David Holt 32.1 10 ~1. Edit /etc/apache2/httpd.conf
Kieran Kelleher 22.1 11 Search for "Directory /" and comment out the Order and Deny lines:
12
David Avendasora 14.1 13 <Directory />
David Holt 36.1 14 Options FollowSymLinks
15 AllowOverride None
16 Order deny,allow
17 Deny from all
David Avendasora 14.1 18 </Directory>
19
Kieran Kelleher 22.1 20 Then search for "ServerName" and add
David Avendasora 14.1 21 ServerName localhost
22
23 Add a line that points to the WebObjects apache config file
24 Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
25
Kieran Kelleher 22.1 26 2. My apache.conf (/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf) file contained the line to load the WebObject module
David Holt 32.1 27 Confirm that apache.conf also includes:
David Holt 36.1 28 WebObjectsConfig [[http://localhost:1085]] 10
David Avendasora 14.1 29
Timothy Worman 26.1 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)
31
32 4. Change permissions of the launch daemon plists for wotaskd and monitor to **exactly** what is written in the wiki
David Holt 36.1 33 644 system/wheel/everyone
Timothy Worman 26.1 34
David Holt 32.1 35 {{code}}
36
David Holt 36.1 37 // cd to the LaunchDaemons directory and execute the following commands
David Holt 32.1 38 $ chmod 644 com.apple.webobjects.womonitor.plist
39 $ chmod 644 com.apple.webobjects.wotaskd.plist
40 $ sudo chown root:wheel com.apple.webobjects.womonitor.plist
41 $ sudo chown root:wheel com.apple.webobjects.wotaskd.plist
42
43 {{/code}}
44
Kieran Kelleher 22.1 45 5. Set your launch parameters in your application:
David Avendasora 14.1 46
David Holt 36.1 47 WODirectConnectEnabled false
48 WOHost localhost
49 WOAdaptorURL [[http://localhost/cgi-bin/WebObjects]]
50 WOPort 5555
David Avendasora 14.1 51
Timothy Worman 26.1 52 6. Update mod//WO
53 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.//
54
Kieran Kelleher 22.1 55 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.
56
David Avendasora 14.1 57 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.
58
Pascal Robert 34.1 59 I needed to change permissions on /Library/WebObjects/Configuration because I was getting this error:
60
61 Don't have permission to write to Configuration Directory /Library/WebObjects/Configuration/ as this user; please change the permissions.
62
63 {{code}}
64
65 sudo chown _appserver:_appserveradm Configuration
66
67 {{/code}}
68
Kieran Kelleher 22.1 69 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.
Pascal Robert 34.1 70
71 See this page for debugging tips:&nbsp;[[WO:Debugging wotaskd and JavaMonitor]]