![]() You can put up service maintenance pages, revise the web front end security, logging, etc. Using a separate instance of Apache gives you far more flexibility to decouple the application from the web front end services. I'd use binary AJP (port 8009) via the Apache mod_jk module, otherwise HTTP proxy. Next, setup up a 64 bit instance of Apache on your 2012 server, with appropriate frontend security, and proxy to the Tomcat on the loopback interface on the appropriate port. My recommendation would be to set up Tomcat to run on your 2012 server as required (32 or 64 bit), and configure it to listen only on the loopback interface to prevent any direct remote connections. ![]() Either way, you'll need to review your JVM options and test. Secondly, does your tomcat application run under a 32 bit or 64 bit JVM? Well behaved applications should cope with both, but I have met some that are 32 bit specific. ![]() From a security and flexibility perspective, I'd hope it's the latter, which is what I'd recommend as a 'migrate' path. Hmm, I doubt you can just 'move' your Tomcat application from 32 bit server 2008, to 64 bit server 2012.įirstly, you don't say if your users connect directly to Tomcat running as a web server, or if you are using an instance of Apache to provide the front end, and proxy to your Tomcat using mod_jk. Posted: Wed 02 Dec '20 23:17 Post subject: Would anybody know of the steps to take to move a working apache tomcat 7 web site from a 32bit windows server 2008 r2, to a new (not upgrade path) 64bt windows server 2012 installa. Posted: Wed 02 Dec '20 16:24 Post subject: migrate Apache Tomcat from server 2008 r2 to new server 2012 ![]() Topic: migrate Apache Tomcat from server 2008 r2 to new server 2012 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |