MSSQL JDBC driver integration

[#1]

I am trying to deploy the MSSQL JDBC (mssql-jdbc-9.4.1.jre11) driver in CPI and I am getting the following error: Deploy artifact failed: (deployJdbcDriver)Failed to deploy jdbc driver null for tenant,

even already tried the solution of changing versions exmaple: 12,8,11, and nothing worked for changing the versions

[Ryan-Crosby · Accepted solution]

You must use one of the approved drivers from this page - https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/configure-jdbc-drivers

Regards,

Ryan Crosby

[AGA82 · Accepted solution]

Hi Ryan - We are facing a similar issue while upgrading the Microsoft JDBC driver in SAP Cloud Integration. We are currently using `mssql-jdbc-8.4.1.jre8`, which works correctly. When we replace it with the approved `mssql-jdbc-12.4.0.jre8` driver, the JDBC Data Source fails with a `CredentialStoreCredentialNotFoundException` for credential `DBCON`. The credential `DBCON` is present in the tenant and was working correctly with the 8.4.1 driver. If we revert to 8.4.1, the same JDBC Data Source works again. Could someone please clarify: 1. After uploading/replacing the JDBC driver, do the existing JDBC Data Sources need to be recreated or redeployed, or should they continue to work without any changes? 2. Does upgrading from 8.4.1 to 12.4.0 provide backward compatibility with existing SQL Server versions supported by 8.4.1? In other words, can we use `mssql-jdbc-12.4.0.jre8` as a replacement for 8.4.1 for our existing SQL Server connections without requiring changes on the SQL Server side? 3. Are there any known compatibility considerations or configuration changes when moving from `mssql-jdbc-8.4.1.jre8` to `mssql-jdbc-12.4.0.jre8` in SAP Cloud Integration? Any guidance on the recommended upgrade procedure would be appreciated.

[Ryan-Crosby · Accepted solution]

@AGA82 my guess is that you would want to re-establish your JDBC Data Source connectivity once the new driver is deployed because in effect it's a different piece of software. The only thing that should be required is re-entering the password and then I imagine it would work without problems.

[AGA82 · Accepted solution]

Hi Ryan - Thank you for your guidance as always. Thanks Ryan. That makes sense. Just to clarify one point, when we deploy `mssql-jdbc-12.4.0.jre8`, the existing JDBC Data Source fails specifically while retrieving the credential, with the following error: `CredentialStoreCredentialNotFoundException: Credential with the specified name is not available in the credential store` The credential `DBCON` definitely exists and works correctly when we revert to `mssql-jdbc-8.4.1.jre8`. When you say "re-establish the JDBC Data Source connectivity", do you mean that we should simply edit the existing JDBC Data Source and re-enter/save the password for `DBCON`, rather than delete and recreate the Data Source? Also, is this re-entry of the password expected whenever the JDBC driver is upgraded to a different version, or is it specific to this particular driver change? Will the latest version 12.4.0 support all SQL server versions? is there any KBA for this? Thanks.

[Ryan-Crosby · Accepted solution]

@AGA82 yes I would start with simply editing the existing data source, and resort to deletion and recreation if that does not work. My guess is the exception is triggered because the credentials are stored against the version of the JDBC driver used when the data source is created.

[AGA82 · Accepted solution]

Thanks Ryan. I will try this. Somehow the error was pointing to the JDBC Data Source name while saying credential not found.