Skip to Content
Last modified by Aaron Rosenzweig on 2011/05/09 01:46
From version 30.1
edited by Ray Kiddy
on 2011/01/13 17:04
Change comment: add question to restart script info
To version 35.1
edited by Kieran Kelleher
on 2008/11/23 19:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kiddyr
1 +XWiki.kieran
Content
... ... @@ -1,6 +1,6 @@
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]]
3 +A summary of the following steps that applies specifically to MacOS X 10.5.5 can be found here: [[Running Through Apache - Leopard Client 10.5.5 - Summary]]
4 4  
5 5  = Turning on Apache =
6 6  
... ... @@ -38,8 +38,8 @@
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
... ... @@ -92,7 +92,7 @@
92 92  
93 93  {{/code}}
94 94  
95 -(Note on Tiger, aka OS X 10.4.X, replace **Apache2.2** with **Apache** in the path above)
95 +(Note on Tiger (OS X 10.4.X, replace **Apache2.2** with **Apache** in the path above)
96 96  
97 97  == Tell wotaskd to Use Localhost Too ==
98 98  
... ... @@ -108,8 +108,6 @@
108 108  
109 109  Now you need to restart wotaskd:
110 110  
111 -===== OS X Tiger 10.4 =====
112 -
113 113  {{code}}
114 114  
115 115  sudo systemstarter stop "WebObjects Services"
... ... @@ -119,32 +119,7 @@
119 119  
120 120  or
121 121  
122 -===== OS X 10.5 Leopard (where launchd is used to control wotaskd) =====
123 -
124 -{{code}}
125 -
126 -sudo launchctl stop com.apple.webobjects.wotaskd
127 -
128 -{{/code}}
129 -
130 -launchd should automatically start wotaskd again for you if configured properly.
131 -
132 -You can check for whether wotaskd is running as a launchd job by typing
133 -
134 -{{code}}
135 -
136 -sudo launchctl list | grep webobjects
137 -
138 -{{/code}}
139 -
140 -which will give something like this:
141 -
142 -{{code}}
143 -
144 -43 - com.apple.webobjects.wotaskd
145 -
146 -{{/code}}
147 -
120 +restart wotaskd and womonitor with launchctl if your WebObjects install launches that way.
148 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"]]
149 149  
150 150  == Finally, Configure your Application ==
... ... @@ -171,9 +171,6 @@
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 172  If you already implemented the "localhost" explicit hostname setup above, then you will probably not need to bother with this section.
173 173  
174 -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"?
175 -
176 -
177 177  {{/info}}
178 178  
179 179  == Making a restart script ==