Open source solutions can sometimes cause headaches.  I’m probably going to get some people going ‘you should have done this-this-that’ with this post if someone stumbles on it, but whatever the case may be this is my opinion and our work and I’m sticking to it.

When attempting to use xPlanner 5.5 of a native Fedora Core 8 install we ran into some key issues.  First off, the embedded Apache and Tomcat are useless.  There probably is some sort of configurational voodoo we could have pulled off but in all honesty admins can save themselves a lot of headache and simply removing the install-existing Apache and Tomcat and instead saving themselves the trouble and simply getting the full packages from the Apache website.

The preliminary difficulties we ran into dealt with the directory structure of Tomcat being different than documentation online for troubleshooting.   Lack of /ROOT/ for one where one usually would put their deployable .war files was one that made a bunch of red flags pop up, and caused a good few hours of frustration with trying to get the system up and running.  Also, related yet separate, the .war files would appear to deploy however refuse to display the usual ‘expected’ page when visiting the server’s http://localhost:8080/ page, and by default will return an error.  With some poking at it we got it to not error out, however we couldn’t get the page to display anything but blank.   IE and Firefox would display ‘done’, as if it did a clean load but would not display content on the page.

A full out install of Apache and Tomcat packages resolved this issue, however it’s recommended that admin double check to make sure their $CATALINA_HOME and $JAVA_HOME environment variables are correctly set.  Save yourselves the headache we had to go through.

You Should Also Check Out This Post:

More Active Posts: