Siebel Data Quality Administration Guide > Setting Up Oracle Data Quality Matching Server for Data Matching > Process of Setting Up ODQ Matching Server for Data Matching  >

Setting Up the Environment and the Database

This task is a step in Process of Setting Up ODQ Matching Server for Data Matching. This topic describes the prerequisites that are needed before starting to set up ODQ Matching Server for data matching, and also how to set up an Oracle database for ODQ Matching Server.

Java Runtime Environment

The installation and operation of the ODQ Matching Server is controlled by a Java application called the Console Client. The Console Client can be run on any operating system that supports Java 1.4 or later, and Java Help 1.1 is required. In order to run the Workbench, the Java Runtime Environment (JRE) is required.

JRE must be installed on the same computer as the Console Client. Before running the Console Client, ensure that the PATH and CLASSPATH environment variables have been set up for the correct Java and Javahelp installations.

For example, on a Win32 client:

SET CLASSPATH=%JAVAHELP_HOME%\jhall.jar
SET PATH=%PATH%;%JAVA_HOME%\bin

On UNIX operating system:

SSAJDK="/usr/java/jdk1.5.0_14"
CLASSPATH="/export/home/qa1/jh2_0/javahelp/lib/jhall.jar"

On UNIX, you set the PATH and CLASSPATH environment variables in the ssaset script file.

Network Protocol

Clients and Servers require a TCP/IP network connection. This includes DNS, which must be installed, configured and available (and easily contactable). The following paths (or their equivalents) must be correctly set up: /etc/hosts, /etc/resolv.conf and /etc/nsswitch.conf. Reverse name lookups must yield correct and consistent results.

ODBC Driver

The ODQ Matching Server uses Open Database Connectivity (ODBC) to access source and target databases. ODBC Drivers for specific databases must be installed and working. Installing and configuring ODBC drivers is operating system and database dependent. Unless the driver is provided by ODQ Matching Server (as is the case for an Oracle database), you must follow the instructions provided by your database manufacturer in order to install them. On Windows operating systems, navigate to Control Panel, Administrative Tools, and then Data Sources (ODBC) to create a DSN and associate it with a driver and database server.

At run time, the database layer attempts to load an appropriate ODBC driver for the type of database to be accessed. The name of the driver is determined by reading the odbc.ini file and locating a configuration block matching the database service specified in the connection string. For example, the database connection string odb:99:scott/tiger@ora920 refers to a service named ora920. A configuration block for ora920 looks similar to the following; the service name appears in square brackets:

[ora920]
ssadriver = ssaoci9
ssaunixdriver = ssaoci9
server = ora920.mydomain.com

A configuration block has the following syntax:

[Service_Name]
DataSourceName = ODBC_DSN
ssadriver = ODBC_Driver
ssaunixdriver = ODBC_UNIX_Driver
server = Native_DB_Service_Name

Table 30 shows some example odbc.ini configurations.

NOTE:  ODQ Matching Server provides a custom driver for the Oracle database that is installed during the installation of the product. ODQ Matching Server does not use the standard driver shipped with the Oracle DBMS.