Deployment-Windows WO 5.3 - WO 5.4

Copy the content of /System/Library/WebObjects/WODocumentRoot to your apache document root directory. If you don't use D2W or D2JC I think you can omit the both Java folders.

88

89

If you are installing WebObjects 5.3 copy /System/Library/PrivateFrameworks/ to C:/Apple/Library

90

91

At least copy the jar files from /Library/WebObjects/Extensions to c:/Apple/Local/Library/WebObjects/Extensions.

axis.jar

axis-ant.jar

commons-discovery-0.2.jar

98

commons-logging-1.0.4.jar

derby.jar

derbyclient.jar

jaxrpc.jar

log4j-1.2.14.jar

saaj.jar

serializer.jar

servlet.jar

wsdl4j-1.5.1.jar

xalan.jar

xercesImpl.jar

xml-apis.jar

= Add environment variable =

114

115

Under "System" add the environment variable NEXT//ROOT = C:/Apple//

116

117

= Installing the Apache Adaptor =

118

119

Copy the [[mod//WebObjects.so//>>http://webobjects.mdimension.com/wonder/mod_WebObjects/Apache2.2/windows/mod_WebObjects.so]] file to c:/apache/modules

In some cases apache won't launch on a Windows Server system with this module.

124

In this case you should install the .Net Framework (3.x) on your system.

= Configuring Apache =

129

130

Open the httpd.conf file in c:/apache/conf and search for the line "LoadModule rewrite//module modules/mod//rewrite.so" and put the following line right befor that:

LoadModule WebObjects_module modules/mod_WebObjects.so

At the end of the httpd.conf file add the following lines:

# WebObjects 5.4: Enable the WebObjects module. loadModule should be added before mod_rewrite

143

Include conf/extra/httpd-webobjects.conf

Find the <Directory /> entry and comment out the last two lines

Options FollowSymLinks

AllowOverride None

# Order deny,allow

# Deny from all

</Directory>

Create the file httpd-webobjects.conf in your c:/apache/conf/extra folder:

# WebObjects 5.4: Enable the WebObjects module. Should be loaded before mod_rewrite

165

# LoadModule WebObjects_module modules/mod_WebObjects.so

166

167

# Path to the Document Root of your Webserver,

168

# it should contain a directory named WebObjects

169

WebObjectsDocumentRoot c:/apache/htdocs

170

171

# You can change the 'cgi-bin' part of WebObjectsAlias to whatever you

172

# prefer (such as Apps), but the 'WebObjects' part is required.

173

WebObjectsAlias /Apps/WebObjects

174

175

# Here are the 3 possible configuration modes.

176

# The apache module uses one of them to get information

177

# about your deployed applications.

178

# 1085 is the reserved port on which wotaskd processes listen to by default.

179

180

# Host List Configuration

181

# wotaskd is started automatically on supported platforms,

182

# so this is the default mode.

183

# The apache module gets its configuration from the wotaskds

184

# listed on the configuration line

185

# For multiple hosts:

186

# WebObjectsConfig http://<name-of-a-host>:<port-on-a-host>,http://<name-of-another-host>:<port-on-a-host> <interval>

187

# For localhost:

188

WebObjectsConfig http://localhost:1085 10

189

190

# Multicast Configuration

191

# The apache module gets its configuration from all wotaskds

192

# that respond to the multicast call on the subnet

193

# WebObjectsConfig webobjects://239.128.14.2:1085 10

194

195

# File Configuration

196

# The apache module gets its configuration from one file

197

# WebObjectsConfig file://<path-to-a-xml-config-file> 10

198

199

# To enable public access to the WOAdaptorInfo page, uncomment the following line

200

# WebObjectsAdminUsername public

201

202

# To enable the WOAdaptorInfo page with restricted access,

203

# uncomment the next two lines and set the user and password

204

# To access the WOAdaptorInfo page with restricted access,

205

# use a URL like: http://webserver/cgi-bin/WebObjects/WOAdaptorInfo?user+password.

206

# WebObjectsAdminUsername user

207

# WebObjectsAdminPassword password

208

209

# To change the logging options, read the following comments:

210

# The option name is "WebObjectsLog" and the first value indicates the path of the log file.

211

# The second value indicates the log level. There are five, in decreasing informational order:

212

# "Debug", "Info", "Warn", "Error", "User"

213

#

214

# Note: To enable logging, touch '/tmp/logWebObjects' as the administrator user (usually root).

215

# Under Windows create c:\TEMP\logWebObjects

216

217

# The following line is the default:

218

# WebObjectsLog /Library/WebObjects/Logs/WebObjects.log Debug

You had to restart your Apache Service to apply your changes.

223

224

= Installing WOTaskDaemon as a Windows Service =

225

226

=== Using Microsoft Windows 2003 resource kit ===

227

228

Microsoft provides free tools to register applications as services : instsrv and srvany.

229

Both are bundled with "Microsoft Windows 2003 resource kit" which can be downloaded [[here>>http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en]].

230

231

Below a quick translation of the [[KB469536>>http://support.microsoft.com/kb/469536/fr]] which describes their usage :

232

233

First create a new service using instsrv that refers to the srvany executable

C:\>C:\Program Files\Windows Resource Kits\Tools\Instsrv WOTaskD C:\Program Files\Windows Resource Kits\Tools\srvany.exe

Then fire regedit and navigate to **HKEY//LOCAL//MACHINEYSTEMurrentControlSetervicesOTaskD**

242

Add a sub-key named "Parameters".

243

In this sub-key add a new REG//SZ key named "Application" and put the path of the WOTaskD.cmd file.//

244

245

Your reg key should now look like below :

246

[[image:wotaskd_reg.png||border="1"]]

247

To try your newly created service simply start it by typing :

C:\>net start WOTaskD

=== ===

You should be aware that srvany is just a laucher, this means that the "service" has no control over WOTaskD's sub-processes:

258

stopping the service has no effect on WOTaskD. For now the only solution I found is to use the following lines in a cmd file :

net stop apache2.2

net stop wotaskd

taskkill /F /IM java.exe /T

=== Using FireDameon ===

269

270

You can use FireDaemon and add a new Service:

271

Executable: C:ppleibraryebObjectsavaApplicationsotaskd.woaotaskd.CMD

272

Working Directory:C:ppleibraryebObjectsavaApplicationsotaskd.woa

273

274

To test the system you can also install WO Monitor as a service:

275

Executable: C:ppleibraryebObjectsavaApplicationsavaMonitor.woaavaMonitor.CMD

276

Working Directory:C:ppleibraryebObjectsavaApplicationsavaMonitor.woa

277

278

= **Testing the installation** =

279

280

Now that everything should be set up properly, it is time for a small test. First, let's look if wotaskd is working.

281

282

Open a browser and go to http:~/~/<myhost>:1085If it works, you should see the host's configuration displayed in the browser. Now, start WOMonitor (double click on ...avaMonitor.woaavaMonitor.CMD) if it is not already running as a service.

283

Wait a few seconds, then point the browser to http:~/~/<myhost>:56789

284

285

You should see Monitor's main window. Now you can start deploying your applications.

= Solving issues =

=== The requested URL ... was not found ===

290