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

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 (Informatica Identity Resolution). 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

        For more information about the format of the rulebase name, see the relevant documentation included in Siebel Business Applications Third-Party Bookshelf in the product media pack on Oracle Software Delivery Cloud.

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

      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.

      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