I am trying to run the WebSphere Test Environment in VAJ to run a servlet. The problem: I am unable to start the...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
persistent server. It gives me a error that specified driver not found. I am connecting to DB2 using COM.ibm.db2.jdbc.app.DB2Driver.
It would be nice to use the local DB2 UDB support for running the WebSphere Test Environment (WTE) name server BUT that can be VERY difficult.Turns out, VisualAge and WebSphere are both VERY picky about the correct version of the JDBC driver. I have only been able to get DB2 to work at V6R1 with fix pack 4 applied.
Nothing else worked and no one at IBM support could verify another version would work to run the name server.
The EASY way to get the WebSphere Test Environment (WTE ) working is to use the instant DB database included with VisualAge. It works perfectly if you install it and use it as the default name server.
I do use DB2 UDB V6 or V7 as my actual database server for both JDBC connections and data sources fine in WTE. The only hitch: I can't use it as the name server.
Be sure to add the db2java.zip file to the VisualAge workspace classpath ( workbench | Windows | Options | Resources ).
In my case, the entry I add is based on where I have DB2 installed on my system:
Remember DB2 UDB works fine with WTE EXCEPT as a name server!
Related Q&A from Jim Mason
Java to Excel with the AS400 may be attractive, but if you have complex VBA macros in Excel, the JDBCODBC bridge will not work well for you. A better...continue reading
There are a couple of options for accessing AS/400 data, from the old way using Client Access ODBC drivers, to Java, to a new application from Groovy.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.