The packages will work on CentOS and RedHat Enterprise 5.x or 6.x, or Amazon Linux, with Apache httpd 2.2 or 2.4.
Installing a deployment environment on platforms that uses RPM packages is now even easier than ever.
- Install a JDK. You can install openjdk with Yum (yum install java-1.6.0-openjdk) or get the JDK from Oracle.
Install the Yum repository of the WOCommunity like this:
Once it's done, you can use Yum to install wotaskd and JavaMonitor.
To install the module for Apache httpd 2.2, run:
for Apache httpd 2.4:
If SELinux is enabled on your system, wotaskd won't be reachable due to its preventing Apache from opening TCP connections. If you're comfortable with allowing Apache to connect to any TCP ports (including external hosts), you can run the following:
And you're done! When the packages are installed, the services are started automatically. JavaMonitor will be running on port 56789. Your Project Wonder applications goes into /opt/Local/Library/WebObjects/Applications.
If you wish to restart wotaskd or Monitor, startup scripts are located in /etc/init.d. You can use the service tool to stop or restart them:
(replace stop with restart to restart them in one step).
When Monitor is started, it will report to the console that is available at address like "ip-10-212-110-28" but that is the internal address of the Amazon server. The external address, which you must use, is available in the AWS console, and of the form "ec2-xx-vv-zz-ww.compute-1.amazonaws.com".
Don't forget to change the password in JavaMonitor after you made the installation!
Notes on CentOS 7 64/ Apache 2.4
The yum repositories for deployment artifacts is a little out of date, so these instructions are based on wonder source and compiling the adaptor on the target system.
Compiling the Apache Adaptor
Configuring Apache for WebObjects
The standard apache.conf (found in the wonder source at wonder/Utilities/Adaptors/Apache2.4/apache.conf) should work fine. Here are a couple of modifications that worked for me:
The authorization for Apache changed between 2.2 and 2.4. If you're used to "Allow from all" or "Deny from all" you should know that Apache 2.4 syntax has changed so this is how those allows/denies work now. This is a mostly permissive structure restricting some of the verbs that are not used (We have some configs that allow PUT, DELETE, PROPFIND, etc... but they don'tcall me "Little Paranoid Larry" for nothing.
CentOS7 switched to using FirewallD from IP Tables. I've tried to understand firewalld and I'm actually digging it even though it's a big change from IP Tables. Useful info on Firewalld can be found at Linux firewalld information at Oracle or FirewallD at Fedora.
The cheat sheet commands that help get started are:
As is mentioned in https://wiki.wocommunity.org/display/documentation/Installing+a+deployment+environment+on+RedHat,+CentOS+or+Amazon+Linux,
you can open up apache to network connections using the command:
If you have additional problems with the SELinux configuration, check the context and ownership of files. More useful information on SELinux can be found at http://wiki.centos.org/HowTos/SELinux.