For basic information on how to deploy the MSSQL Bridge, see the Kinetic Bridging Getting Started Guide.
The MSSQL Bridge comes packaged to run under Java 6. If the Servlet Contaner, such as Tomcat, that this Bridge web application is deployed to runs on Java 5, then:
- Rename the /WEB-INF/lib/sqljdbc.jar.java5 file to /WEB-INF/lib/sqljdbc.jar
- Rename the /WEB-INF/lib/sqljdbc4.jar file to /WEB-INF/lib/sqljdbc4.jar.java6
In order to use the integrated security option (authenticating with the Microsoft SQL Server as the user running your J2EE application server) you must follow the steps below after deploying the WAR file:
- Determine if the JVM your java applicaiton server is running on is either 32-bit or 64-bit.
- Copy either the 32-bit (/WEB-INF/lib/sqljdbc_auth/x86/sqljdbc_auth.dll) or 64-bit (/WEB-INF/lib/sqljdbc_auth/x64/sqljdbc_auth.dll) version of the sqljdbc_auth.dll file that matches the architecture your JVM is using to a directory specified in your java.library.path variable.
- Make sure your java application server is running as the Windows user account that you want to use for authenticating against the Microsoft SQL Server.
- Restart your java application server.
- Login to the bridge administrator console and change the 'Integrated Security' option from "No" to "Yes" (the Username and Password fields will be ignored now), set the Server, Port, and Database Name properties for your environment and save the changes.
|Use Integrated Security||No|
- Fixed a bug that was causing the bridge log to be left blank.
- Updated the Bridge Bootstrap to version 1.1.4.
Improved logging to include actual parameter values in queries when TRACE mode is set for the logging level.
Added support for Integrated Security when running on Windows Server. See 'Integrated Security' under the Deployment section.