Skip to Content
Last modified by Aaron Rosenzweig on 2011/05/09 01:46
From version 32.1
edited by David Holt
on 2008/10/29 12:33
Change comment: There is no comment for this version
To version 30.1
edited by Ray Kiddy
on 2011/01/13 17:04
Change comment: add question to restart script info

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dholt
1 +XWiki.kiddyr
Content
... ... @@ -1,5 +1,7 @@
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/]] (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.
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 +
3 3  = Turning on Apache =
4 4  
5 5  Go to **System Preferences > Sharing > Services** and turn on **Personal Web Sharing** if it is not already on.
... ... @@ -36,8 +36,8 @@
36 36  
37 37  {{code}}
38 38  
39 -# First, we configure the "default" to be a very restrictive set of
40 -# features.
41 +# First, we configure the "default" to be a very restrictive set of
42 +# features.
41 41  #
42 42  <Directory />
43 43   Options FollowSymLinks
... ... @@ -52,8 +52,8 @@
52 52  
53 53  {{code}}
54 54  
55 -# First, we configure the "default" to be a very restrictive set of
56 -# features.
57 +# First, we configure the "default" to be a very restrictive set of
58 +# features.
57 57  #
58 58  <Directory />
59 59   Options FollowSymLinks
... ... @@ -82,7 +82,7 @@
82 82  
83 83  == Tell the adaptor to use localhost ==
84 84  
85 -Edit **/System/Library/WebObjects/Adaptors/Apache/apache.conf** to make sure that your enabled/uncommented WebObjectsConfig property looks like this:
87 +Edit **/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf** to make sure that your enabled/uncommented WebObjectsConfig property looks like this:
86 86  
87 87  {{code}}
88 88  
... ... @@ -90,6 +90,8 @@
90 90  
91 91  {{/code}}
92 92  
95 +(Note on Tiger, aka OS X 10.4.X, replace **Apache2.2** with **Apache** in the path above)
96 +
93 93  == Tell wotaskd to Use Localhost Too ==
94 94  
95 95  Edit **/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties**
... ... @@ -104,6 +104,8 @@
104 104  
105 105  Now you need to restart wotaskd:
106 106  
111 +===== OS X Tiger 10.4 =====
112 +
107 107  {{code}}
108 108  
109 109  sudo systemstarter stop "WebObjects Services"
... ... @@ -113,7 +113,32 @@
113 113  
114 114  or
115 115  
116 -restart wotaskd and womonitor with launchctl if your WebObjects install launches that way.
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 +
117 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"]]
118 118  
119 119  == Finally, Configure your Application ==
... ... @@ -140,6 +140,9 @@
140 140  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.
141 141  If you already implemented the "localhost" explicit hostname setup above, then you will probably not need to bother with this section.
142 142  
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 +
143 143  {{/info}}
144 144  
145 145  == Making a restart script ==