Well, there could be a few things going on here.
I'm guessing you get that error when the application runs?
One thing you can do in your code is just create an instance of the driver class:
COM.ibm.db2.jdbc.app.DB2Driver driver = new COM.ibm.db2.jdbc.app.DB2Driver();
Or whatever the constructor is. That will tell you if you're linking to the driver file at design time.
But this may be a runtime error? Your design time environment and runtime environment are two different things.
You may actually have to package the db2java.zip file right in your applicaiton. Certainly try that to get things working. Put it in the root of the EAR or the lib of the war file if you're creating an
J2EE app. Otherwise, import the jar file from the directory to bring it into the Java project.
The Hiberntate Configuration object is using this file, so when you go:
Configuration configuration = new Configuration();
it's looking for the drivers. The classpath used by WebSphere to link to support a connection pool might not be accessible to your application code at runtime.
Looks like you need to repackage.
Post back and let us know how you're doing.
-Cameron McKenzie