Configuring External Database Access

The ESP server accesses external databases by using database services defined in the service.xml configuration file.

For the server to communicate with external databases, you must:

Have a working JDBC, ODBC, or Open Client™ connection with the appropriate JDBC, ODBC, or OCS driver for the desired external database installed.
To connect to an SAP HANA database, you must have an SAP HANA ODBC client installed. SAP recommends that you use the latest version of the SAP HANA ODBC client available, but it must be at least version 1.0.67.
Specify service definitions in the service.xml file for your desired database connections.

If you make changes to the service.xml file while the ESP Server is running, the Server does not recognize the changes until you restart it. If you are running on the local cluster, which the ESP Studio starts on its own, restart the ESP Studio as well.

Adapter	Supported Drivers	Supported Databases
SAP® Sybase® Adaptive Server® Enterprise (ASE) Output Adapter	Open Client™	SAP Sybase ASE
Database Input and Output Adapters	JDBC	SAP Sybase ASE IBM DB2 Oracle Kx Systems KDB+ Microsoft SQL Server SAP HANA®
Database Input and Output Adapters	ODBC	SAP Sybase ASE SAP® Sybase® IQ SQL Anywhere® IBM DB2 Oracle Microsoft SQL Server TimesTen MySQL 5.x PostgreSQL SAP HANA
SAP HANA Adapter	ODBC	SAP HANA
SAP Sybase IQ	ODBC	SAP Sybase IQ

On UNIX systems, SAP recommends upgrading to version 2.3.0 or later of unixODBC. If you are using a version lower than 2.3.0, set a parameter for the driver that instructs the database manager not to synchronize database access. To do this, add a line that says “Threading = 0” for your driver in the odbcinst.ini file.

If you are running the SAP HANA Output adapter on a UNIX system, use only unixODBC 2.3.0 or higher.

If you are using version 2.3.0, add “Threading=0” in the odbcinst.ini file to ensure optimal adapter performance.
If you are using version 2.3.1, create a symbolic link under <2.3.1 installation folder>/lib as follows:
```
ln -s libodbc.so.2.0.0 libodbc.so.1
```
This link is required because ESP links to libodbc.so.1, which unixODBC 2.3.1 has renamed libodbc.so.2. With the link, ESP will now use libodbc.so.2.