Hi, our DBA has asked if we can move our jdbc jar files into a centralised (per server) location rather than under tomcat\lib. He feels from his DBA perspective it will be easier to manage versions.
Every bit of Tomcat documentation I've found states the jar file can either go under the Tomcat lib or the web app's lib folder but I've not found anything to suggest the ojdbc6.jar can reside elsewhere and classpath pointer make it usable (eg Oracle installation folder).
Oracle's documentation states tomcat\lib at http://www.oracle.com/technetwork/artic ... 55431.html (old document though)
Tomcat's documentation is the same but unfortunately states Oracle 8i, 9i and 10g, all of which are out of support http://tomcat.apache.org/tomcat-7.0-doc ... howto.html
As you may guess our DBA is somewhat stuck on the idea so I'd like to find a more up to date document to show that we have it in the best location and get Ebase / other user feedback.
Out of interest does anyone run Ebase where Oracle jdbc files reside outside of Tomcat?
I've got Beyond Compare which is used to prove the right version is being used. From an application perspective it is felt that the comparison is adequate.
Thanks,
Oracle connectivity
Moderators: Jon, Steve, Ian, Dave
-
- Moderator
- Posts: 1342
- Joined: Wed Sep 12, 2007 12:49 pm
Steve,
We've not been asked this question before, most people seem happy to put database driver jars into tomcat/lib. Ebase is a client to Oracle so it doesn't seem unreasonable to install some Oracle client libraries into Tomcat. Also, there is no need to use the same version of the driver jar file as the Oracle server: our normal recommendation is to always install the latest one into Tomcat - see Oracle doc.
Having said all that, I think it is possible to extend Tomcat's class loaders to include external libraries. Best suggestion I've seen is to use shared.loader or common.loader properties as per http://stackoverflow.com/questions/1300 ... -classpath.
Regards
Jon
We've not been asked this question before, most people seem happy to put database driver jars into tomcat/lib. Ebase is a client to Oracle so it doesn't seem unreasonable to install some Oracle client libraries into Tomcat. Also, there is no need to use the same version of the driver jar file as the Oracle server: our normal recommendation is to always install the latest one into Tomcat - see Oracle doc.
Having said all that, I think it is possible to extend Tomcat's class loaders to include external libraries. Best suggestion I've seen is to use shared.loader or common.loader properties as per http://stackoverflow.com/questions/1300 ... -classpath.
Regards
Jon
0 x
Who is online
Users browsing this forum: No registered users and 9 guests