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 :
Install Sun Java JDK
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 java.sun.com. I also created two symbolink links :
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 :
(You can also install 5.3.3 instead of 5.4.3)
WebObjects frameworks are now installed in /opt
Edit the bash profile of the appserver, and add this line :
and run it manually in your current shell :
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 :
and fix some permissions :
4. Now we can start wotask and Monitor
You can start wotaskd and Monitor to make sure that they run without any problems :
5. Last step : compiling and installing the Apache module
For Ubuntu distributions :
On that system the relevant command names are apache2ctl and apxs2, and the document root is /var/www (not /usr/local/apache/htdocs as in the example below).
(you will need httpd-devel and gcc)
For CentOS, RedHat or Fedora distributions :
.. default install location is then /etc/httpd
You can also find pre-built binaries of the module at webobjects.mdimension.com. If no pre-built binaries exist for your platform, follow those instructions:
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. (this can be found in Adaptors directory (JS)) (Adaptors directory is now under %PATH_OF_UNZIPPED_SOURCE%/Utilities )
If using modern Ubuntu (and OpenSuse 11.1 too) releases, you'll find that srandom is missing, so as mentioned on the list (JL) :
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.
In another case I ran 'make CC=gcc' in the Adaptors directory then moved to the Apache2.2 directory. (JS)
In OpenSuse 11.1, using Yast, you need to install the apache_devel, in order to get apxs2. I needed to create a symlink called apxs, pointing to apxs2, in order to run the make correctly.
Instead of copying the WebObjects directory, you can use a alias to point to the folder inside NEXT_ROOT. In your Apache configuration, add something like :
and add a directive to allow fetching files in this directory:
Or (depending on your Apache configuration) you could use a symbolic link.
You also need, as explained by the adaptor's README file, to add this directive in httpd.conf :
If you don't add it, you will get 403s (Forbidden) HTTP errors.
If you want to keep /cgi-bin/WebObjects as the base URL, you will need to remove a line in httpd.conf. Find the line that starts with ScriptAlias /cgi-bin and comment it out, or else Apache will try to find a WebObjects CGI in /cgi-bin instead of loading the adaptor from the Apache module.
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):
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.
Jerome Chan told me that you can check if the Apache module is loaded by doing this :
On my installation on OpenSuse 11.1, I had to change the path to the lib64 directory where Apache contains the modules.
Auto Start WOTaskd and WOMonitor
One last thing, you need a init script to start wotaskd and Monitor at boot time. This is the one I wrote :
You also need to add the script with chkconfig so that everything start up after a reboot. If you named the above script as "webobjects", do :
For CentOS, RedHat or Fedora distributions :
For Ubuntu :
A better choice for Ubuntu (later releases anyway) is to use upstart instead of rc.d. One major benefit is that you can configure upstart to respawn your instance of wotaskd if it crashes unexpectedly. This is an example of our upstart conf for wotaskd:
Drop the above into /etc/init/ (note NOT init.d) and start it initially with:
Problems with Application Responding to WOMonitor/WOTaskd
If your Linux server is a virtual machine or if it has multiple IP addresses, you may find that clicking 'Stop' in WOMonitor has no effect on instances. This can usually be solved for all Wonder-based applications running on hosts with such a problem by simply creating the following file (known as the 'Machine Properties' file in Wonder's ERXProperties):
And inside that file, add an array property that defines all the IP addresses assigned to your host, for example:
To learn more, see the class named WOHostUtilities in ERExtensions framework
If SELinux is enabled on your system, wotaskd won't run because of SELinux policies. You need to run :