Saturday morining 8:00 am I wake up roll out of bed, try and make myself presentable as quickly as possible and jump in the car to drive 30 miles south of my house. Today is the day we finish setting up our first Linux Fedora 5 server. On the agenda today is getting Apache 2.2.2 to talk with Tomcat 5.5.something Subversion up and running with our source code imported, Subversion working with Apache 2.2.2 and finally if we have time get Maven 2 loaded and the CruiseControl application installed. Since some of this stuff I have only done one time prior it was a full schedule to say the least.
9:00 am
Luckily Tom has already set up the server minus the XWindows libraries but including Tomcat 5, Subversion, and Apache 2.2.
Now we need to get the Apache server to communicate with the Tomcat server. This is not as easy as it sounds since the documentation on the Tomcat site has seemingly been abanden long ago. We copied down the .so file that we suppose would work for the Intel based x86 architecture and go about setting up the httpd.conf file to include the new shared library, add a workers.properties file to the httpd/conf directory and modify the server.xml file under the Tomcat installation to enable AJP13. Once completed we get repeated errors from the http server (Apache) exclaiming that the mod_jk.so file is bad. We go through several girations of this before, including investigating moving to another server Jetty or Resin.
For the Impatient (What works):
1.) Get Fedora 5 installled minus xWindows.
2.) Type “service httpd status” to get the status of Apache.
3.) If apache is not installed then install it using “yum install httpd”
4.) Try starting Tomcat “service tomcat5 start”
5.) If Tomcat is missing then type “yum install tomcat5”
6.) Test the installation “telnet localhost 80”
Now to get Tomcat working with Apache use the Proxy approach
1.) finish…. later. collecting our details.
