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  >

Initial Loading of Siebel Data into ODQ Matching Server Tables

This procedure is a step in Process of Setting Up ODQ Matching Server for Data Matching. To initially load your Siebel application data into ODQ Matching Server (IIR) tables, complete the steps in the following procedure.

To initially load Siebel application data into ODQ Matching Server tables

1. In the Siebel application:
   1. Log in as administrator and navigate to Administration - Runtime Events screen, then the Action Sets view.
   2. Query in the Name field for ISSLoad* and make sure that all action sets are active. If some are not:
      • Activate them by selecting the Active check box for each action set.
      • Then reload run-time events by clicking Menu, and selecting Reload Runtime Events.
   3. Navigate to Administration - Data Quality screen, then the Data Quality Settings view, and modify any one of the records (for example, increase the Match Threshold value) to trigger the export data process.

      This action triggers the run-time events to export account, contact, and prospect records from the Siebel application into xml data files. Depending on the number of records in your database, this process can take some time so wait until the process completes.

      NOTE:  The location of the XML data file is specified by the ISS Set File Name value of each ISSLoad * action set.

   4. Copy the exported files to the following IIR folder location:

      <Drive>:\ids\iss2704s\ids\data

      This is where the Load IDT process gets the files and loads them into IIR.

      NOTE:  If the Siebel application and IIR are installed on the same box, then there is no need to copy the exported files to the IIR folder as the export process places the files directly in the IIR folder.

   5. Navigate back to Administration - Runtime Events, then the Action Sets view, and:
      • Deactivate all ISSLoad* action sets.
      • Then reload run-time events by clicking Menu, and selecting Reload Runtime Events.
   6. Navigate back to Administration - Data Quality, then the Data Quality Settings view, and reset Match Threshold to it original value.

      This ensures that this action will not be triggered every time a data quality setting is modified.

2. In Informatica Identity Resolution:
   1. Start the IIR server by navigating to:

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

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

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

   3. If not already done so, create a new system in IIR using SiebelDQ.sdf. 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) 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.

      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. Load IIR with the data files exported from the Siebel application by clicking the System/Load IDT button.