Skip to Content
Version 31.1 by Ramsey Gurley on 2009/10/24 15:03
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
Ramsey Gurley 30.1 3 [[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
Ramsey Gurley 30.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 />
Ramsey Gurley 30.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
Ramsey Gurley 30.1 27 Confirm that apache.conf also includes:
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
Ramsey Gurley 30.1 33 644 system/wheel/everyone
Timothy Worman 26.1 34
Kieran Kelleher 22.1 35 5. Set your launch parameters in your application:
David Avendasora 14.1 36
Ramsey Gurley 30.1 37 --WODirectConnectEnabled false
38 --WOHost localhost
39 --WOAdaptorURL http:~/~/localhost/cgi-bin/WebObjects
40 --WOPort 5555
David Avendasora 14.1 41
Timothy Worman 26.1 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.//
44
Kieran Kelleher 22.1 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
David Avendasora 14.1 47 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.
48
Kieran Kelleher 22.1 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.