Bookshelf Home | Contents | Index | PDF     

Siebel Data Quality Administration Guide > Installing Data Quality Products > Process of Installing the Oracle Data Quality Matching Server >

Configuring Oracle Data Quality Matching Server

The following tasks describe the steps involved in configuring Oracle Data Quality Matching Server for data matching on Microsoft Windows and on UNIX respectively.

This task is a step in Process of Installing the Oracle Data Quality Matching Server.

Configuring Oracle Data Quality Matching Server on Microsoft Windows

Use the following procedure to configure Oracle Data Quality Matching Server on Microsoft Windows.

To configure Oracle Data Quality Matching Server for data matching on Microsoft Windows

  1. If required, modify the odbc.ini file located at <drive>:\<IIR_Installation_Folder>\InformaticaIR\bin\ to contain the ODBC connection string of your target database, for example, as follows:

    [Target]
    ssadriver=ssaoci9
    server=qa19b_sdchs20n519

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

    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).

    The database information that you enter when installing Oracle Data Quality Matching Server is reflected in the odbc.ini file. If all values are correct and you do not want to make any changes to the database information, then you can skip this step.

  2. Copy the SiebelDQ.sdf file to the following (Informatica Identity Resolution server) folder location:

    <Drive>:\<IIR_Installation_Folder>\InformaticaIR\ids

    NOTE:  For an example SDF file, see Sample SiebelDQ.sdf File.

  3. To use the XML Sync Server instead of the External Business Components for Informatica Identity Resolution, then activate or deactivate the following ports located in <Drive>:\<IIR_Installation_Folder>\env\isss.bat.

    ::set SSA_XSPORT=1671

    ::set SSA_XSHOST=localhost:1671

    Removing the double colon from the beginning of the line activates the process listening on the ports:

    set SSA_XSHOST=localhost:1671

    set SSA_XSPORT=1671

    NOTE:  For Informatica Identity Resolution Version 2.7, you turn on the XML Sync Server by modifying the idsenvs.bat file located in <Drive>:\<ISS Installation Folder>\iss2704s\bin.

  4. Create a tmp folder for the Informatica Identity Resolution Synchronizer Workflow Log in <Drive>:\<IIR_Installation_Folder>\InformaticaIR\. For example:

    C:\InformaticIR\tmp

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

  5. Start the Informatica Identity Resolution Server by navigating to, for example, the following:

    Programs, Informatica, Identity Resolution V2.8.07 (InformaticaIR), Informatica Identity Resolution, Informatica IR Server - Start(Configure Mode)

    NOTE:  You can also start the Informatica Identity Resolution server from the command prompt using the idsup command.

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

    Programs, Informatica, Identity Resolution V2.8.07 (InformaticaIR), Informatica Identity Resolution, Informatica IR Console Client - Start(Admin Mode)

  7. Create a new system in Informatica Identity Resolution using SiebelDQ.sdf.

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

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

Configuring Oracle Data Quality Matching Server on UNIX

Use the following procedure to configure Oracle Data Quality Matching Server on UNIX.

To configure Oracle Data Quality 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 Informatica Identity Resolution is more recent than the one packaged with SSA-NAME3, copy the ssaiok shared library from the Informatica Identity Resolution 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 Informatica Identity Resolution 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. If required, 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 4 describes the ODBC drivers required for different operating systems.

    The database information that you enter when installing Oracle Data Quality Matching Server is reflected in the odbc.ini file. If all values are correct and you do not want to make any changes to the database information, then you can skip this step.

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

    Make sure that the SDF file is compressed before using FTP to copy it to the UNIX server. 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 Software Delivery Cloud. 

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