Printable View
Friends,
Recently we have upgraded the Application server from Websphere v5.1 to v6.1.
WAS(Websphere Application Server) v5.1 was using DB2 Legacy JDBC Driver. Now, it is depricated in v6.1.
Asap now, we continue using the Legacy driver in v6.1 also. But soon, we need to upgrade the JDBC driver to DB2 Univer JDBC driver.
Does anyone know that, the changes need to be done on the application side to upgrade the JDBC Driver?
The help will be highly appriciated. Thanks in advance.
- SANSSAN.
It would seem to me that changing the driver should be transparent to your deployed application unless you are directly referencing classes in the driver jar from your application code. Have you tried using the new driver? It should take less than 5 minutes to configure.
Our web application was using the Connection pooling for the DB Retrival.
When we change the driver, it required the following change.
We had an DB2 column as a CHARACTAR type and Legacy driver was able to go find with the following statement on java code.
preparedStatement.setBytes(index, curString.getBytes());
But, for the same code, we got Illegal Conversion exception on the Universal Driver. This is because, Universal driver implicitly convert in to the Server data type before send to the DB2 server.
We have modified this to setString(), now its working fine.
Just wanted to share with you all.
Thanks all for the support.