Considerations for microsoft access, Considerations for mysql – Kofax Business Interaction Server User Manual
Page 14
![background image](/manuals/658284/14/background.png)
Chapter 3
8
Business Interaction Server Configuration Guide
Using Microsoft Access, Microsoft SQL Server, MySQL, or
PostgreSQL
This section outlines the necessary steps to successfully perform a data lookup in
Microsoft Access, Microsoft SQL Server, MySQL or PostgreSQL. The following lists a
few things that you should consider before actually starting to configure the data
connector.
Considerations for Microsoft Access
If you want Business Interaction Server to perform data lookup in your Microsoft
Access database, the following prerequisites must be met:
For a successful data lookup, make sure your Microsoft Access database is
installed on the same computer as Business Interaction Server.
Do not use special characters in your databases. In the current JDK version,
JDBC-ODBC Bridge does not support Unicode UTF-16. Consequently, data
lookup in Microsoft Access databases will fail if fields contain special
characters. For more information about this bug see http://bugs.sun.com/
bugdatabase/view_bug.do?bug_id=6345277.
Considerations for MySQL
If you are using a MySQL database, follow these instructions to make your MySQL
Server database ready for data lookup.
In order for Business Interaction Server to connect to your MySQL database,
install the appropriate JDBC driver.
a
Download MySQL Connector/J, the official JDBC driver for MySQL, from
http://dev.mysql.com/downloads/connector/j/5.1.html.
b
Open the ZIP archive of MySQL Connector/J.
c
Copy and paste mysql-connector-java-
Avalin server library of Business Interaction Server, usually located in
C:\Program Files\Kofax\Business Interaction
Server\Avalin\Jboss\server\avalin\lib.
d
Restart BISService.
For a successful data lookup, the SQL mode must be ANSI_QUOTES.
The default character set must be UTF-8.