Move Tomcat, MySQL and jre1.6.0 from Windows XP to Linux/W2008

I want to move a web site to new more powerful hardware from a workstation running Windows XP Pro Sp3 x32 with Tomcat 5.5.20, MySQL 5.4.20, and jre1.6.0.

Will this be a painful process if I move it to a Linux server? I have prepared several operating systems for testing. I am a long time Windows administrator and a linux newbie. When I finish, a web developer will take over troubleshooting.

I have installed four(4) x86_64 evaluation edition operating systems (multiboot) on the new server to test the website migration: Windows 2008 Server Std Edition with Hyper-V, Red Hat Enterprise Server 5.4, SUSE Linux Enterprise Server 11, and openSUSE 11.1. I have installed XEN on Red Hat and may do the same with the SUSE's. I thought I would perform testing on virtual machines.

In a clutch, I could install XP Pro Sp3 as a guest virtual machine. I plan to test using virtual machines to avoid reinstallation of the host OS during botched testing.

Thanks,

Rich

Migrating to linux is not that much pain full.

but you can try other options also

one of the possible solution is

install 3-4 instances of tomcat(as windows service) and use clustering with load balancing you will see a huge performance boost up.

you can go through the link...

http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html

Hi,

Moving to Linux won't pose a problem, as long as you don't use that daft Debian/Ubuntu Tomcat apt-package, but a real Tomcat from Apache.org.

You'll probably have a lot more troubles fighting Xen than you will with the Java stuff. And I'm saying this as someone who's running several Xen servers in production right now.

Tomcat can be installed as easily as zipping everything up, copying it to the target machine (regardless of source/destination OS's) and unzipping. You can get more involved if you want to hook it into OS system control services, but Tomcat itself doesn't need any of that. The only mods required would be if you have absolute pathnames in application configurations. Obviously there's no "C:\Documents and Settings" directory on Linux, though I have been known to create a C:\usr on Windows occasionally for convenience reasons.

For MySQL, the simplest thing to do for starters is to leave the database connections pointing to the original database server (assuming it's not LOCALHOST). You might have to adjust grant access and firewall rules, though. Since MySQL was originally a Unix-platform product and it comes with virtually all Linux distros as part of the core OS install package list, it's actually easier to get a MySQL server up and running on Linux than on Windows.