You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

I needed to install the WebObjects deployment environment on a CentOS 5.2 64 bit box, and by combining tidbits of information from the mailing lists and the wiki, I was able to have a working environment. This is how I did it :

1. You need to install a Java SDK. DON'T use the Java stuff from GNU, use a JDK from Sun instead. In my case, I installed JDK 1.5.0_16 from a RPM I got from I also created two symbolink links :

ln -s /usr/java/jdk1.5.0_16 /usr/java/jdk1.5
ln -s /usr/java/jdk1.5/bin/java /usr/bin/java

and you need to change your path in your bash profile (_~/.bash_profile) to have this path :


2. Get the WebObjects installer from mDimension's Web site :


and install it like this :

sudo /usr/java/jdk1.5/bin/java -jar WOInstaller.jar 5.4.3 /opt

(You can also install 5.3.3 instead of 5.4.3)
WebObjects frameworks are now installed in /opt

[root@ ~]# ls -l /opt/
total 12
drwxr-xr-x 3 root root 4096 Nov  9 08:19 Developer
drwxr-xr-x 4 root root 4096 Nov  9 08:19 Library
drwxr-xr-x 3 root root 4096 Nov  9 08:20 Local

3. Now we need to change some permissions. To follow the conventions from Mac OS X, we will create two users to run wotaskd and Monitor under this user :

sudo groupadd appserveradm
sudo useradd -g appserveradm appserver

and fix some permissions :

[root@ ~]# chown -R appserver:appserveradm /opt/Local
[root@ ~]# chown -R appserver:appserveradm /opt/Library
[root@ ~]# chmod 750 /opt/Library/WebObjects/JavaApplications/JavaMonitor.woa/JavaMonitor
[root@ ~]# chmod 750 /opt/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/
[root@ ~]# chmod 750 /opt/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd

4. Now we can start wotask and Monitor

[root@ ~]# su - appserver

Edit the bash profile of the appserver, and add this line :

NEXT_ROOT=/opt; export NEXT_ROOT

and run it manually in your current shell :

[appserver@ ~]$ NEXT_ROOT=/opt; export NEXT_ROOT

You can start wotaskd and Monitor to make sure that they run without any problems :

[appserver@ ~]$ $NEXT_ROOT/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd &
[appserver@ ~]$ $NEXT_ROOT/Library/WebObjects/JavaApplications/JavaMonitor.woa/JavaMonitor -WOPort 56789 &

5. Last step : compiling and installing the Apache module

Get the source of the module (adaptor) from Wonder. You only need the Adaptors (and its subfolders) folder.

Edit make.config and change the value of ADAPTOR_OS to LINUX.

and at the line before "endif\n#end Linux", add :


Go to the ApacheXX folder that match your Apache version. In my case, I'm using Apache 2.2 built from source and installed in /usr/local/apache.

[root@ Adaptors]# cd Apache2.2/
[root@ Apache2.2]# make
[root@ Apache2.2]# /usr/local/apache/bin/apxs -i -a -n WebObjects
[root@ Apache2.2]# cp -rp /opt/Library/WebObjects/WODocumentRoot/WebObjects /usr/local/apache/htdocs
[root@ Apache2.2]# cp apache.conf /usr/local/apache/conf/extra/webobjects.conf

And edit /usr/local/apache/conf/extra/webobjects.conf to comment the LoadModule WebObjects_module line. You can also change the WebObjectsAlias property, in my case I use /apps/WebObjects. Last step : add the following line in httpd.conf (near the end):

Include /conf/extra/webobjects.conf

Check for any errors with apachectl configtest, and if everything's ok, you are good to go. You can install your first app, don't forget that your app must be accessible by the appserver user or the appserveradm group. If your app don't start or if Monitor complains about a path, it might be a permission problem.

  • No labels