Deploying Interaction Server 8.5.1

Apart from the information provided on this page, the 8.5.1 release of Interaction Server is deployed in the same way as in previous releases.

UTF-8 Support

To enable the UTF-8 encoding, add the parameter -codepage UTF-8 to the startup file.

Database Connection

With DB Server

This configuration is the one used in releases 8.5.0 and earlier. It makes use of two configuration objects, a DAP and a DB Server instance, and is described in earlier versions of this Deployment Guide and in the Management Framework documentation.

With ODBC

To use an ODBC connection, you must add an option called dbprotocol to the settings section of the Interaction Server DAP and give it the setting odbc. You must also configure the Interaction Server Database Access Point (DAP) and the Interaction Server option odbc-string (settings section).

DAP

On the DB Info tab, enter

• User Name
• Password

Do not enter any other values on this tab.

odbc-string

The value of this option is a list of key-value pairs separated by semicolons: key=value;key=value;key=value;...;key=value;

It must contain the following keys, listed with their possible values and defaults:

• database—Any alphanumeric string, no default
• engine—MS SQL, DB2, or Oracle, no default
• driver—Any alphanumeric string in curly brackets, default depends on value of ‘engine’
• server—Any alphanumeric string, no default

Here are the default values for driver:

Database Type	Default Driver
MS SQL	{SQL Server Native Client 10.0}
DB2	{IBM DB2 ODBC DRIVER - DB2COPY1}
Oracle	{Oracle in OraClient11g_home1}

Example:

Driver={SQL Server Native Client 10.0};database=test_db;driver={TempDriver};server=ixndbhost;engine=MS SQL

See also the procedure that is described for configuring ODBC for the Database Capture Point.