Install Sun Java JDK
Make sure to install the correct "bit" version for the OS, e.g. install 64 bit JVM on a 64 bit installation, and a 32 bit JVM on a 32 bit installation! To find that information, do:
If the response is x86_64, it's a 64 bit system. If the response is i386 or i686, it's a 32 bit system.
Creating symbolic links as follows is useful (alternatively use the 'alternatives' command to manage JVMs):
and you need to change your path in your bash profile (_~/.bash_profile) to have this path :
2. Get the WebObjects installer from the wocommunity's Web site :
and install it like this :
WebObjects frameworks are now installed in /opt
To follow the conventions from Mac OS X, we will create two users to run wotaskd and Monitor under this user :
Edit the bash profile of the appserver
and add this line :
and run it manually in your current shell :
3. Next, we need to install the Wonder version wotaskd and JavaMonitor.
4. Now we need to change some permissions:
5. Now we can start wotask and Monitor
You can start wotaskd and Monitor to make sure that they run without any problems :
6. First step : installing Apache httpd
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
First, check if a pre-built module already exists at wocommunity.org. If you are running CentOS 6.x, you can use the module for CentOS 5.5, it works fine.
Once you have downloaded the module, you can install it with:
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.
Systems using upstart (Ubuntu and maybe others)
If you are running Ubuntu that have support for upstart, you can grab the two startup scripts for upstart on GitHub. Grab the two files (womonitor.conf and wotaskd.conf) and copy them in /etc/init/. Once they are in this directory, run:
Don't forget to change the permissions on the startup file so that the owner is root and that everyone have execution rights!
Systems not using upstart (CentOS, RedHat, Fedora and others)
If you are running a system not capable of running upstart, like CentOS, RedHat or older versions of Ubuntu, you need to use the old-style init.d startup script. Again, the scripts are available on GitHub. Grab the two files (womonitor and wotaskd) and copy them in /etc/init.d/.
Once the scripts are in /etc/init.d/, you can start them:
Last step: add the startup scripts under chkconfig control with:
If you are using Ubuntu or Debian without upstart support, you need to use update-rc.d instead of chkconfig:
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, or that the applications never start (the level just go up and down non-stop). 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 :
Be aware that SELinux is enabled by default on CentOS 6.x, you will need to either call the setsebool command or to disable SELinux