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  >

Installing 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 installing ODQ Matching Server on Microsoft Windows and UNIX operating systems respectively.

NOTE:  Before installing and setting up ODQ Matching Server, install SSA-NAME3 server. For more information about SSA-NAME3 server installation on Microsoft Windows and on UNIX, see the relevant documentation included in Siebel Business Applications Third-Party Bookshelf in the product media pack on Oracle E-Delivery. 

Installing ODQ Matching Server on Microsoft Windows

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

To install ODQ Matching Server on Microsoft Windows

  1. Run setup from the root directory of the installed product media pack (which you downloaded from Oracle E-Delivery), and follow the onscreen prompts.
  2. Test ODBC connectivity.

    If this is your first time installing ODQ Matching Server, then an ODBC configuration file named %SSABIN%\odbc.ini is created. To generate this file, the installer will prompt you for the necessary information. If this is not your first time installing ODQ Matching Server and you have a configuration file from a previous installation, then the odbc.ini file will be copied to the server's bin directory.

  3. Run the IIR Console in Configure Mode.

    This mode tests the installation by loading a predefined IIR system and verifying its search and synchronization results.

  4. Apply bug fixes.

    Confirm that all bug fixes are installed by using the version command in the command prompt from the IIR server installation's bin directory ($SSABIN). For example:

    c:\ids\iss2704s\bin>version

    Identity Systems' ISS v2.7.04 (FixCD083 FixK057) + FixK066 + FixK104

  5. Start the IIR server, for example, by navigating to:

    Programs, Identity Systems' Products, ISS 2.7.04, ISS v2.7.04 Server Start

For more information about each of these steps and about IIR server installation on Microsoft Windows, see the relevant documentation included in Siebel Business Applications Third-Party Bookshelf in the product media pack on Oracle E-Delivery.

Installing ODQ Matching Server on UNIX

The installation process for ODQ Matching Server on UNIX is different from the installation process on Microsoft Windows (for example, there is no installation wizard). Installation on UNIX mainly consists of unarchiving the release, setting up the environment variables, and then running the console.

Use the following procedure to install ODQ Matching Server on UNIX. The installation can be completed from any user account as root privilege is not required.

