Author Topic: http and tomcat?  (Read 1299 times)

pixelpshr

  • Newbie
  • *
  • Posts: 10
    • View Profile
http and tomcat?
« on: May 23, 2014, 06:32:50 PM »
Hello,
First I want to thank you for the effort you've put into your book(s) and the lengths you've gone to in creating the guide to OS X Server that Apple "forgot" to publish.

I am looking forward to your explanation of web site configuration under Server. I have to admit that it has me flummoxed. Of course, adding to my confusion is the fact that I also need to support Apache Tomcat. I have managed to get tomcat working, and having httpd hand off requests for *.jsp pages to the tomcat server. But, it seems like such a kludge that I cannot believe that I did it the way nature (ok, the developers) intended.

I'm hoping that you might have a chapter or appendix that discusses proper tomcat configuration.

Thanks!
Thom

Reid Bundonis

  • Administrator
  • Full Member
  • *****
  • Posts: 107
    • View Profile
Re: http and tomcat?
« Reply #1 on: May 23, 2014, 09:10:59 PM »
Thank you for your comments and welcome to the forum.  I am glad the book is proving useful. 

Tomcat on OS X has been a saga littered with beaten down admins.  From the travesty that was WebObjects under tomcat to the current fragile state of JAMF, Tomcat is a beast that is tough to tame.

You know, the funny thing is that one of the original purposes I had for the original Rhapsody server was to run a web site, on Apache, on an Apple Server.  Back then it was all about the configuration files.  It was pure Apache.  Anything you wanted to happen, you could make it work.  I even remember writing one of my first shell daemons, Scout (get it, Apache... Scout - I thought I was so clever).  It would watch the parent Apache process and respawn when it died.  Yep, the joy of failing processes back in the Rhapsody days. 

10.6.8 was likely the pinnacle of GUI administration of Web Services on OS X.  The limitations and lock in since makes it frustrating at best to host anything more than the default site.  Conf files that overwrite your changes, performance issues that seem to have no explanation (folder listings in 10.7 Server... oh the pain), and the "change for change's sake" approach to services as OS X evolves.

The second book will have a Web and Wiki section.  However, I am delaying that section from the first release as Profile Manager has hung me up these past two months with its constant updates.  I am aiming for a delivery to Apple before the end of this month.  Then the 1.1 version of the book should have the Web and Wiki content and if all goes well will be delivered shortly after the initial release is approved.

I will see if I can add some Tomcat specific topics into the chapter. 

I can understand Apple's approach however.  They went the open road approach and people got themselves into deep trouble and broke the server.  So they went the opposite route... lock it down and expose the top functions.  I feel that there should be a middle road.  Or, there should be an "Admin Config" boolean switch.  Let the admin choose to use the UI or go manually.  But make it so the two do not constantly fight each other.