It seems that there is a problem with Oracle 12c drivers. I was having the same problem here on Websphere Liberty Profile using ojdbc7.jar driver. I've download 11.2.0.3's ojdbc6.jar driver from here, and suddenly, it started working. IBM BPM includes Java database connectivity (JDBC) drivers for DB2, DB2 for z/OS, Oracle, and Microsoft SQL Server databases. The versions of the JDBC drivers that are included in IBM BPM are determined by the levels of the corresponding database products that were supported by the particular release of IBM BPM.
- Websphere Sql Server Jdbc Driver For Macromedia
- Sql Server Jdbc Connection String
- Microsoft Sql Server Jdbc Driver
- Install Sql Server Jdbc Driver
IBM WebSphere Connect JDBC and SequeLink JDBC Drivers Abstract This page provides updates for JDBC drivers shipped with WebSphere Application Server to enable connectivy to the Microsoft SQL Server database. Start WebSphere Application Server Community Edition before you install a JDBC driver on WebSphere Application Server Community Edition. Use the Administrative Console of WebSphere Application Server Community Edition to install a JDBC driver. Frequently Asked Questions (FAQ) for JDBC Driver.; 6 minutes to read Contributors. All; In this article. Download JDBC Driver. This page provides answers to frequently asked questions about the Microsoft JDBC Driver for SQL Server. In more detail, when Microsoft SQL Server JDBC Driver 2.0 passes 'SSLv3' as the string argument, the Sun JSSE provider returns an SSLContext instance that supports both the SSLv3 protocol and the TLS protocol.
This page provides answers to frequently asked questions about the Microsoft JDBC Driver for SQL Server.
Frequently asked questions
How can I help improve the JDBC Driver?
The JDBC Driver is open-source and the source code can be found on GitHub. You can help improve the driver by filing issues and contributing to the code base.
Which versions of SQL Server and Java do the driver support?
See the Microsoft JDBC Driver for SQL Server support matrix page for details.
What is the difference between the JDBC driver packages available on the Microsoft Download Center and the JDBC driver available on GitHub?
The JDBC driver files available on the GitHub repository for the Microsoft JDBC driver are the core of the JDBC driver and are under the open-source license listed in the repository. The driver packages on the Microsoft Download Center include additional libraries for Windows-integrated authentication and enabling XA transactions with the JDBC driver. Those additional libraries are under the license included with the downloadable package.
What should I know when upgrading my driver?The Microsoft JDBC Driver 7.4 supports the JDBC 4.2, and 4.3 (partially) specifications and includes three JAR class libraries in the installation package as follows:
| JAR | JDBC Specification | JDK Version |
|---|---|---|
| mssql-jdbc-7.4.1.jre12.jar | JDBC 4.3 (partially), and 4.2 | JDK 12.0 |
| mssql-jdbc-7.4.1.jre11.jar | JDBC 4.3 (partially), and 4.2 | JDK 11.0 |
| mssql-jdbc-7.4.1.jre8.jar | JDBC 4.2 | JDK 8.0 |
The Microsoft JDBC Driver 7.2 supports the JDBC 4.2, and 4.3 (partially) specifications and includes two JAR class libraries in the installation package as follows:
| JAR | JDBC Specification | JDK Version |
|---|---|---|
| mssql-jdbc-7.2.2.jre11.jar | JDBC 4.3 (partially), and 4.2 | JDK 11.0 |
| mssql-jdbc-7.2.2.jre8.jar | JDBC 4.2 | JDK 8.0 |
The Microsoft JDBC Driver 7.0 supports the JDBC 4.2, and 4.3 (partially) specifications and includes two JAR class libraries in the installation package as follows:
| JAR | JDBC Specification | JDK Version |
|---|---|---|
| mssql-jdbc-7.0.0.jre10.jar | JDBC 4.3 (partially), and 4.2 | JDK 10.0 |
| mssql-jdbc-7.0.0.jre8.jar | JDBC 4.2 | JDK 8.0 |
The Microsoft JDBC Driver 6.4 supports the JDBC 4.1, 4.2, and 4.3 (partially) specifications and includes three JAR class libraries in the installation package as follows:
| JAR | JDBC Specification | JDK Version |
|---|---|---|
| mssql-jdbc-6.4.0.jre9.jar | JDBC 4.3 (partially), 4.2, and 4.1 | JDK 9.0 |
| mssql-jdbc-6.4.0.jre8.jar | JDBC 4.2, and 4.1 | JDK 8.0 |
| mssql-jdbc-6.4.0.jre7.jar | JDBC 4.1 | JDK 7.0 |
The Microsoft JDBC Driver 6.2 supports the JDBC 4.0, 4.1, and 4.2 specifications and includes two JAR class libraries in the installation package as follows:
| JAR | JDBC Specification | JDK Version |
|---|---|---|
| mssql-jdbc-6.2.2.jre8.jar | JDBC 4.2, 4.1, and 4.0 | JDK 8.0 |
| mssql-jdbc-6.2.2.jre7.jar | JDBC 4.1 and 4.0 | JDK 7.0 |
The Microsoft JDBC Drivers 6.0 and 4.2 for SQL Server supports JDBC 4.0, 4.1, and 4.2 specifications and include two JAR class libraries in the installation package as follows:
Websphere Sql Server Jdbc Driver For Macromedia
Sql Server Jdbc Connection String
| JAR | JDBC Specification | JDK Version |
|---|---|---|
| sqljdbc42.jar | JDBC 4.2, 4.1, and 4.0 | JDK 8.0 |
| sqljdbc41.jar | JDBC 4.1 and 4.0 | JDK 7.0 |
The Microsoft JDBC Driver 4.1 for SQL Server supports the JDBC 4.0 specification and includes one JAR class library in the installation package as follows:
| JAR | JDBC Specification | JDK Version |
|---|---|---|
| sqljdbc41.jar | JDBC 4.0 | JDK 7.0 and 6.0 |
Do I need to make any code changes in my application to use the latest driver with my existing SQL Server version?
In general, the driver is designed to be backward compatible so that you do not need to change your existing applications when upgrading the driver. In the event that a new driver version introduces a breaking change, the Release Notes for the JDBC Driver section provides clear details on the change and the impact to existing applications. In addition, you can review the release notes included with the driver for a list of bugs fixed in that release and known issues.
How much does the driver cost?
The Microsoft JDBC Driver for SQL Server is available at no additional charge.
Can I redistribute the driver?The JDBC Drivers 4.1, 4.2, 6.0, 6.2, 6.4, and 7.0 are redistributable. Review the 'Distributable Code' clause in the license agreements.
Can I use the driver to access Microsoft SQL Server from a Linux computer?Yes! You can use the driver to access SQL Server from Linux, Unix, and other non-Windows platforms. For more information, see Microsoft JDBC Driver for SQL Server Support Matrix.
Does the driver support Secure Sockets Layer (SSL) encryption?Starting with version 1.2, the driver supports Secure Sockets Layer (SSL) encryption. For more information, see Using SSL Encryption.
Which authentication types are supported by the Microsoft JDBC Driver for SQL Server?
The table below lists available authentication options. A pure Java Kerberos authentication is available starting with the 4.0 release of the driver.
| Platform | Authentication |
| Non-Windows | Pure Java Kerberos |
| Non-Windows | SQL Server |
| Non-Windows | Azure Active Directory Authentication |
| Windows | Pure Java Kerberos |
| Windows | SQL Server |
| Windows | Kerberos with NTLM backup |
| Windows | NTLM |
| Windows | Azure Active Directory Authentication |
Does the driver support Internet Protocol version 6 (IPv6) addresses?
Yes. The driver supports the use of IPv6 addresses. Use the connection properties collection and the serverName connection string property. For more information, see Building the Connection URL.
Microsoft Sql Server Jdbc Driver
What is adaptive buffering?
Adaptive buffering is introduced starting with Microsoft SQL Server 2005 JDBC Driver version 1.2. It is designed to retrieve any kind of large-value data without the overhead of server cursors. The adaptive buffering feature of the Microsoft SQL Server JDBC Driver provides a connection string property, responseBuffering, which can be set to 'adaptive' or 'full'. In the version 1.2 release, the buffering mode is 'full' by default and the application must set the adaptive buffering mode explicitly. Starting with the JDBC Driver version 2.0, the default behavior of the driver is 'adaptive'. Thus, your application does not have to request the adaptive behavior explicitly to get the adaptive buffering behavior. For more information, see Using Adaptive Buffering and the blog What is adaptive response buffering and why should I use it?.
Does the driver support connection pooling?
The driver provides support for Java Platform, Enterprise Edition 5 (Java EE 5) connection pooling. The driver implements the JDBC 3.0 required interfaces to enable the driver to participate in any connection-pooling implementation that is provided by middleware application server vendors. The driver participates in pooled connections in these environments. For more information, see Using Connection Pooling. The driver does not provide its own pooling implementation, but rather it relies on third-party Java application servers.
Is support available for the driver?
Several support options are available. You may post your question or issue to our GitHub repository which is monitored by Microsoft. Forums are monitored by Microsoft, MVPs, and the community. You may also contact Microsoft Customer Support. The development team may ask you to reproduce the issue outside any third-party application servers. If the issue cannot be reproduced outside the hosting Java container environment, you will need to involve the related third-party so that the team can continue to assist you. The team may also ask you to reproduce your issue on an operating system such as Windows so the problem can be best supported.
Is the driver certified for use with any third-party application servers?The driver has been tested against various application servers including IBM WebSphere and SAP Netweaver.
How do I enable tracing?
The driver supports the use of tracing (or logging) to help resolve issues and problems with the JDBC Driver when it is used in your application. To enable the use of client-side JAR tracing, the JDBC Driver uses the logging APIs in java.util.logging. For more information, see Tracing Driver Operation. For server-side XA tracing, see Data Access Tracing in SQL Server.
Where can I download older versions of the driver such as the SQL Server 2000 JDBC driver, 2005 driver, 1.0, 1.1, or 1.2 driver?
These driver versions are not available for download as they are no longer supported. We are continually improving the Java connectivity support. As such, we highly recommend you work with the latest version of Microsoft JDBC driver.
I am using JRE 1.4. Which driver is compatible with JRE 1.4?
For customers who are using SAP products and require JRE 1.4 support, you may contact SAPService Marketplace to obtain the 1.2 Microsoft JDBC driver.
Can the driver communicate using FIPS validated algorithms?
The Microsoft JDBC Driver does not contain any cryptographic algorithms. If a customer leverages operating system, application, and JVM algorithms that are deemed acceptable by Federal Information Processing Standards (FIPS) and configures the driver to use those algorithms then the driver uses only the designated algorithms for communication.
See also
Question & Answer
Install Sql Server Jdbc Driver
Question
How do I configure messaging engines to use a SQL Server data store?
Answer
The information below provides details to help you configure a SQL Server data source a messaging engine can use for its data store.
Since each messaging engine requires unique databases, ensure you have an empty database created for each additional messaging engine. The database used in the example below is the maximo database. The owner specified for this database (maximo) will already have the necessary privileges to create tables.
Preparing the SQL Server Driver
For each node in your cluster, you will need to place a copy of the SQL Server driver jar file. The jar file must be located in the same place on each hosts. There are a few ways to tell WebSphere how to reference the jar file. For this example, we will use an absolute path value.
1. Ensure a folder exists on each node that has the identical path and that the WebSphere service user has access to this location. For example, the following location typically exists:
c:IBMWebSphereAppServerlib
2. Navigate to the Maximo folder that contains a copy of the SQL Server driver jar. This is typically found in the following location with the name shown below:
c:IBMSMPmaximoapplicationsmaximolibsqljdbc.jar
3. Copy this file to the identical location on each node as noted in step one.
4. Synchronize the changes, then restart the deployment manager and node agents.
Creating the SQL Server Data Source Provider
1. Log in to the WebSphere console, and from the left pane, select Resources/JDBC Providers
2. On the JDBC providers screen, set the scope to be your cell
3. Click the 'new' button
4. Select the following values from the dropdown boxes presented:
Database Type: SQL Server
Provider Type: Microsoft SQL Server JDBC Driver
Implementation Type: XA data source
5. Click next
6. In the Class Path text box, enter the path and file name of your SQL Server driver jar:
c:IBMWebSphereAppServerlibsqljdbc.jar
7. In the name field accept the default and click next.
8. Click 'apply' and save and synchronize with other nodes.
Creating the SQL Server Data Source
1. Navigate to your JDBC provider created in the previous steps.
2. Click the link on the right side of the screen called 'data sources'.
3. Click the 'new' button.
4. In the Data source name field enter a name for your data source. For example:
sqlxads
5. In the JNDI name field, enter the value that the messaging engine will use to reference this data source. For example:
jdbc/sqlxads
6. Click next.
7. Enter the Database name, Port number, and Server name for your Maximo SQL Server database. You can find this information in the maximo.properties file.
8. Click next. The authentication data will be entered later. Click next again, then Finish.
9. Click apply, save and synchronize the changes.
Creating a J2C Authentication Alias
1. Navigate to your jdbc data source called sqlxads created in the previous steps.
2. On the right side of the screen, under Related Items, click the link for JAAS - J2C authentication data.
3. Click the 'new' button.
4. In the alias field, enter a value you would like to use:
i.e. maximo
5. Enter the username and password used to connect to the database:
i.e. maximo/maximo
6. Click apply and save and synchronize the changes.
7. Now you will need to navigate back to your data source called sqlxads
8. Under the 'Security Settings' section, select your newly created authentication alias from the following two dropdown boxes:
Authentication Alias for XA Recovery
Component-managed Authentication alias
9. Click apply and save and synchronize the changes.
10. Restart all application servers to ensure the store tables are created in the database and to pick up the driver changes.
11. Test the connection.
Once the test has succeeded, you can set this data source as the data store location for your messaging engines when adding bus members. When entering the data store on the message engine, the schema name to be entered is 'dbo' for SQL Server.