This document captures the instructions for configuring connectivity to SQL Server in a Microsoft Enterprise deployment.
The preferred method for connecting to a SQL Server database is via JDBC using the JDBC Query, JDBC Store and JDBC Execute nodes. Although ODBC will work, JDBC is preferred over ODBC as ODBC will require a system administrator to create a DSN for each database connection thus increasing the maintenance required to administer the deployment.
In order for the JDBC nodes to run, the following steps must be completed.
The actual JAR file may vary for very old versions or very recent versions of SQL Server.
- Navigate to Microsoft’s JDBC Driver download
- Scroll down to the driver download section
- Choosing a version higher than 4.1 will ensure you have the necessary file downloaded for our software.
- Be sure to scroll down to the correct version, as you'll likely only see up to v4.0 by default
- Be sure to note the location to which you extract the files.
- Files of type tar.GZ may be opened with freely available third party tools such as 7-zip.
- Navigate to the extracted location and copy the sqljdbc41.jar file
- Place the jar file into the <LAE Install>/lib/java/ext directory.
Configuring the JDBC Nodes
- Configure the DbURL.
- Configure the DbDriver
Windows Authentication Mode
In some situations, a client may require Windows Authentication to gain access to the database using predefined credentials. In addition to the steps captured in the section “JDBC Connectivity”, 2 additional steps must be completed to complete the setup. Follow the steps below:
- Extract sqljdbc_auth.dll from the previously retrieved zip file in: \enu\auth\x64
- Place the file in: <Install Directory>/jre/jre/bin
- Add the additional parameter “integratedSecurity=true” to the DbURL parameter
SQL Server Authentication Modes
The configuration of the SQL server database can be checked by going into SQL server administration and searching on security properties. If only Windows authentication is supported, the first bullet will be selected.
In Windows Authentication mode, the server will pass the credentials of the username and password used to start the Lavastorm service. For example, in the picture below, building39\prasmussen will be assumed to be the pre-authenticated username sent to SQL server.
The user name can then be validated by reviewing the access permissions for the specified user. Windows Authenticated users will be denoted by a “\” in the login.