If your Virtual DataPort server is running, restart the server so the new driver is added to the classpath. For Denodo 6 and older versions, copy the 'mssql-jdbc-x.x.jar’ file to DENODO_HOME/extensions/thirdparty/lib. For Denodo 7 and newer versions, skip steps 3 and 6.This option has different behaviors depending on the driver version used: Using Windows credentials (writing the credentials in the data source dialog).A dll is needed and the steps can be found below Reading OS Credentials without the need of adding login/password in Denodo’s JDBC Data Source dialog.There are a different methods to authenticate into SQLServer using Windows Credentials: Virtual DataPort will use the credentials of the user that started the VDP server. Jdbc:jtds:sqlserver://host:port/database useNTLMv2=true domain=domain Create a new JDBC data source in the Virtual DataPort Administration Tool or the Web Design Studio.Copy the file under /extensions/thirdparty/dll.For instance, for a 64-bit operating system, extract the file under 圆4/SSO. Extract the file that matches the target architecture. Extract from the distribution jtds-xxx-dist.zip the file ntlmauth.dll.Download the latest jTDS driver version from here.Content Using the jTDS JDBC driverīefore creating a data source to a MS SQL Server database from Virtual DataPort using the jTDS driver and Windows Authentication follow these steps:
The configuration with the jTDS and the Microsoft drivers will be explained. When using this approach, the credentials from the user that started the Denodo VDP service will be the ones used to access the SQL Server data source. These steps are only needed when we do not want to use a login and a password in our SQL Server JDBC data source and we want to obtain those credentials from the operating system. This document describes how to use Windows Authentication to access SQL Server using a JDBC data source.
0 kommentar(er)