To install ODQ Matching Server on UNIX

  1. Unarchive the release.

    The ODQ Matching Server UNIX release is supplied as a compressed tar file. Copy the compressed tar file to your UNIX computer. If using FTP, binary mode must be selected. Once the compressed tar file is on your UNIX computer:

    1. If the packaged release file has a .Z file name extension, then extract the file as follows: compress -d xxx.tar.z.

      If the packaged release file has a .zip file name extension, then extract the file as follows: unzip xxx.zip.

    2. Extract the binaries from the tar archive. For example:

    tar -xf xxx.tar

    After this has completed, there will be a directory on your computer called iss2704.ful containing all of the IIR components.

    1. Install the latest fix pack (if there is one available). A fix pack is distributed as a compressed tar file. Decompress and untar fixes, using one of the following:

    compress -d fixknnnsrv.tar.z
    tar -x fixKnnnsrv.tar

    unzip fixKnnnsrvt.zip
    tar -x fixKnnnsrv.tar

    1. Optionally, rename the release directory. For example:

    mv iss2704.ful iss2704

    NOTE:  If applying a fix pack in the future, you must temporarily restore the release directory name because untarring the fix pack places updates in the iss2704.ful directory.

  2. Set up the environment variables.
    1. Start a fresh Bourne shell, for example: sh.
    2. Edit the $SSATOP/ssaset script where SSATOP represents the name of the IIR release directory, as follows:

      NOTE:  The most recent version of ssaset is available on each fix pack and is called ssaset.ori. Copy this file to ssaset and then customize as required. Most of the environment variables that are set by this script do not need modification. However, some must be set and others must be checked.

      • Set SSATOP using an absolute path, and point it to the IIR Installation directory:

        /home/user/iss/iss2704

    • Set SSAN3V2TOP to the SSA-NAME3 v2 directory.

        /home/user/iss/nm32704

    • Establish your environment to enable communication with your host DBMS using the scripts provided to you by your database administrator. These scripts typically set some environment variables and paths required to communicate with your DBMS. The setup script for an Oracle Database is usually called by:

        . oraenv

    • Select the relevant setup script for your operating system and source it. This sets environment variables used to link the DBMS library. For example:

        . $SSATOP/setups/xxx

    where xxx refers to your operating system. For example:

        . $SSATOP/setups/gcclibc2 (Linuz)
        . $SSATOP/setups/rs32lfio (AIX 4.3.3, 32 bit)
        . $SSATOP/setups/solaris (Oracle Solaris 8, 32 bit)
        . $SSATOP/setups/hpux11 (HP-UX 11.0 PA-RISC, 64 bit)

    • Create the $HOME/tmp directory (if not already created) for each user who runs IIR programs and scripts.

      The setup script sets the variable SSATEMP to point to the $HOME/tmp by default. This directory is used for storing various temporary files. Alternatively, you can change this environment variable to point to another directory as long as a unique directory name is used for each user.

    • Check which version of awk is available on your UNIX operating system, then change the SSAAWK statement to specify this version. Use nawk for Oracle Solaris.
    • Set SSAPR to reflect the location of the SSA-NAME3 Population Rule directory (that is, if it differs from the default setting).
    • Set your Java environment if you want to use any of the Java clients, including the Console, from UNIX. The CLASSPATH and PATH variables must be set up appropriately (for more information, see Setting Up the Environment and the Database). Make sure Java Help (jhall.jar) is included in the CLASSPATH. For example:

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

    • Modify the line which sets SSAORATOP to point to the Oracle home directory ($ORACLE_HOME) on your system.
    • Select the appropriate LD_LIBRARY_PATH (or the equivalent) for your operating system. Comment out the inappropriate paths for different operating systems.
    • The default library paths work for most users. However, it is recommended that users change Library Paths to suit their requirements (for more information, see Configuring ODQ Matching Server on UNIX).
    • Modify SSASQLLDR to specify the name of your Mass Load utility.

      For an Oracle Database, it is called sqlldr.
      For UDB, it is called db2.
      For Microsoft SQL, it is called bcp.
      On OS/390, you must use $SSABIN/ssaload.

      Make sure that dbtype is set or changed accordingly. For example, use the following for Oracle Databases:

        SSASQLLDR="sqlldr"
        SSA_DB_TYPE="ora"

    • Check the host and port information for each IIR server program. Port numbers only must be changed if the default ports clash with those used by an existing process. The default port numbers and corresponding environment variables are listed in the following table.
      Server Name
      Environment Variable

      Search Server

      SSA_SEPORT=1666

      Connection Server

      SSA_COPORT=1667

      Rulebase Server

      SSA_RBPORT=1668

      Connection Server

      SSA_CSPORT=1669
    • The OS/390 environment requires additional variables.

      SSA_DB_PLAN and SSA_DB_SUBSYSTEM must be set to the name of your database plan and subsystem respectively.

      DB2HLQ must be set to the high level qualifier of your DB2 installation dataset (usually DSN710).

    • SSA_DB_RBSTORAGE must be set to the storage clause of the Rulebase (for example: "IN SSA02").
    1. Source ssaset to establish the environment variables. For example:

    .$SSATOP/ssaset

    Note the following:

    • POSIX compliant shells can terminate the script when any undefined environment variables are referenced. If this occurs, add the following command as the second line of the script and then source it again:

        set +u

    • Change the following line:

        SSA_XSHOST="$SSA_XSHOST:$SSA_XSPORT"

    to:

        SSA_XSHOST="$SSA_XXHOST:$SSA_XSPORT"

    • Before the following line:

        echo "ssaset: The ISS environment variables have been set.":

    Add the following environment parameters:

        SSA_RBNAME="odb:0:<ISSDB_userName>/<ISSDB_passWord>@<Service_Name>";     export SSA_RBNAME

        SSA_RB_RESTART_ID="0"; export SSA_RB_RESTART_ID

    where:

    • ISSDB_userName is the database user created in SQL script 1_x.sql.
      ISSDB_passWord is the database password created in SQL script 1_x.sql.
      Service_Name is the connection string name as defined in the odbc.ini file.
  3. Test the installation by running a regression test to confirm that the software has been installed and configured correctly.

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

  4. Start and stop the IIR server from a UNIX shell prompt as follows:

    $SSABIN/idsup
    $SSABIN/idsdown

  5. Verify that IIR is operational. For example, from within the IIR ConsoleClient:
    1. Click Search Client, select the Search Client radio button, then click OK.
    2. Click the appropriate search mechanism button, input the desired search criteria, then click Search.

      The records stored in the IIR tables are returned.  

For more information about each of these steps and about IIR server installation and set up 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.