Skip to Content
Last modified by Aaron Rosenzweig on 2011/05/09 01:46
From version 69.1
edited by Timothy Worman
on 2010/08/20 21:42
Change comment: There is no comment for this version
To version 71.1
edited by Pascal Robert
on 2011/05/09 01:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.tworman
1 +XWiki.probert
Content
... ... @@ -1,32 +1,32 @@
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>>Web Applications-Development-Direct Connect]]. See that [[page>>Web Applications-Development-Direct Connect]] for why you don't want to be using Direct Connect. See this page for how to stop.
1 +If you are accessing your application with URLs that look like [[http:~~/~~/localhost:45437/cgi-bin/WebObjects/AppName.woa/>>url:http://localhost:45437/cgi-bin/WebObjects/AppName.woa/||shape="rect"]] (with the xxx:portnum instead of xxxx/-portnum) ... then you are using the [[Evil Direct Connect>>doc:WO.Development-Direct Connect]]. See that [[page>>doc:WO.Development-Direct Connect]] for why you don't want to be using Direct Connect. See this page for how to stop.
2 2  
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]]
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>>doc:Running Through Apache - Leopard & Snow Leopard Client - Summary]]
4 4  
5 5  = Turning on Apache =
6 6  
7 -Go to **System Preferences > Sharing > Services** and turn on **Personal Web Sharing** if it is not already on.
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":
8 8  
9 -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.
9 +{{code theme="Eclipse"}}
10 +sudo apachectl restart
11 +{{/code}}
10 10  
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 +
11 11  = Optional Extra Configuration: Explicitly Setting Your Hostname =
12 12  
13 13  {{info title="Useful Information"}}
18 +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. Pascal's note: setting ServerName to localhost won't block access from other network interfaces. The only Apache configuration that can block access from other interfaces than localhost is the Listen directive. As long as you let Apache to listen on all network interfaces, access from other machines will work.
14 14  
15 -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.
16 -
17 17  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.
18 -
19 19  {{/info}}
20 20  
21 21  == Edit Apache Config ==
22 22  
23 23  {{warning title="Bonjour, comment ça va? .... Trés bien, merci!"}}
24 -
25 -*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.
26 -
26 +**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.
27 27  {{/warning}}
28 28  
29 -Edit **/etc/httpd/httpd.conf**, find the line containing **ServerName** and change it to this. If you use Leopard (OS X 10.5), the file is at **/etc/apache2/httpd.conf**.
29 +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**.
30 30  
31 31  {{code}}
32 32  
... ... @@ -34,12 +34,12 @@
34 34  
35 35  {{/code}}
36 36  
37 -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
37 +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
38 38  
39 39  {{code}}
40 40  
41 -# First, we configure the "default" to be a very restrictive set of
42 -# features.
41 +# First, we configure the "default" to be a very restrictive set of
42 +# features.
43 43  #
44 44  <Directory />
45 45   Options FollowSymLinks
... ... @@ -54,8 +54,8 @@
54 54  
55 55  {{code}}
56 56  
57 -# First, we configure the "default" to be a very restrictive set of
58 -# features.
57 +# First, we configure the "default" to be a very restrictive set of
58 +# features.
59 59  #
60 60  <Directory />
61 61   Options FollowSymLinks
... ... @@ -74,6 +74,10 @@
74 74  
75 75  {{/code}}
76 76  
77 +{{info}}
78 +If you installed WebObjects in another directory (for instance, /Developer/WebObjects), prepend that directory path in front of /System.
79 +{{/info}}
80 +
77 77  Then restart apache:
78 78  
79 79  {{code}}
... ... @@ -108,22 +108,22 @@
108 108  
109 109  Now you need to restart wotaskd:
110 110  
111 -===== OS X Tiger 10.4 =====
115 +===== OS X 10.5 Leopard and afterward (where launchd is used to control wotaskd) =====
112 112  
113 113  {{code}}
114 114  
115 -sudo systemstarter stop "WebObjects Services"
116 -sudo systemstarter start "WebObjects Services"
119 +sudo launchctl stop com.apple.webobjects.wotaskd
117 117  
118 118  {{/code}}
119 119  
120 120  or
121 121  
122 -===== OS X 10.5 Leopard (where launchd is used to control wotaskd) =====
125 +===== (% style="color: rgb(0,0,0);" %)**OS X Tiger 10.4 and earlier**(%%) =====
123 123  
124 124  {{code}}
125 125  
126 -sudo launchctl stop com.apple.webobjects.wotaskd
129 +sudo systemstarter stop "WebObjects Services"
130 +sudo systemstarter start "WebObjects Services"
127 127  
128 128  {{/code}}
129 129  
... ... @@ -145,7 +145,7 @@
145 145  
146 146  {{/code}}
147 147  
148 -(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"]]
152 +(In 10.5 it appears to be necessary to launch with launchctl. See [[Running Monitor and wotaskd on Mac OS X 10.5 "client">>doc:WO.WO 5\.4 Getting Started||anchor="javamonitor"]])
149 149  
150 150  == Finally, Configure your Application ==
151 151  
... ... @@ -160,17 +160,17 @@
160 160  
161 161  {{/code}}
162 162  
163 -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.
167 +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.
164 164  
165 -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.
169 +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.
166 166  
167 167  = Apache Restart =
168 168  
169 169  {{info title="Why would I need this?"}}
170 -
171 171  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.
172 -If you already implemented the "localhost" explicit hostname setup above, then you will probably not need to bother with this section.
175 + If you already implemented the "localhost" explicit hostname setup above, then you will probably not need to bother with this section.
173 173  
177 +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".
174 174  {{/info}}
175 175  
176 176  == Making a restart script ==
... ... @@ -185,3 +185,5 @@
185 185  /usr/sbin/apachectl start
186 186  
187 187  {{/code}}
192 +
193 +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.