Hi,
I partially agree with RMG.
as long as the driver(s) do not relying on a native lib, it is fine to have them under code/jars and just reload the package.
Remember to define a dependency in those packages relying on the WmJDBCAdapter package to get them reloaded and the connections restarted properly when the JDBC-Adapter reloads.
For those with native lib part the jar needs to go under code/jars/static and the native lib in the IntegrationServer/instances/default/lib directory. In this case shutting down and restarting the IS is required to get the native lib loaded properly.
It is fine having one jar (hopefully the latest) for each database type being used in the code/jars directory.
What you should avoid is having multiple versions for one database type in parallel as ths might be causing ClassLoading issues or the wrong version gets picked first.
Regards,
Holger
#webMethods#Adapters-and-E-Standards#Integration-Server-and-ESB