In previous version to WAS 7.0 you always had to create a new WebSphere Variable for the JDBC connection between WAS & MSSQL:
- MSSQLSERVER_JDBC_DRIVER_PATH
However now in WAS 7.0 IBM have kindly created a default Websphere Variable for you:
- MICROSOFT_JDBC_DRIVER_PATH
This initially threw me as by default I created the MSSQLSERVER_JDBC_DRIVER_PATH that I was accustomed to at the node level scope but then experienced problems trying to test the connection getting the following error message:
“Libraries not found in the following: /sqljdbc.jar”
Thus WAS was picking up the new variable provided for you in WAS 7.0 over the old one.
One to watch out for. Hope this helps someone.
