Udostępnij za pośrednictwem

IBM WebSphere 6.1 now supports SQL Server 2005 JDBC driver v1.2

  • Artykuł

Many of you have asked us before, "Is the Microsoft SQL Server JDBC driver supported by IBM WebSphere?". Now, we have the answer. In collaboration with the IBM WebSphere team, the SQL Server JDBC team is happy to announce starting with IBM WebSphere 6.1 update 6.1.0.15, our SQL Server JDBC driver v1.2 is officially Tested with IBM® WebSphere® Application Server Software and is listed on IBM website's list of supported JDBC drivers for WebSphere 6.1.

Jimmy Wu
SQL Server JDBC Team

Comments

  • Anonymous
    July 28, 2008
    Any documentation on how to setup this JDBC driver with WebSphere 6.1? I've been googling like mad, and I can't find anything except this blog. I'm not sure what to put in for DataStoreHelper, and when I pick the default, it complains about being incompatible with the ConnectionPoolDataSource.

  • Anonymous
    July 28, 2008
    Are you using the WebSphere 6.1 Fixpack which enables the use of our driver? http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=D400&uid=swg24018265&loc=en_US&cs=UTF-8&lang=en

  • Anonymous
    July 28, 2008
    The comment has been removed

  • Anonymous
    August 09, 2008
    Websphere works very well with DB2 :) You dont need Websphere application server v6.1 with fixpack 15 for "Microsoft SQL Server 2005 JDBC Driver" to work. For older systems, download the newest drivers from microsoft and create a new user defined jdbc provider. Use: com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource as the implementation and com.ibm.websphere.rsadapter.MSSQLDataStoreHelper as data store helper in your datasource settings. You can also use: com.ibm.websphere.rsadapter.GenericDataStoreHelper but it will give you a warning each time you use it. Fix pack 15 makes this setup easier and uses com.ibm.websphere.rsadapter.MicrosoftSQLServerDataStoreHelper instead. Also checkout: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rdat_minreqmssql.html

  • Anonymous
    August 09, 2008
    Do not copy sqljdbc.jar to websphere lib directory. Install the microsoft sql jdbc driver files under program files. Then create a websphere variable like ${MICROSOFT_JDBC_DRIVER_PATH} that points to this directory. (usually C:Program FilesMicrosoft SQL Server 2005 JDBC Driversqljdbc_1.2enu) Include ${MICROSOFT_JDBC_DRIVER_PATH}/sqljdbc.jar in classpath while creating your jdbc provider. This way you dont have to restart websphere.

  • Anonymous
    October 22, 2008
    How to specify the failover partner for JDBC driver? Is it done using 6.1 console or is it to be done while making the connection?

  • Anonymous
    March 12, 2009
    The comment has been removed

  • Anonymous
    May 27, 2009
    In this step: f. you click finish, but you're not done. Go back into this datasource and at the bottom of the page you need to configure the database name, server name, and port. Then click apply, save, and test the datasource (may need to stop/start Web$phere). There's no field to configure database name, server name, and port. Any sugestions?

  • Anonymous
    June 15, 2009
    I need the Microsoft 2.0 JDBC driver to work with WebSphere 7.0.  I can get it to work, but IBM doesn't list the 2.0 driver on its prerequisites page (at http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27012421).  I posted this same question on the MSDN board at http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/3be5c043-7084-4f5f-95e0-4fe9ffca312f.  Are you working with IBM on this?  How does certification occur?

  • Anonymous
    July 02, 2009
    Hey Wes, Sorry for taking a little while to get back to you. When IBM releases a major version they will certify our latest JDBC version. That's why JDBC 1.2 is certified for WAS 7.0. After that, IBM just claims forward support for later released versions. Thus, since WAS 7.0 was already released and already certified for 1.2, they offer support 2.0 and not certification. They do not believe there are major changes between 1.2 and 2.0. --Tres London [SQL Server]

  • Anonymous
    July 29, 2009
    thank you Guys for your helping hand

  • Anonymous
    October 18, 2009
    /* In this step: f. you click finish, but you're not done. Go back into this datasource and at the bottom of the page you need to configure the database name, server name, and port. Then click apply, save, and test the datasource (may need to stop/start Web$phere). There's no field to configure database name, server name, and port. */ I have similar problem. Any updates on this issue?

  • Anonymous
    November 10, 2009
    You need to add them as custom properties: databaseName: java.lang.String serverName: java.lang.String portNumber: java.lang.Integer Think this should work.

  • Anonymous
    November 25, 2009
    Any idea when/if IBM will add support for SQLServer to Websphere standalone ( see http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp ). I tried this with my MQ7 + JDBC2.0 install and it did not seem to work. Basically I used the qMgr = new MQQueueManager("QM1")  Connection con = qMgr.getJDBCConnection( xads );  qMgr.begin() pattern passing in a SQLServerXADataSource.

  • Anonymous
    February 15, 2010
    Dear team, I am very happy the way you guys are explain.Alos I need one help from your side. I am facing one problem. When I am connecting SQLSERVER 2000 my application is calling store procedure which runing fine and when needed i am getting SQLException in java code which i am easily dispaly in the view page but when I am coonecting SQLSERVER 2008(64) bit it is also running fine as it should behave but when the system needs to throw exception it is not throwing exception when calling the same store procedure in side java code, so that i am not able to display the error mesage in view page. Please suggest me what i will do. Thanks In advance

  • Anonymous
    March 14, 2010
    I want to configure JDBC provider in websphere 6.1 to connect to SQL server 2008. Could you please let me know what JDBC provider i have to use. And i'm using WAS 64 bit and SQL server 64bit versions.

  • Anonymous
    April 07, 2010
    We have Websphere 6.0 with SQLServer2000, and we have some specific questions: 1.- What version of the Microsoft JDBC driver you recommended, independient of the Application Server? 2.- The version that you recommendend, respect the version Microsoft JDBC 1.2, includes fixes for bugs thats mean WebSphere. 3.- For WebSphere 6.0 what is the recommended version of Microsoft JDBC driver? thanks in advance

  • Anonymous
    June 02, 2010
    This is great. I struggled to setup the jdbc connection between RAD7 and SQL 2005  for days. The post of 'AdvisorTechnical 28 Jul 2008 9:00 PM' within this blog resolved my problem within 5 minutes. Tons of thanks!!

  • Anonymous
    August 25, 2011
    What if the existing jdbc driver is 2x and needs to be updated to 3x..

  • Anonymous
    November 29, 2011
    @Asking - The Microsoft JDBC Driver 3.0 also works with IBM Websphere.