This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SQL Server 2000 and WSAD 5.1 issues

 
Jose Velarde
Ranch Hand
Posts: 78
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using the Websphere Connect JDBC driver for MS SQL 2000. When I try to register this driver using this:

Class.forName("com.ibm.websphere.jdbc.sqlserver.SQLServerDriver")

I get this error message:

java.lang.ClassNotFoundException

I've correctly set the CLASSPATH in the Java Build Path of WSAD to point to the required jars. Am i missing something?

Let me add that I was able to establish a connection to the database using the Data View of WSAD.
 
Jose Velarde
Ranch Hand
Posts: 78
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok I sort of had a work around for this issue. I extracted the jars and manually put it in my EAR lib folder. I then added these jars in the classpath and then add it in the manifest file using the Java JAR Dependencies. It worked!

Referencing the jars using the Add Variable seems to be not working at runtime. I noticed that when I do this the jars do not go to the manifest file.

Is there another way to solve this? The architect's preference is to not put any jars on the EAR lib folder. Is there a way for WSAD to recognize the SQL Server driver at runtime?
[ May 15, 2005: Message edited by: Jose Velarde ]
 
Jose Velarde
Ranch Hand
Posts: 78
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I also get this error message when I start creating a connection.

This driver is locked for use with embedded applications.

I got the following from the IBM Information center:

Use the proper DataStoreHelper class to configure data sources for the Connect JDBC driver

If you use the WebSphere Embedded Connect JDBC driver for Microsoft SQL Server, you must use the proper DataStoreHelper class. If you use an incorrect DataStoreHelper class, either of the following exceptions might occur:

java.sql.SQLException: [IBM][SQLServer JDBC Driver]This driver is locked for use with embedded applications.
at com.ibm.websphere.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.ibm.websphere.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.ibm.websphere.jdbc.base.BaseConnection.validatedUnlocked(Unknown Source)

java.sql.SQLException: [IBM][SQLServer JDBC Driver]?}???h???C?o???A???A?v???P?[?V???g?p???b?N???E?B
at com.ibm.websphere.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.ibm.websphere.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.ibm.websphere.jdbc.base.BaseConnection.validatedUnlocked(Unknown Source)
The correct DataStoreHelper class for the WebSphere Embedded Connect JDBC driver for Microsoft SQL Server and WebSphere Embedded Connect JDBC driver for Microsoft SQL Server (XA) providers is com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper.



How do I set this up in my WSAD environment?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic