1. Data Quality Administration Guide
  2. What’s New in This Release

4Installing Data Quality Products

Installing Data Quality Products

This chapter explains how to install the following data quality products for Siebel CRM and Oracle Customer Hub:

Process of Installing the Oracle Data Quality Matching Server

The Oracle Data Quality Matching Server provides real-time and batch data matching functionality using licensed third-party Informatica Identity Resolution (IIR) software. The Oracle Data Quality Matching Server connector uses the Universal Connector in a mode where match candidate acquisition takes place within the Oracle Data Quality Matching Server. Since the match keys are generated and stored within the Oracle Data Quality Matching Server, key generation and key refresh operations are eliminated within Siebel CRM.

To install the Oracle Data Quality Matching Server for data matching, perform the following tasks:

  1. Setting Up the Environment and the Database

  2. Installing Oracle Data Quality Matching Server

  3. Creating Database Users and Tables for Oracle Data Quality Matching Server

  4. Configuring Oracle Data Quality Matching Server

  5. Configuring Data Quality for Oracle Data Quality Matching Server

  6. Modifying Configuration Parameters for Oracle Data Quality Matching Server

  7. Deploying Workflows for Oracle Data Quality Matching Server Integration

  8. Initial Loading of Siebel Data into Oracle Data Quality Matching Server Tables

Setting Up the Environment and the Database

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

Java Runtime Environment

The installation and operation of theOracle Data Quality 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: 

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 Oracle Data Quality 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 a driver is provided by Oracle Data Quality 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 system, 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;

[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

Creating Database Users and Tables for Oracle Data Quality Matching Server shows the databases supported by Oracle Data Quality Matching Server, describes the ODBC drivers required for different operating systems, and shows example odbc.ini configurations.

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

Installing Oracle Data Quality Matching Server

This task is a step in Process of Installing the Oracle Data Quality Matching Server. The following tasks describe the steps involved in installing Oracle Data Quality Matching Server on Microsoft Windows and on UNIX respectively.

Note: License key information for the Oracle Data Quality Matching Server is included in the product media pack on Oracle Software Delivery Cloud.

Installing Oracle Data Quality Matching Server on Microsoft Windows

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

Note: Installation is the same no matter what version of Informatica Identity Resolution you are installing.
To install Oracle Data Quality Matching Server on Microsoft Windows

  1. Run setup from the root directory of the installed product media pack (which you downloaded from Oracle Software Delivery Cloud), and follow the onscreen prompts to install the following options:

    • Install License Server

    • Install Informatica Product

    Note: You must install these options in the order that they are displayed.

  2. Select Install License Server, click Next to continue, then do the following:

    1. Browse to the installation directory where you want to install the License Server, then click Next.

    2. Enter the host name and port number for the License Server.

    3. Verify the installation summary details on the next screen that displays, then click Install.

    4. When installation is complete, you are prompted to start the License Server. Click No to close the prompt, then Finish to return to the main installer window.

    5. Copy the OEM license key file downloaded from Oracle Software Delivery Cloud to the following location:

      <Drive:>\InformaticaIR\licenses

    6. Set the environment variable SSALI_MZXPQRS to STANISLAUS (system variable).

    7. Start the License Server by selecting, for example, the following:

      Programs, Informatica, Identity Resolution V2.8.07 (InformaticaIR), Informatica License Server, and then Start.

  3. Select the Install Informatica Product from the main installer window, click Next to continue, then do the following:

    1. When prompted to specify the path to the OEM license, browse to the [installation_media_directory]\data\file1003.dat file, and then click Next to continue.

    2. Enter the host name and port number for the License Server (or accept the default), then click Next.

    3. Browse to the installation directory where you want to install Informatica Identity Resolution, then click Next.

    4. The next screen displays a list of components, click Select All, and then Next.

    5. The next screen displays an installation summary of products and modules that you want to install. Review the details and click Next to confirm that they match your requirements.

    6. Select default port values for all servers.

      Make sure to add XML Synchronization server at port 1671. This server is not set by default. Click Next when done.

    7. On the next screen, enter database information, as follows:

      • Service Name: Enter the database service name on Informatica Identity Resolution. This is used when configuring SIEBEL instances.

      • ODBC Data Source Name: Enter the ODBC Connect String name if using ODBC (the ODBC Data Source name is required only when connecting through ODBC).

      • ODBC Driver: Select the applicable database driver from the drop-down list (the ODBC driver name must be provided even when ODBC is not being used).

      • Native Service: Enter the name for the database connection as defined in dB Client\ Server utilities (for example: for Oracle an databases, this is the TNS entry name).

        Example settings when using an Oracle database are:

                 Service Name: target
ODBC Data Source Name: 
          ODBC Driver: Oracle 9 (or later) client software
  Native Service Name: <tns_entry>
        Note: All configuration information entered in this step is written to the odbc.ini file. Creating Database Users and Tables for Oracle Data Quality Matching Server shows some example odbc.ini configurations.

    8. Click Next to start the installation.

    9. Click Finish to complete.

  4. Post installation, do the following:

    1. Install the hot fix on top of the Base Installer for Informatica Identity Resolution 2.8.07. Make sure that you apply the latest Informatica Identity Resolution fix, which is available on Oracle Software Delivery Cloud. 

      C:\InformaticaIR\bin>version
SSA-NAME3 v2.8.07 (FixL106)
SSA-NAME3 Extensions v2.8.07 (FixL106)
Data Clustering Engine v2.8.07 (FixL106)
Informatica Identity Resolution v2.8.07 (FixL106 + FixL113 + FixL114 + FixL120 
+ FixL123 + FixL124 + FixL125 + FixL126 + FixL127 + FixL134 + FixL136 + FixL140 
+ FixL141 + FixL145 + FixL147 + FixL148)

    2. Rename xsserv.xml.org located in <drive>\InformaticaIR\bin to xsserv.xml. This file has a sample format. Change it to match the following: 

      <server xmlns="_http://www.identitysystems.com/xmlschema/iss-version-1/
xmlserv">
 <mode>generic</mode>
 <rulebase>odb:0:db_username/db_password@ISS_connectstring</rulebase>
</server>
Note: If you do not make these changes to xsserv.xml, then errors might occur using legacy SIEBEL-ISS Sync workflows.

Installing Oracle Data Quality Matching Server on UNIX

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

Note: Installation is the same no matter what version of Informatica Identity Resolution you are installing.
To install Oracle Data Quality Matching Server on UNIX

  1. The following prerequisites must be met:

    1. Obtain an installable ISO from Informatica or Oracle Software Delivery Cloud.

    2. Make sure to mount the ISO to a suitable location which is accessible to the user who is installing Informatica products.

    3. Ensure that the required ODBC entries (if applicable) are created.

    4. Ensure to add TNS entries pointing to the Informatica Identity Resolution Database (target database) for system configurations.

    5. The Informatica Installer requires a UNIX GUI for installation and product administration. If necessary, contact your system administrator to make sure that the corresponding applications and X-Server have been enabled for easy access.

  2. After ensuring the installer location and GUI access, start the installer from the mounted location using the following command:

    ./install

    The Informatica Installer window opens with three options. You must install the three options in the order that they are displayed.

  3. Select the Install License Server from the installer, click Next to continue, then do the following:

    1. Select the path where you want to install the license server, then click Next.

    2. Enter the port number for the License Server on the next screen that displays. You can accept the default (if available), or choose to change the port. Click Next when done.

    3. Verify the installation summary details on the next screen that displays, then click Install.

    4. When installation is complete, you are prompted to start the License Server. Click No, and then Finish to return to the main installer window. You must start the License Server only when the license file is available.

    5. Copy the OEM license key file downloaded from Oracle Software Delivery Cloud to the following location:

      <Drive:>/InformaticaIR/licenses

    6. Export the environment variable SSALI_MZXPQRS to STANISLAUS (system variable) before proceeding to the next step.

    7. Start the License Server:

      • Start an xterm / ssh session.

      • Change to bash (Bourne Shell)

      • Copy the license file to <installation_folder>/licenses

    8. Set common environment variables by sourcing idsset script located at <IIR_Installation_Folder>/env. For example:

      . ./idsset

    9. Set the environment variables required to start the License Server by sourcing script lienvs located at <IIR_Installation_Folder>/env. For example:

      . ./lienvs

    10. Start the License Server using the following command: $SSABIN/liup.

  4. Select Install Informatica Product from the main installer window, click Next to continue, then do the following:

    1. When prompted to specify the path to the OEM license, browse to the [installation_media_directory]/data/file1003.dat file, and then click Next to continue.

    2. Enter the License Server port number or accept the default, then click Next.

    3. The next screen displays a list of components. Licensed components have an editable check-box. Select the check box beside the required components and populations, and then click Next.

    4. The next screen displays a summary of selected options. Verify the details, then click Next.

    5. On the next screen, select or set servers and their ports, then click Next. If a port is already in use, you must change it.

    6. On the next screen, enter database information:

      • Service Name: Enter the database service name on Informatica Identity Resolution (this is used when configuring SIEBEL instances).

      • ODBC Data Source Name: Enter the ODBC Connect String name if using ODBC (the ODBC Data Source name is required only when connecting through ODBC).

      • ODBC Driver: Select the applicable database driver from the drop-down list (the ODBC driver name must be provided even when ODBC is not being used).

      • Native Service: Enter the name for the database connection as defined in dB Client/Server utilities (for example: for Oracle an databases, this is the TNS entry name).

        Example settings when using an Oracle database are:

                 Service Name: target
ODBC Data Source Name: 
          ODBC Driver: Oracle 9 (or later) client software
  Native Service Name: <tns_entry>

        Click Next to continue.

        Note: All configuration information entered in this step is written to the odbc.ini file. Creating Database Users and Tables for Oracle Data Quality Matching Server shows some example odbc.ini configurations.

    7. The next screen displays an installation summary of products and modules that you want to install. Verify the details and confirm that they match your requirements.

    8. Click Install to start the installation.

    9. Click Finish to complete.

  5. Post installation, rename xsserv.xml.ori located in <IIR_Installation_Folder>/bin to xsserv.xml. Change the contents of this sample file as follows:

    1. Change <mode> to generic

    2. Add rulebase details.

      For example:

      <server xmlns="_http://www.identitysystems.com/xmlschema/iss-version-1/xmlserv">
<mode>generic</mode> 
<rulebase>odb:0:db_username/db_password@ISS_connectstring</rulebase> </server>
      Note: If you do not make these changes to xsserv.xml, then errors might occur using legacy SIEBEL-ISS Sync workflows.

Creating Database Users and Tables for Oracle Data Quality Matching Server

Creating database users and tables involves executing a number of scripts on the Oracle Data Quality Matching Server database. The scripts that you must execute are located in the Oracle Data Quality Applications media pack on Oracle Software Delivery Cloud. Once the media pack is downloaded and installed, the scripts are located in the InformaticaIR/dbscript/ora folder. For example (idsuseru.sql):

C:/InformaticaIR/dbscript/ora/idsuseru.sql

You must open these scripts and modify them as required, depending on the database that you are using. For example, complete the steps in the following procedure to create database users and database tables for Oracle Data Quality Matching Server if using an Oracle database. Note the following:

  • The procedure is similar if using Microsoft SQL Server, UDB, or DB2 on OS/390. However, you must modify the SQL scripts according to the database that you are using.

  • The procedure is also similar whether creating database users and database tables for Oracle Data Quality Matching Server on Microsoft Windows or on UNIX.

  • When setting up the database for Oracle Data Quality Matching Server on UNIX, you must set TNSNAmes.ora with an entry to the target database (Oracle Data Quality Matching Server database), and perform connectivity testing using SQLPLUS if required.

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

To create database users and tables for Oracle Data Quality Matching Server if using an Oracle database

  1. Log in to the database as database administrator, then execute the idsuseru.sql script to create a new database user with appropriate privileges to create and update Oracle Data Quality Matching Server tables.

    Note: You must be logged in as database administrator to execute idsuseru.sql.

  2. Log in to the database as the new database user (created in Step 1 with appropriate privileges to create and update Oracle Data Quality Matching Server tables), then execute the following SQL scripts to create other Oracle Data Quality Matching Server database tables, such as IDT and IDX tables. You can execute the following SQL scripts in any order:

    Note: IDT tables store the copy of source records in the Oracle Data Quality Matching Server database. IDX tables store the index keys for IDT tables. Each IDT table can have one or more IDX tables associated with it.

    1. Execute idstbora.sql to create control tables for the Oracle Data Quality Matching Server.

    2. Execute updsyncu.sql to create database objects required by the Oracle Data Quality Matching Server to synchronize data in ID tables with updates to user source tables.

      Run this script on all databases containing user source tables that require synchronization, and also before loading any ID tables that require synchronization.

    3. Execute updsynci.sql to create database objects required by the Oracle Data Quality Matching Server to synchronize data in ID tables with updates to user source tables.

      Run this script on the database which will contain IDTs, and also before loading any ID tables that require synchronization.

    4. Execute updsyncg.sql to create database objects required by the Oracle Data Quality Matching Server to synchronize data in SSA-ID tables with updates to user source tables.

      This script will create public synonyms for the Oracle Data Quality Matching Server objects created on user source table databases. This script must be run by someone (for example, the database administrator) who has the privilege to CREATE PUBLIC SYNONYM. Run this script after running updsyncu.sql. Use the same userid to run updsynci.sql as you did to run updsyncu.sql.

      Note: You must be logged in as database administrator to execute updsyncg.sql.

The following table describes some example odbc.ini configurations.

Database Description Example odbc.ini Configurations

Oracle Database 10g

The Oracle database driver works out-of-the box and is named %SSABIN%\ssaoci{8|9}.dll on Windows, and $SSABIN/libssaoci{8|9}.s{o|l} on UNIX. There are no special setup requirements, other than adding configuration blocks to your odbc.ini file. The ODBC_Driver name can be either ssaoci8 or ssaoci9. The former must be used with Oracle 8 client libraries and does not support Unicode data. The latter can be used with Oracle 9 (or later) client libraries and supports Unicode access.

When using the ssaoci9 driver with Oracle Database 10g client software, the connectivity test might fail on some UNIX operating systems. This occurs because the driver has been linked with libclntsh.so.9.0, which is not distributed with Oracle Database 10g. Oracle normally provides backward compatibility by adding symbolic links to redirect requests for older versions of the library to the current version. Unfortunately, by default, this practice is restricted to minor versions only (for example, 9.0-9.2). To overcome the problem, locate the appropriate Oracle lib directory (lib, lib32, or lib64) and add a symbolic link. For example:

cd $ORACLE_HOME/lib32
ln -s ./libclntsh.so libclntsh.so.9.0

[ora10g]
ssadriver = ssaoci9
ssaunixdriver = ssaoci9
server = 
ora10g.mynet8tns.name

Universal Database (UDB)

UDB must be installed prior to the installation of Oracle Data Quality Matching Server.

IBM provides ODBC drivers for both Windows and UNIX operating systems, named db2cli and db2 respectively.

For more information about the db2cli and db2 drivers, see the appropriate UDB manuals for full details.

 
[test-udb]
DataSourceName = udb8
ssadriver = db2cli
ssaunixdriver = db2
server = 
UDB_database_alias

Microsoft SQL Server

Microsoft provides a Windows ODBC driver named sqlsrv32. It is configured by adding a new Data Source Name (DSN) using Control Panel, Administrative Tools, Data Sources (ODBC).

For more information about the sqlsrv32 driver, see the appropriate Microsoft manuals for specific details.

The ODBC_Driver name is sqlsrv32 and the Native_DB_Service is the server name (-S parameter of the osql and bcp utilities).

The SQL Server Native Client (sqlncli.dll) can be used as an alternative driver.

 
[production]
DataSourceName = msq2003
ssadriver = sqlsrv32
server = mySQLServer

Sybase

For more information about the sybdrvodb drivers, see the appropriate Sybase manuals for installation specifics.

 
[production]
DataSourceName = ase150
ssadriver = sybdrvodb
ssaunixdriver = 
sybdrvodb
server = mySybaseServer

Testing Connectivity

Use the dblist utility to test your ODBC configuration by connecting to a database whose connection string is provided with the -d parameter. An example of the output associated with a successful connection follows:

$SSABIN/dblist -c -dodb:99:ssa09/SSA09@ora920
Maximum connections per module: 1024
Linked databases: odb: sdb:
Driver Manager: 'Identity Systems ODBC Driver Manager 1.2.2.3'
ODBC Driver: 'ssaoci9 SSADB8 2.7.0.00MSVC60 Jun 8 2006 17:26:56'
DBMS Name: 'Oracle DBMS (9.2.0.6.0)'
Native DB type: 'ora'

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

    Creating Database Users and Tables for Oracle Data Quality Matching Server 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 (IIR server) folder location: 

    <Drive>:\<IIR_Installation_Folder>\InformaticaIR\ids
    Note: For an example SDF file, see Sample Siebel DQ.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 IIR 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 IIR 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 IIR 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 IIR using SiebelDQ.sdf.

    The system that you create in IIR (Console Client, Admin Mode) will hold all the IDT and IDX database tables.

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

      Creating Database Users and Tables for Oracle Data Quality Matching Server 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

Modifying Configuration Parameters for Oracle Data Quality Matching Server

The ssadq_cfg.xml file contains the global configuration parameters for Oracle Data Quality Matching Server (IIR). To modify ssadq_cfg.xml, complete the steps in the following procedure. This task is a step in Process of Installing the Oracle Data Quality Matching Server. For an example ssadq_cfg.xml file, see Sample Configuration Files.

To modify configuration parameters for the Oracle Data Quality Matching Server

  1. Open up a text editor.

  2. Modify the following parameters in ssadq_cfg.xml, as required:

    1. Set <iss_host> to point to the server where Oracle Data Quality Matching Server is running.

    2. Set <iss_port> to 1666 (which is the default), unless you are using a different port for installation.

    3. Set the <rulebase_name> parameter. For example, with Oracle Database 10g:

      • username is ssa

      • password is SIEBEL

      • ServiceName is Target (as specified in the odbc.ini file for the Oracle Data Quality Matching Server server)

      • <rulebase_name> Example: odb:0:ssa/SIEBEL@Target

    4. Set <contact_system>, <account_system>, and <prospect_system> to the name of the system that you create in Oracle Data Quality Matching Server (IIR) using the SiebelDQ.sdf file.

      The system that you create in IIR (Console Client, Admin Mode) will hold all the IDT and IDX database tables.

      If you want to run Oracle Data Quality Matching Server against only a single entity (for example, Accounts) as opposed to multiple entities (Accounts, Contacts, and Prospects), then you must alter the definitions within the SiebelDQ.sdf file to include only the one entity that you want as otherwise the synchronizer fails to run. In this example, you must remove the definitions for Contacts and Prospects.

      Any changes that you make to the SDF file must be appended to the user property for the business service DQ Sync Services. If you do not want to use a particular field (for example, Birth Date) as part of deduplication, then that field must be removed from the SDF file. In addition, you must do the following:

      • Remove the corresponding mapping from data quality third-party administration settings in your Siebel application.

      • Change the user property in the DQ Sync Services business process. For example:

        For Account, change the Account_DeDupFlds user property.

        For Contact, change the Contact_DeDupFlds user property.

      • Remove the DeDup field from the user property.

      • Remove the corresponding mapping in the user property for external length.

        This is Account_ExtLen for Account, and Contact_ExtLen for Contact.

      Since CUT Address is shared across Account and Contact, any change in the CUT Address is reflected in both Account and Contact de-duplication.

  3. Save the ssadq_cfg.xml file and copy to the SDQConnector folder on Siebel Server for changes to take effect:

    siebsrvr/SDQConnector

Deploying Workflows for Oracle Data Quality Matching Server Integration

In the Siebel application, make sure that the following workflows are deployed and activated if using workflows to synchronize with the Oracle Data Quality Matching Server. This task is a step in Process of Installing the Oracle Data Quality Matching Server.

  • ISS Build Load File

  • ISS Delete Record Sync

  • ISS ErrorHandler

  • ISS Launch Build Load File

  • ISS Launch Delete Record Sync

  • ISS Launch PreDelete Record Sync

  • ISS Launch PreWrite Record Sync

  • ISS Launch Write Record Sync

  • ISS PreDelete Record Sync

  • ISS PreWrite Record Sync

  • ISS WriteRecordNew

  • ISS WriteRecordUpdated

  • ISS Write Record Sync

  • ISS Launch Record Sync

  • ISS PreLaunch Record Sync

  • ISS Launch Record ASync

These workflows are used to synchronize data between the Siebel application and Oracle Data Quality Matching Server (IIR) tables. For more information about Siebel Workflow, see Siebel Business Process Framework: Workflow Guide.

Note: The activation or deactivation of these workflows depends on your business needs. The business service, DQ Sync Services, can be used if you are using the multiple address feature.

Initial Loading of Siebel Data into Oracle Data Quality Matching Server Tables

To initially load your Siebel application data into Oracle Data Quality Matching Server (IIR) tables, complete the steps in the following procedure. This procedure uses SQL scripts and is for large implementations where, for example, the database is too large to use an XML file import or export to initially load Siebel application data into Oracle Data Quality Matching Server tables.

Caution: Before proceeding any further, you must read, understand, and follow the following guidelines:

  • It is highly recommended that data is directly loaded from source tables into Oracle Data Quality Matching Server tables.

    The sample system definition file (SiebelDQ.sdf) includes appropriate sections to load data directly from source tables into Oracle Data Quality Matching Server tables.

    Note: For an example SDF file, see Sample Siebel DQ.sdf File.

  • The system definition file includes information about the matching criteria for various entities.

    As part of the initial analysis, it is essential that you review the sample system definition file (SiebelDQ.sdf) and make appropriate changes to it, before creating any new systems in IIR.

  • The sample system definition file (SiebelDQ.sdf) is not a preconfigured configuration file; it serves as a sample for you to start with.

  • Make sure that the entries in the system definition file are in sync with the data quality configuration settings that you set up in your Siebel application (in Administration - Data Quality screen, Third Party Administration view).

  • Make sure that the user properties that you set up in Siebel Tools for the business service are in sync with the entries in your system definition file.

Note: If you encounter errors when trying to initially load a high volume of data (greater than 10,000 records), then set the system environment variable SSAOCI_IGNORE_UCS2_BYTES to one, and restart the Oracle Data Quality Matching Server server and client. Also, adding zeros when setting the SSA_XML_SIZE parameter can help when initially loading large files. For example: set SSA_XML_SIZE to 8000000.

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

To initially load Siebel application data into Oracle Data Quality Matching Server tables

  1. Start the IIR 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)

  2. Start the IIR Console Client (in Admin Mode) by navigating to:

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

  3. If not already done so, create a new system in IIR using the appropriate System Definition file that you have reviewed and modified using the sample SiebelDQ.sdf file as a starting point. Or, if a system already exists, select it and refresh it by clicking the System/Refresh button.

    The system that you create in IIR (Console Client, Admin Mode) will hold all the IDT and IDX database tables.

    Note: If you want to run IIR against only a single entity (for example, Accounts) as opposed to multiple entities (Accounts, Contacts, and Prospects), then you must alter the definitions within the SiebelDQ.sdf file to include only the one entity that you want as otherwise the synchronizer fails to run. In this example, you must remove the definitions for Contacts and Prospects.

  4. Run the IDS_IDT_<ENTITY TO BE LOADED>_STG.sql script to take a snapshot of records in the Siebel application. For example, for account initial load, execute the following script from the SQL prompt as user SSA_SRC:

    IDS_IDT_ACCOUNT_STG.sql

    Depending on project requirements, IIR configuration, and data quality configuration, you must modify sample scripts provided with the software accordingly.

    Note: It is not mandatory to always load the data incrementally. If the initial volume of data to load is not high, then you can load the data directly from source tables to IIR tables in one go.

  5. Run the IDS_IDT_CURRENT_BATCH_<ENTITY TO BE LOADED>.sql script to create the dynamic view to load the snapshot created in Step 4. For example, for account initial load, execute the following script from the SQL prompt as user SSA_SRC:

    IDS_IDT_CURRENT_BATCH_ACCOUNTS.sql

    To be in sync with the snapshot created in Step 4 and the SDF file used for system creation in Step 3, you must modify the sample scripts provided with the software according to project requirements, IIR configuration, and data quality configuration. Also, use a batch size that is appropriate to your project needs, initial data load volume, and any other project specific needs.

  6. Run the following SQL script to create the database table to store the current batch number being loaded:

    IDS_IDT_CURRENT_BATCH.sql

  7. Load IIR with data from the Siebel application by clicking the System/Load IDT button.

    Make sure to select the All_load option from the Loader Definition menu in the dialog that displays. This process loads records with batch number 1 from the snapshot created earlier. Validate the data to make sure that all the records with batch number 1 are correctly loaded.

  8. Open a command window and navigate to the directory where the initial load scripts were copied during product installation.

  9. Execute the initial load process by entering the following command at the command line:

    IDS_IDT_LOAD_ANY_ENTITY.CMD <Entity> <System> <Work Directory>

    For example, for account initial load, execute the following script:

    IDS_IDT_LOAD_ANY_ENTITY.CMD Account c:/initialLoad/logs

    This loads data in batches from the snapshot created in Step 4. The log files and error files recording the outcome of each batch load are stored in the C:/InitialLoad/logs directory.

  10. Examine the log files and error files to identify any batch that failed to load. Use the information in the log and error files to determine the root cause for any failure and fix the underlying issue.

  11. Incrementally load the failed batches individually using the following script from the command line:

    IDS_IDT_LOADBATCH_ANY_ENTITY.CMD

    For example, to load batch 33 of account, execute the following script from the command line:

    IDS_IDT_LOADBATCH_ANY_ENTITY.CMD Account SiebelDQ c:/initialLoad/logs 33

  12. Examine the log files and error files to ensure that the (failed) batches successfully loaded. In case of errors, use the information in the log and error files to determine the root cause for the failure and fix the underlying issue. Repeat Step 11 until all the batches have successfully loaded.

  13. Repeat this process to load other entities such as contacts and prospects.

Process of Installing the Oracle Data Quality Address Validation Server

The Oracle Data Quality Address Validation Server provides address validation and standardization functionality using licensed third-party Informatica Identity Resolution software. The process of installing the Oracle Data Quality Address Validation Server for data cleansing is broken down into the following tasks:

  1. Installing Oracle Data Quality Address Validation Server

  2. Configuring Siebel CRM for the Oracle Data Quality Address Validation Server

  3. Modifying Configuration Parameters for Oracle Data Quality Address Validation Server

  4. Acquiring the License Key and Postal Directories for Oracle Data Quality Address Validation Server

Installing Oracle Data Quality Address Validation Server

Use the following procedure to install the Oracle Data Quality Address Validation Server. This task is a step in Process of Installing the Oracle Data Quality Address Validation Server.

Note: Installation is the same no matter what version of Informatica Identity Resolution you are installing.

To install Oracle Data Quality Address Validation Server

  1. Install Informatica Identity Resolution.

    The Oracle Data Quality Address Validation Server is installed as part of Informatica Identity Resolution installation. For more information about Informatica Identity Resolution installation on Microsoft Windows and on UNIX, see the following: The ssadqasm.dll file uses the Oracle Data Quality Address Validation Server for address cleansing. You need a license to use the Oracle Data Quality Address Validation Server.

  2. Obtain licensing for the postal directories (or postal validation databases), and then:

    Note: The postal directories and the license for the postal directories must be obtained directly from Informatica Address Doctor. For more information, see Acquiring the License Key and Postal Directories for Oracle Data Quality Address Validation Server. Informatica bundles geographies in different ways - for example, North America is cheaper than USA + Canada + Mexico.

    1. Copy the postal validation databases to the following location:

      <InstallDir>:/InformaticaIR/ssaas/ad5/ad/db
      Note: This is the postal directory path for Informatica Address Doctor Version 5. For Informatica Address Doctor Version 4, the postal directory path is InformaticaIR/ssaas/ad/ad/db.

    2. Copy the following DLLs from informaticaIR/bin to siebelsrvr/bin:

      ssasec.dll

      ssadqasm.dll

      ssadqsea.dll

      ssaiok.dll

      Note: Copy these DLLs if using Windows. Copy the libXXXX.so DLLs if using UNIX. For UNIX, the target directory is siebsrvr/lib. For Windows, the target directory is siebsrvr\bin.]

      Make sure that you copy the DLLs to Siebel Server every time you upgrade or apply a new patch for your Siebel application.

    3. Place the Oracle Data Quality Address Validation Server key file in the /ssaas/ad5/ad/db folder. For example: 

      <InstallDir>:/InformaticaIR/ssaas/ad5/ad/db

      The key file contains an unlock code for specific databases; Informatica sends the key file along with the postal directories.

      Note: If using Informatica Identity Resolution 9.01, see Upgrading to Informatica Identity Resolution 9.01 ( Upgrading to Informatica Identity Resolution 9.01).

  3. Install country files in the /ssaas/ad5/ad/db folder. For example: 

    /InformaticaIR/ssaas/ad5/ad/db

  4. Add UNITED STATES to the COUNTRY list of values:

    1. Navigate to Administration - Data screen, then the List of Values Explorer view.

    2. Click Query, and query for the following in the List of Values - Type field: COUNTRY.

    3. In the LOV explorer panel, click the COUNTRY node (by clicking the + sign) and navigate to the values for COUNTRY.

    4. Add a new entry for UNITED STATES.

      Repeat this step for each country where you acquired postal directories. For example, add CANADA to the COUNTRY list of values in the same way, add MEXICO to the COUNTRY list of values in the same way, and so on.

Modifying Configuration Parameters for Oracle Data Quality Address Validation Server

The ssadq_cfgasm.xml file contains the global configuration parameters for Oracle Data Quality Address Validation Server. You must modify ssadq_cfgasm.xml in order to map Siebel CRM business components (<bc_field>) to data types supported by IIR (<data_type>). The following table lists the data types that are supported by IIR. For an example ssadq_cfgasm.xml file, see Sample Configuration Files.

Data Type Meaning

Nobility

For example: Lord, Sir, and so on.

Title

For example: Mr. Mrs, Dr, and so on.

FName

First name

MName

Middle name

LName

Last name

Function

For example: Manager, Director, and so on.

Building

Building name

SubBuilding

Sub building name

HouseNumber

House number

Street1

Street address line 1

Street2

Street address line 2

POBox

Post office box number

DeptLocality

For example: URB, Colonia.

Locality

For example: County

Province

For example: State

Zip

Postal code

Country

Country name

In addition to providing field mappings, the ssadq_cfgasm.xml file defines a standardization operation (<std_operation>) for each field, which controls how the field will be standardized.

The following table lists the standardization operations that are supported by IIR.

Standardization Operation Description

Upper

Convert text to upper case.

Lower

Convert text to lower case.

Camel

Convert text to camel case (upper case for first letter only)

Use the following procedure to modify configuration parameters for Oracle Data Quality Address Validation Server. This task is a step in Process of Installing the Oracle Data Quality Address Validation Server.

To modify configuration parameters for Oracle Data Quality Address Validation Server

  1. Open the ssadq_cfgasm.xml file in a text editor.

  2. Use the following syntax to map a Siebel CRM business component field name to a supported IIR data type: 

    <Parameter>
 <datacleanse_mapping>
    <mapping>
        <bc_field>AccountName</bc_field>
        <data_type>Organization</data_type>
        <std_operation>Camel</std_operation>
    </mapping>
 </datacleanse_mapping>
</Parameter>

    This example maps the Siebel CRM business component field name AccountName to the supported IIR Organization data type, and defines camel as the standardization operation.

    Repeat this step as required.

  3. Save the ssadq_cfgasm.xml file and copy it to the SDQConnector folder on Siebel Server for the changes to take effect:

    siebsrvr/SDQConnector

  4. To integrate with the Informatica Address Doctor Version 5 postal directories, add the following tag to the ssadqasm_cfg.xml file located in siebelserver/SDQConnector:

    <Parameter>
    <asm_version>V5</asm_version>
</Parameter>

When enabling data cleansing, you must add the country LOV value according to how the country is returned by the postal directory after cleansing. For example, if Country USA looks like “UNITED STATES�? post cleansing, then you must add the LOV value UNITED STATES to the Country picklist.

Note: An upgrade from Informatica Identity Resolution 2.7.04 to 2.8.07 should be treated like a new setup. In such cases, install Informatica Identity Resolution 2.8.07 on a new port, create a new system, perform the initial load, start the synchronizer to make it operational, and then delete the current Informatica Identity Resolution 2.7.04 setup.

Acquiring the License Key and Postal Directories for Oracle Data Quality Address Validation Server

The Oracle Data Quality Address Validation Server is installed as part of Informatica Identity Resolution installation. All content and license keys for the postal directories, however, must be purchased directly from Informatica Address Doctor. Subsequent updates and support for the postal directories is provided by Informatica Address Doctor also.

Address Doctor postal directories are currently certified in USA, Canada, and Australia. Address Doctor provides coverage for over 240 countries but not all coverage is the same. Address Doctor assigns a grade (A+, A, B) for each country's coverage. As this grade can change, it is recommended that you check the Address Doctor Web site at the following address for the latest grades:

http://www.addressdoctor.com/en/countries_data/countries5.asp

License keys, once purchased, provide a 12-month subscription to the postal directories and restrict the use of address validation to the purchased countries or territories. The maximum duration of the license key is 12 months.

A postal directory is ultimately owned and managed by the country or territory that provides the postal data, and hence is managed differently across providers. You can keep an eye on postal directory updates by:

  • Verifying the postal reference data on the Address Doctor Web site.

  • Reviewing any update emails that Address Doctor sends.

Use the following procedure to acquire the license key and postal directories for Oracle Data Quality Address Validation Server. This task is a step in Process of Installing the Oracle Data Quality Address Validation Server.

To acquire the license key and postal directories for Oracle Data Quality Address Validation Server

  1. Send the following information to Informatica Address Doctor using the email address oracleAV@informatica.com:

    • Full customer contact information, including: company name, contact name, email address, billing address, telephone, and fax numbers.

    • The countries, regions, or territories for which you require the license and postal reference data.

    • The platform on which the Oracle Data Quality Address Validation Server is deployed (for example, Oracle Solaris 10 or Windows 32 bit).

    • The underlying Informatica product and version (for example, Informatica Identity Resolution version 2.7 or 2.8).

  2. When you have purchased the license key and postal directories for Oracle Data Quality Address Validation Server:

    • Informatica Address Doctor emails the license key information to the named contact.

    • Informatica Address Doctor support emails the credentials to download the reference key to the named contact.

      You need this information to install and access the postal directories as described in Installing Oracle Data Quality Address Validation Server.

Installing the Universal Connector

As a preliminary step in installing data quality software, including the Universal Connector software, you must use the Siebel Image Creator utility and Siebel CRM media files (from your DVD or FTP site) to create a network-based Siebel CRM installation image. For installation instructions, including instructions on creating the installation image, see Siebel Installation Guide for the operating system you are using.

To use the Universal Connector, you must install the Data Quality Connector component when running the InstallShield wizard for Siebel Server Enterprise. For information about installing the Universal Connector on a network, see Installing Third-Party Application Software for Use with the Universal Connector.

Note: If using the Data Quality Applications product media pack on Oracle Software Delivery Cloud to install data quality products, then the Universal Connector component is installed as part of that installation process.

Installing Third-Party Application Software for Use with the Universal Connector

Unlike most other third-party software, you must install third-party software for use with the Universal Connector after you install Siebel CRM. Install the third-party software in the SDQConnector directory where your Siebel CRM are installed; that is, the Siebel_Server_root/SDQConnector directory. See the documentation provided by the third-party vendor for instructions.

Installing Third-Party Data Cleansing Files for Use with the Universal Connector

To perform data cleansing, the third-party vendor software usually needs a set of files for standardization and data cleansing. For information about specifying the location of such files, see the documentation provided by the third-party vendor.

Universal Connector Libraries

The Universal Connector uses standard Siebel CRM business services for data matching and cleansing. These business services call a generalized adapter that can communicate with an external data quality application through a set of library files.

The names of the shared libraries are vendor-specific, but must follow naming conventions as described in Vendor Libraries.

The Siebel CRM installation process copies these DLL or shared library files to a location that depends on the operating system you are using, as shown in the following table.

Does Vendor Support Multiple Languages? DLL Storage Locations (Windows) Shared Library Storage Locations (UNIX)

No

For Siebel Server:

Siebel_Server_root\bin\

For Developer Web Client:

Client_root\bin\

For Siebel Server:

Siebel_Server_root/lib

Yes

For Siebel Server:

Siebel_Server_root\bin\langua
ge_code

For Developer Web Client:

Client_root\bin\language_code

where language_code is the appropriate language code, such as ENU for U.S. English.

For Siebel Server:

Siebel_Server_root/lib/
language_code
Note: The DLLs or shared libraries for each vendor can be specific to certain operating systems or external product versions, so it is important that you confirm with your vendor that you have the correct files installed on your Siebel Server.

The Universal Connector requires that you install third-party applications on each Siebel Server that has the object managers enabled for data quality functionality. If you plan to test real-time mode using a Siebel Developer Web Client, you must install the third-party Data Quality software on that computer, as well.

Note: When installing data quality products using the Data Quality Applications product media pack on Oracle Software Delivery Cloud, the DLL or shared library files are copied to a location that depends on the operating system you are using.