Skip to Content
Last modified by Aaron Rosenzweig on 2011/05/09 01:46
From version 31.1
edited by Pascal Robert
on 2011/05/09 01:42
Change comment: There is no comment for this version
To version 32.1
edited by David Holt
on 2008/10/29 12:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.probert
1 +XWiki.dholt
Content
... ... @@ -1,15 +1,9 @@
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.
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.
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>>Running Through Apache - Leopard & Snow Leopard Client - Summary]]
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. You can also do it by command line with "apachectl":
5 +Go to **System Preferences > Sharing > Services** and turn on **Personal Web Sharing** if it is not already on.
8 8  
9 -{{code theme="Eclipse"}}
10 -sudo apachectl restart
11 -{{/code}}
12 -
13 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 14  
15 15  = Optional Extra Configuration: Explicitly Setting Your Hostname =
... ... @@ -30,7 +30,7 @@
30 30  
31 31  {{/warning}}
32 32  
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**.
27 +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**.
34 34  
35 35  {{code}}
36 36  
... ... @@ -42,8 +42,8 @@
42 42  
43 43  {{code}}
44 44  
45 -# First, we configure the "default" to be a very restrictive set of
46 -# features.
39 +# First, we configure the "default" to be a very restrictive set of
40 +# features.
47 47  #
48 48  <Directory />
49 49   Options FollowSymLinks
... ... @@ -58,8 +58,8 @@
58 58  
59 59  {{code}}
60 60  
61 -# First, we configure the "default" to be a very restrictive set of
62 -# features.
55 +# First, we configure the "default" to be a very restrictive set of
56 +# features.
63 63  #
64 64  <Directory />
65 65   Options FollowSymLinks
... ... @@ -78,10 +78,6 @@
78 78  
79 79  {{/code}}
80 80  
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 -
85 85  Then restart apache:
86 86  
87 87  {{code}}
... ... @@ -92,7 +92,7 @@
92 92  
93 93  == Tell the adaptor to use localhost ==
94 94  
95 -Edit **/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf** to make sure that your enabled/uncommented WebObjectsConfig property looks like this:
85 +Edit **/System/Library/WebObjects/Adaptors/Apache/apache.conf** to make sure that your enabled/uncommented WebObjectsConfig property looks like this:
96 96  
97 97  {{code}}
98 98  
... ... @@ -100,8 +100,6 @@
100 100  
101 101  {{/code}}
102 102  
103 -(Note on Tiger, aka OS X 10.4.X, replace **Apache2.2** with **Apache** in the path above)
104 -
105 105  == Tell wotaskd to Use Localhost Too ==
106 106  
107 107  Edit **/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties**
... ... @@ -116,45 +116,18 @@
116 116  
117 117  Now you need to restart wotaskd:
118 118  
119 -===== OS X 10.5 Leopard and afterward (where launchd is used to control wotaskd) =====
120 -
121 121  {{code}}
122 122  
123 -sudo launchctl stop com.apple.webobjects.wotaskd
124 -
125 -{{/code}}
126 -
127 -or
128 -
129 -===== {{color value="#000000"}}{*}OS X Tiger 10.4 and earlier{*}{{/color}} =====
130 -
131 -{{code}}
132 -
133 133  sudo systemstarter stop "WebObjects Services"
134 134  sudo systemstarter start "WebObjects Services"
135 135  
136 136  {{/code}}
137 137  
138 -launchd should automatically start wotaskd again for you if configured properly.
114 +or
139 139  
140 -You can check for whether wotaskd is running as a launchd job by typing
116 +restart wotaskd and womonitor with launchctl if your WebObjects install launches that way.
117 +(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"]]
141 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 -
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"]])
157 -
158 158  == Finally, Configure your Application ==
159 159  
160 160  Add or edit these launch parameters:
... ... @@ -170,7 +170,7 @@
170 170  
171 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.
172 172  
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.
134 +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.
174 174  
175 175  = Apache Restart =
176 176  
... ... @@ -179,8 +179,6 @@
179 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 180  If you already implemented the "localhost" explicit hostname setup above, then you will probably not need to bother with this section.
181 181  
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".
183 -
184 184  {{/info}}
185 185  
186 186  == Making a restart script ==
... ... @@ -195,5 +195,3 @@
195 195  /usr/sbin/apachectl start
196 196  
197 197  {{/code}}
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.