Advice on Tomcat use for staging servers

[BabyJeffy]

Hello again,

Currently our intranet has two servers (identical spec) with the same software loaded (and running) on it... Tomcat, Apache, mySQL, and the OS is MS Server 2003.

Everything is running fine... no complaints. The second server is currenty known as the Development Server - but I'm looking at how I can split the environment on the Development Server so that I can have a Staging Environment(for content people to upload content before it hits production - and for testing new code before it's installed live), and a Development Environment (where I can code new stuff without affecting the Staging Environment.

Me? I have no problems just creating a new webapp that acts as my "sand box to play in" (and creating a new database for use in the "sandbox&quot. Management would prefer I used another instance of Tomcat, Apache and MySQL rather than share.

Has anyone experienced the latter (new instances complete with all the port conflicts etc)? Wouldn't it be a better move to go for the first suggestion (as I had planned)? What is your opinion -- I'd appreciate some input before I commit to the transition.

Cheers,
Jeff

 

[byam]

During development, you may need to restart Tomcat to get some changes effective. If both development and staging are running on the same Tomcat instance, staging will be interupted if development need to be restarted.

Better to have separate instance of Tomcats,running on different port.