Hello all,
I looked through the list archives and the jakarta docs, but didn't find
any info.
What changes, if any, do i have to make to my tomcat configuration if i want to upgrade my java SDK. I would like to do this because of the verisign root certificate expiration.
my versions:
j2sdk1.4.0_01 jakarta-tomcat-4.0.4 apache 1.3.20
dave
David,
First - for your specific versions, all you have to do is upgrade java. Once that works, you're in business - no changes to Tomcat. This is because the changes between JDK 1.4.0_01 and 1.4.2_01 should not have an impact on libraries used by Tomcat.
HOWEVER, the prudent action when upgrading any part of your enterprise system is to do the upgrade on some other system first, and get all the "kinks" out before you upgrade a production environment.
Just last week I went through the very same process, triggered by a bug in an older version of MySQL. The bug was identified and fixed in more recent versions, but I had not kept up-to-date. Worse, my development environment had become much newer (though not fully up-to-date) than my production environment... Time to upgrade both!
(NOTE: production is on a Sun server running Solaris, Devel is on a Win-XP box. MySQL, Tomcat and Java have versions for both, and my code can compile on one and run on the other with no problems.)
First, I upgraded the devel system. Since this system is not "mission critical" on a daily basis, and since it is the devel environment, it was a good candidate. It was also "almost current", so (hopefully) few changes. MySQL upgraded seamlessly (backup database, archive old version, unzip new version, restore database).
Java also upgraded seamlessly (uninstall old version, install new version). I got the newest version of what used to be called the "MM" JDBC jar file, and was fine.
Tomcat was more of a challenge. I was a few versions old, so "server.xml" had changed quite a bit. It had trouble initially finding my .keystore file, but I asked on this list and got that working. *this is why upgrading on a non-critical system is so essential. Had I started on the production machine, I would have been down for a week*. I also had to make some changes to the way the manager application worked (old vs. new), but once that was done I was fine.
The big problem with Tomcat upgrades is making sure it all runs. Most critical are the Java libraries (jar files) for special things. I had to be sure poi.jar (Java excell spreadsheet support), mysql.jar (the JDBC driver), activation.jar and mail.jar (the Java mail API) were all correct for both compile and Tomcat. I usually use a server upgrade as a time to upgrade and test newest versions of these support libraries as well. Once that was done, I tested the application on the devel machine. Once the tests all run, I simply repeat the process on the devel server.
I keep notes on what I do (or have done) when building / upgrading my server, so installing new versions is rarely a big problem.
Finally, you can upgrade "in parallel". That is, before you turn off or remove the old versions of this stuff, you can often install and run the new version to test that it works. Certainly I have been able to do that on my Sun box with MySQL. Java is tougher - I find it's just better to install the new version and go. Likewise, Tomcat's use of ports prevents parallel operation on the same port, but my server runs only SSL (port 443 with all other ports disabled), so the default install of Tomcat (port 8080) will work in parallel.
I hope this helps,
-Richard
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
