Bookshelf Home | Contents | Index | PDF     

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  >

Configuring ODQ Matching Server

This task is a step in Process of Setting Up ODQ Matching Server for Data Matching. The following tasks describe the steps involved in configuring ODQ Matching Server on Microsoft Windows and UNIX operating systems respectively.

Configuring ODQ Matching Server on Microsoft Windows

Use the following procedure to configure ODQ Matching Server on Microsoft Windows.

To configure ODQ Matching Server for data matching on Microsoft Windows 

  1. Modify the odbc.ini file located at <drive>:\IIR Installation folder\iss2704s\bin\ to contain the ODBC connection string of your target database, for example, as follows:

    [Target]
    ssadriver=ssaoci9
    server=qa19b_sdchs20n519

    NOTE:  For an Oracle database, the server parameter specifies a connect string from the tnsnames.ora file (which is the network configuration file of the Oracle Database client). For other databases, the server contains the ODBC datasource name (DSN).

    Table 30 summarizes the ODBC drivers required for different operating systems.

  2. Copy the SiebelDQ.sdf file to the following (IIR server) folder location:

    <Drive>:\IIR Installation folder\iss2704s\ids

  3. Turn on XML Sync Server by modifying the idsenvs.bat file located in <Drive>:\IIR Installation Folder\iss2704s\bin.

    In idsenvs.bat, activate the following commands (by removing the "::" at the beginning of the line):

    set SSA_XSHOST=localhost:1671
    set SSA_XSPORT=1671

  4. Create a tmp folder for the IIR Synchronizer Workflow Log in <Drive>:\IIR Installation Folder\iss2704s\. For example:

    C:\ids\iss2704s\tmp

    NOTE:  If you install IIR on a different drive (other than C:\), you must modify the ISSErrorHandler workflow in the Siebel application to specify the correct log folder. Other modifications that must be made if you install IIR on a drive other than C:\ include modifying action sets and the location where you deploy the XML files.

  5. Start IIR Server, for example, by navigating to:

    Programs, Identity Systems' Products, ISS 2.7.04, ISS v2.7.04 Server Start (Configure Mode)

  6. Start the IIR Console Client (in Admin Mode), for example, by navigating to the following:

    Programs, Identity Systems' Products, ISS 2.7.04, ISS v2.7.04 Console Client (Admin Mode)

  7. Create new system in IIR using SiebelDQ.sdf.

    The system that you create in IIR (Console Client, Admin Mode) must hold all the IDT and IDX database tables. For more information about creating a new system in IIR, see the relevant documentation included in Siebel Business Applications Third-Party Bookshelf in the product media pack on Oracle E-Delivery.

  8. When the system is created (initially, it will be empty), run LoadIDT from the IIR Console Client. For more information, see Initial Loading of Siebel Data into ODQ Matching Server Tables.

Configuring ODQ Matching Server on UNIX

Use the following procedure to configure ODQ Matching Server on UNIX.

To configure ODQ Matching Server for data matching on UNIX

  1. Copy the most recent version of the shared library libssaiok.so (libssaiok.sl on HP-UX) to the SSA-NAME3 bin directory.

    If the version packaged with IIR is more recent than the one packaged with SSA-NAME3, copy the ssaiok shared library from the IIR server distribution to the SSA-NAME3 bin directory as follows:

    cp $SSATOP/common/bin/libssaiok.* $SSAN3V2TOP/bin

    No action is required if the version packaged with IIR is older than the one packaged with SSA-NAME3.

  2. Set the shared library path according to your operating system.

    The following table shows examples of shared library paths.

    Operating System
    Shared Library Path

    Linux and Oracle Solaris

    LD_LIBRARY_PATH="$SSABIN:$SSANM3BIN:<DBMS shared object location>" export LD_LIBRARY_PATH

    HP-UX

    SHLIB_PATH="$SSABIN:$SSANM3BIN:<DBMS shared object location>"
    export SHLIB_PATH

    AIX

    LIBPATH="$SSABIN:$SSANM3BIN:<DBMS shared object location>"
    export LIBPATH
  3. Modify the odbc.ini file to contain the ODBC connection string of your target database:
    1. Copy the odbc.ini.ori file located in the $SSATOP/bin folder, and rename it odbc.ini.
    2. Edit the odbc.ini to contain the ODBC connection string of your target database, for example, as follows:

    [Target]
    ssaunixdriver=ssaoci9
    server=<TNS_entry_name_from_tnsnames.ora>

    For an Oracle database, the server parameter specifies a connect string from the tnsnames.ora file (which is the network configuration file of the Oracle Database client). For other databases, the server contains the ODBC datasource name (DSN). Most UNIX installations do not need the ODBC DSN, but if required, parameters change accordingly:

    [Target]
    DataSourceName=ODBC_DNS_Name_Pointing_to_ISS_DB
    ssaunixdriver=<ssaoci9>

    Table 30 describes the ODBC drivers required for different operating systems.

    NOTE:  The odbc.ini file is located in the $SSATOP/bin folder.

  4. Copy the System Definition File (SDF) to the UNIX server.

    Make sure that the SDF file is compressed before using FTP to copy the file. You must use the -a switch to extract a file on a UNIX server, for example, as follows:

    unzip - sysdeffile.zip

For more information about configuring ODBC on UNIX, see the relevant documentation included in Siebel Business Applications Third-Party Bookshelf in the product media pack on Oracle E-Delivery

    
Siebel Data Quality Administration Guide Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.