Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are in the process of moving our Java app servers from Resin to Tomcat running on RHEL4 - this is has been forced on us by changes adopted by our third party vendor. I want to make sure we are adopting best practice with regards to the management of Tomcat - can anyone make recommendations on best practice, tools, processes that we should look to adopt ?

share|improve this question
    
I don't understand your question. Resin uses config files, Tomcat uses config files. Whatever method you use for managing your configurations (Puppet, Chef, cfengine, etc.) would apply to both. Can I ask what, exactly, you're looking for best practices on...? – Andrew M. Nov 21 '10 at 4:21

You could install either LambdaProbe or it's fork PSIProbe which will give you a Manager view into the app/apps for monitoring, deployment and maintenance. Both are open source products and usage is very similar to the default Tomcat Manager app. Though LambdaProbe does not seem to be maintained any more.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.