Version 31.1 by Pascal Robert on 2011/05/09 01:42

Hide last authors
Ray Kiddy 30.1 1 If you are accessing your application with URLs that look like [[http://localhost:45437/cgi-bin/WebObjects/AppName.woa/]] (with the xxx:portnum instead of xxxx/-portnum) ... then you are using the [[Evil Direct Connect>>Development-Direct Connect]]. See that [[page>>Development-Direct Connect]] for why you don't want to be using Direct Connect. See this page for how to stop.
Kieran Kelleher 22.1 2
Ray Kiddy 30.1 3 A summary of the following steps that applies specifically to MacOS X 10.5.5 can be found here: [[Running Through Apache - Leopard & Snow Leopard Client - Summary>>Running Through Apache - Leopard & Snow Leopard Client - Summary]]
Kieran Kelleher 22.1 4
Kieran Kelleher 28.1 5 = Turning on Apache =
Kieran Kelleher 22.1 6
Pascal Robert 31.1 7 Go to **System Preferences > Sharing > Services** and turn on **Personal Web Sharing** if it is not already on. You can also do it by command line with "apachectl":
Kieran Kelleher 28.1 8
Pascal Robert 31.1 9 {{code theme="Eclipse"}}
10 sudo apachectl restart
11 {{/code}}
12
Kieran Kelleher 22.1 13 When you turn on your web server, Apache will listen on the network interfaces that were configured when it starts. If you change networks, you may need to manually restart apache. You can do this by either stopping and restarting Personal Web Sharing, or you can run "apachectl restart" from the commandline as the root user. Because this can get annoying if you are working on a laptop, or periodically using VPN's, there are a couple ways to make this process easier.
14
Kieran Kelleher 28.1 15 = Optional Extra Configuration: Explicitly Setting Your Hostname =
Kieran Kelleher 22.1 16
17 {{info title="Useful Information"}}
18
Kieran Kelleher 28.1 19 The changes in this section are only required if you want your hostname to be stable across network changes. While this simplifies many aspects of development (like testing cookies and https), it may cause problems with those specific aspects (cookies, https, etc.) if you need to be able to access your dev machine from a remote machine, including if you need to be able to test your web app from a Parallels VM.
Kieran Kelleher 22.1 20
Kieran Kelleher 28.1 21 Bonjour Delays: Apparently the procedure here is also useful for preventing "Bonjour" delays when you launch the browser to test your app on your development machine.
22
Kieran Kelleher 22.1 23 {{/info}}
24
Kieran Kelleher 28.1 25 == Edit Apache Config ==
Kieran Kelleher 22.1 26
Kieran Kelleher 28.1 27 {{warning title="Bonjour, comment ça va? .... Trés bien, merci!"}}
Kieran Kelleher 22.1 28
Kieran Kelleher 28.1 29 *Do NOT try to use the Bonjour / Rendezvous name of your machine in this step.* It will cause you grief. Accept this and don't even try. You have been warned.
Kieran Kelleher 22.1 30
Kieran Kelleher 28.1 31 {{/warning}}
32
Pascal Robert 31.1 33 Edit **/etc/apache2/httpd.conf**, find the line containing **ServerName** and change it to this. If you still running Tiger (OS X 10.4), the file is at **/etc/httpd/httpd.conf**. If you develop on Linux, the configuration file is probably in **/etc/httpd/conf**.
Kieran Kelleher 28.1 34
Kieran Kelleher 22.1 35 {{code}}
36
37 ServerName localhost
38
39 {{/code}}
40
Kieran Kelleher 28.1 41 That line may be commented out by default. You can simply uncomment it (remove the leading pound sign). You will also need to find this block
Kieran Kelleher 22.1 42
43 {{code}}
44
Ray Kiddy 30.1 45 # First, we configure the "default" to be a very restrictive set of
46 # features.
Kieran Kelleher 28.1 47 #
48 <Directory />
49 Options FollowSymLinks
50 AllowOverride None
51 Order deny,allow
52 Deny from all
53 </Directory>
54
55 {{/code}}
56
57 And modify like so:
58
59 {{code}}
60
Ray Kiddy 30.1 61 # First, we configure the "default" to be a very restrictive set of
62 # features.
Kieran Kelleher 28.1 63 #
64 <Directory />
65 Options FollowSymLinks
66 AllowOverride None
67 # Order deny,allow
68 # Deny from all
69 </Directory>
70
71 {{/code}}
72
73 Got to the very end of **/etc/apache2/httpd.conf** and add :
74
75 {{code}}
76
77 Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
78
79 {{/code}}
80
Pascal Robert 31.1 81 {{info}}
82 If you installed WebObjects in another directory (for instance, /Developer/WebObjects), prepend that directory path in front of /System.
83 {{/info}}
84
Kieran Kelleher 28.1 85 Then restart apache:
86
87 {{code}}
88
Kieran Kelleher 22.1 89 sudo apachectl restart
90
91 {{/code}}
92
Kieran Kelleher 28.1 93 == Tell the adaptor to use localhost ==
Kieran Kelleher 22.1 94
Kieran Kelleher 28.1 95 Edit **/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf** to make sure that your enabled/uncommented WebObjectsConfig property looks like this:
96
97 {{code}}
98
99 WebObjectsConfig http://localhost:1085 10
100
101 {{/code}}
102
103 (Note on Tiger, aka OS X 10.4.X, replace **Apache2.2** with **Apache** in the path above)
104
105 == Tell wotaskd to Use Localhost Too ==
106
Kieran Kelleher 22.1 107 Edit **/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties**
108
109 Add this line after the **WOPort=1085** one:
110
111 {{code}}
112
113 WOHost=localhost
114
115 {{/code}}
116
117 Now you need to restart wotaskd:
118
Pascal Robert 31.1 119 ===== OS X 10.5 Leopard and afterward (where launchd is used to control wotaskd) =====
Ray Kiddy 30.1 120
Kieran Kelleher 22.1 121 {{code}}
122
Pascal Robert 31.1 123 sudo launchctl stop com.apple.webobjects.wotaskd
Kieran Kelleher 22.1 124
125 {{/code}}
126
127 or
128
Pascal Robert 31.1 129 ===== {{color value="#000000"}}{*}OS X Tiger 10.4 and earlier{*}{{/color}} =====
Ray Kiddy 30.1 130
131 {{code}}
132
Pascal Robert 31.1 133 sudo systemstarter stop "WebObjects Services"
134 sudo systemstarter start "WebObjects Services"
Ray Kiddy 30.1 135
136 {{/code}}
137
138 launchd should automatically start wotaskd again for you if configured properly.
139
140 You can check for whether wotaskd is running as a launchd job by typing
141
142 {{code}}
143
144 sudo launchctl list | grep webobjects
145
146 {{/code}}
147
148 which will give something like this:
149
150 {{code}}
151
152 43 - com.apple.webobjects.wotaskd
153
154 {{/code}}
155
Pascal Robert 31.1 156 (In 10.5 it appears to be necessary to launch with launchctl. See [[Running Monitor and wotaskd on Mac OS X 10.5 "client">>WO 5.4 Getting Started||anchor="javamonitor"]])
Kieran Kelleher 22.1 157
Kieran Kelleher 28.1 158 == Finally, Configure your Application ==
Pascal Robert 24.1 159
160 Add or edit these launch parameters:
161
Kieran Kelleher 22.1 162 {{code}}
163
Pascal Robert 24.1 164 -WODirectConnectEnabled false
165 -WOHost localhost
166 -WOAdaptorURL http://localhost/cgi-bin/WebObjects
167 -WOPort 5555
Kieran Kelleher 22.1 168
169 {{/code}}
170
Pascal Robert 24.1 171 The WOPort is optional, but useful if you want consistent URLs for bookmarks and such. You can use any number you want, but it needs to be unique for each application you launch (or rather, you can only run one app instance on a given WOPort at a time). In WOLips, WOPort, WODirectConnectEnabled, and WOAdaptorURL already exist and just need to be updated. WOHost does not, and needs to be added. The dash in front of the name ("-WOHost") is important and must be in the name for the setting to work properly.
Kieran Kelleher 22.1 172
Pascal Robert 31.1 173 You may want to set this in your global WOLips settings so you don't have to set it every time you make a new launch configuration. You will need to go back and modify existing launch configurations with these settings even if you set it globally. Global settings only apply to newly created launch configurations. To change the global settings, in Eclipse, open the Eclipse menu, choose Preferences... and select WOLips > Launch.
Kieran Kelleher 22.1 174
Kieran Kelleher 28.1 175 = Apache Restart =
Kieran Kelleher 22.1 176
Kieran Kelleher 28.1 177 {{info title="Why would I need this?"}}
Kieran Kelleher 22.1 178
Kieran Kelleher 28.1 179 If you have a laptop and you get an "Application cannot be found" or some such error in the browser after auto-switching networks (for example going from a work network to a home network), restarting apache can resolve the error condition most of the time. A script is shown below to do that.
180 If you already implemented the "localhost" explicit hostname setup above, then you will probably not need to bother with this section.
181
Pascal Robert 31.1 182 No, really. Why would one need this? Is there a difference between ("apachectl stop" ; "apachectl start") and "apachectl restart"? If so, that may be a problem with apachectl. If there is a difference, why is the difference important? What bad thing will happen if one only uses "apachectl restart"? Pascal's answer: there is no difference between apachectl stop/start and apachectl restart, so the restart script could simply do a "apachectl restart".
Ray Kiddy 30.1 183
Kieran Kelleher 28.1 184 {{/info}}
185
Pascal Robert 24.1 186 == Making a restart script ==
Kieran Kelleher 22.1 187
Pascal Robert 24.1 188 Create a script named /usr/local/bin/restartApache and set the contents to:
Kieran Kelleher 22.1 189
190 {{code}}
191
Pascal Robert 24.1 192 #!/bin/bash
193 /usr/sbin/apachectl stop
194 sleep 1
195 /usr/sbin/apachectl start
Kieran Kelleher 22.1 196
197 {{/code}}
Pascal Robert 31.1 198
199 Please note that you DON'T need to do this if you set your ServerName in Apache to localhost. Running everything under localhost is the best way to go.