5Configuring Data Quality with Universal Connector

Configuring Data Quality with Universal Connector

This chapter describes the data quality configuration that you can perform for Siebel CRM and Oracle Customer Hub. It covers the following topics:

• Data Quality Configuration Overview

• Installing the Universal Connector

• Process of Configuring New Data Quality Connectors

• Configuring Vendor Parameters

• Mapping of Vendor Fields to Business Component Fields

• Configuring the Windows Displayed in Real-Time Data Matching

• Configuring the Mandatory Fields for Fuzzy Query

• Data Quality User Properties

• Optimizing Data Cleansing Performance

• Optimizing Data Matching Performance

Note: You must be familiar with Siebel Tools before performing some of the data quality configuration tasks. For more information about Siebel Tools, see Using Siebel Tools and Configuring Siebel Business Applications.

Data Quality Configuration Overview

The following table summarizes the data quality configuration that you can perform for Siebel CRM and Oracle Customer Hub.

Table Data Quality Configuration Options

Type	Configuration	See...
Generic data quality configuration for all data quality products	Configure new connectors for data matching and data cleansing for the Universal Connector	Process of Configuring New Data Quality Connectors
	Configure vendor parameters. You can configure the parameters for each of the software vendors.	Configuring Vendor Parameters
	Configure field mappings for business components. You can change or add field mappings.	Mapping of Vendor Fields to Business Component Fields
	Configure the windows displayed in real-time data matching	Configuring the Windows Displayed in Real-Time Data Matching
	Configure the mandatory fields for fuzzy search.	Configuring the Mandatory Fields for Fuzzy Query
Oracle Data Quality Matching Server Configuration	Data Matching	Configuring Oracle Data Quality Matching Server
		Configuring a New Field for Real-Time Data Matching
		Loading Data Incrementally
Oracle Data Quality Address Validation Server Configuration	Data Cleansing	Configuring Siebel Business Applications for the 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 Business Applications. Install the third-party software in the SDQConnector directory where your Siebel Business Applications 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 About the Universal Connector API.

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.

Table Storage Locations for Universal Connector Library Files by Operating System

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.

Process of Configuring New Data Quality Connectors

You can define your own connectors for data matching and data cleansing for the Universal Connector. To configure new data quality connectors, perform the following tasks:

1. Registering New Data Quality Connectors

2. Configuring Business Components and Applets for Data Matching and Data Cleansing

Note: These processes do not cover vendor-specific configuration. You must work with Oracle-certified alliance partners to enhance data quality features for your applications.

Registering New Data Quality Connectors

Data Quality connector definitions are configured in the Third Party Administration view. You can specify one external application for data matching and a different application for data cleansing for the Universal Connector. You do this by setting the correct input values for each external application.

Note: The vendor parameters in the Siebel application are specifically designed to support multiple vendors in the Universal Connector architecture without the need for additional code. The values of these parameters must be provided by third-party vendors. Typically, these values cannot be changed because specific values are required by each software vendor. For more information about the values to use, see the installation documentation provided by your third-party vendor.

The Deduplication and Data Cleansing business services include a generalized adapter that communicates with the external data quality application through a set of dynamic-link library (DLL) or shared library files.

The DLL Name setting in the Third Party Administration view tells the Siebel application how to load the DLL or shared library. The names of the libraries are vendor-specific, but must follow naming conventions as described in About the Universal Connector API. The Siebel application loads the libraries from the locations described in Levels of Enabling and Disabling Data Cleansing and Data Matching.

Use the following procedure to register a data quality connector. This topic is a step in Process of Configuring New Data Quality Connectors.

To register a data quality connector

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, create a new record and complete the necessary fields, as shown in the following table.

   Name	Library Name
   The name of the vendor. For a data matching connector, the name must match the value specified in the server parameter DeDuplication Data Type. For a data cleansing connector, the name must match the value specified in the server parameter Data Cleansing Type.	The name of the vendor DLL or shared library.

Configuring Business Components and Applets for Data Matching and Data Cleansing

This topic describes how to configure business components and applets, whether existing ones or new ones you create, for data matching and data cleansing.

You can configure existing business components or create additional business components for data matching for the Matching Server and for data matching and data cleansing for the Universal Connector.

Typically, you configure existing business components; however, you can create your own business components to associate with connector definitions. For information about how to create new business components and define user properties for those components, see Configuring Siebel Business Applications.

Note: You must base new business components you create only on the CSSBCBase class to support data cleansing and data matching, or make sure that the business component uses a class whose parent is CSSBCBase. This class includes the specific logic to call the DeDuplication and Data Cleansing business services.

To configure business components for data matching and data cleansing, complete the steps in the following procedure. This topic is a step in Process of Configuring New Data Quality Connectors.

To configure business components for data matching and cleansing

1. Associate the business component with a connector.

   This includes configuring the vendor parameters shown in the following table.

   	Name	Value
   For data matching	Business_component_name DeDup Record Type	Business_component_name
   For data matching	Business_component_name Token Expression	Consult the vendor for the value of this field. Note: Applies to the Universal Connector, where key generation is carried out by the Siebel application.
   For data matching	Business_component_name Query Expression	Consult the vendor for the value of this field. Note: Applies to the Universal Connector, where key generation is carried out by the Siebel application.
   For data matching	Parameter 1	"global", "iss-config-file", "ssadq_cfg.xml" Note: Applies to the Oracle Data Quality Matching Server only, where match keys are generated by the Oracle Data Quality Matching Server.
   For data cleansing	Business_component_name DataCleanse Record Type	Business_component_name

2. Configure the field mappings for each business component and operation.

3. Create a DeDuplication Results business component and add it to the Deduplication business object.

4. Configure an applet as the DeDuplication Results List Applet.

5. Configure Duplicate views and add them to the Administration - Data Quality screen.

6. Add the business component user properties as shown in the following table.

   Property	Value
   DeDuplication Results BusComp	The buscomp that you created in Configuring Business Components and Applets for Data Matching and Data Cleansing.
   DeDuplication Results List Applet	The applet that you created in Configuring Business Components and Applets for Data Matching and Data Cleansing.

7. Add a field called Merge Sequence Number to the business component and a user property called Merge Sequence Number Field.

Configuring Vendor Parameters

For each of the third-party software vendors that data quality uses for data cleansing or data matching, you can configure the vendor parameters that the Siebel application passes to the vendor software. You configure the vendor parameters in the Administration - Data Quality screen, Third Party Administration view, which also contains the DLL or shared library name for each vendor.

There are preconfigured vendor parameters for the Universal Connector with Oracle Data Quality Matching Server and Oracle Data Quality Address Validation Server as examples.

To configure vendor parameters

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the Vendor Parameters view tab.

4. In the Vendor Parameters List, create new records as required, or configure the values of existing vendor parameters.

Mapping of Vendor Fields to Business Component Fields

For each vendor who supports data cleansing or data matching, there are field mappings that specify:

• The fields that are used in data cleansing and data matching

• The mapping between the Siebel application field names and the corresponding vendor field names.

There are mappings for each supported business component and data quality operation (DeDuplication and Data Cleansing). There are preconfigured field mappings for the Oracle Data Quality Matching Server Connector, see Preconfigured Field Mappings for Oracle Data Quality Matching Server.

You can configure the field mappings for a business component to include new fields or modify them to map to different fields. There might also be additional configuration required for particular third-party software.

Note: You must contact the specific vendor for the list of fields that the vendor supports for data cleansing and data matching and to understand the effect of changing field mappings.

Related Topics

Mapping Data Matching Vendor Fields to Siebel Business Components

Adding a Field Mapping for Data Matching

Mapping Data Cleansing Vendor Fields to Siebel Business Component Fields

Mapping Data Matching Vendor Fields to Siebel Business Components

This topic explains how to map data matching vendor fields to Siebel business component fields.

To map a data matching vendor field to a Siebel business component field

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the BC Vendor Field Mapping view tab.

4. In the BC Operation list, select the record for the required business component and the DeDuplication operation. The field mappings are displayed in the Field Mapping list.

5. In the Field Mapping list enter the required values for Business Component Field and Mapped Field.

Adding a Field Mapping for Data Matching

In addition to the preconfigured fields that are used in data matching, you can configure your data quality implementation to inspect certain additional fields during data matching, such as a date of birth field for Contacts, or a D-U-N-S number field for Accounts.

For the Universal Connector, if the key token expression changes, you must regenerate match keys. Therefore, if you are adding a new field and the new field is added to the token expression, you must generate the match keys.

The following procedure describes how to add a field mapping.

To add a field mapping for data matching

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the BC Vendor Field Mapping view tab.

4. In the BC Operation list, select the record for the required business component and operation

   • For example, to include a date of birth as a matching criterion, select the record for Contact and DeDuplication.

   • For example, to include a D-U-N-S number as a matching criterion, select the record for Account and DeDuplication.

   The field mappings are displayed in the Field Mapping list.

5. In the Field Mapping list, create a new record and complete the necessary fields as in the example shown in the following table.

   Business Component Field	Mapped Field
   Birth Date	Contact.Birth Date
   DUNS Number	Account.DUNS Number

6. If required, modify the corresponding real-time and batch mode data flows to incorporate the new field so that data quality considers the new field during data matching comparisons.

Mapping Data Cleansing Vendor Fields to Siebel Business Component Fields

Data cleansing is triggered when a record is saved after a field that is defined as an active data cleansing field is updated.

Default settings are preconfigured for the Account, Contact, Prospect, and Business Address business components to support integration with Oracle Data Quality Address Validation Server, but you can configure the mappings to your requirements or to support integration to other vendors.

Note: For Siebel Industry Applications, the CUT Address business component is enabled for data cleansing rather than the Business Address business component.

For example the following are active data cleansing fields for the Contact business component:

• Last Name

• First Name

• Middle Name

• Job Title

Tip: Only fields that are preconfigured as data cleansing fields in the vendor properties trigger real-time data cleansing when they are modified.

To map a data cleansing vendor field to a Siebel business component field

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the BC Vendor Field Mapping view tab.

4. In the BC Operation list, select the record for the required business component and Data Cleansing operation.

   The field mappings are displayed in the Field Mapping list.

5. In the Field Mapping list enter the required values for Business Component Field and Mapped Field.

Configuring the Windows Displayed in Real-Time Data Matching

In real-time data matching when the user saves a new account, contact, or prospect record, the Siebel application displays the duplicate records in a window.

You can change the name of the windows that are displayed, and you can specify that a window is displayed for some other applets. This can be a similar applet to the Contact List, Account List, or List Mgmt Prospective Contact List applet or a customized applet. Both list and detail applets are supported, as long as they are not child applets.

For more information about configuring the windows displayed in real-time data matching, see the following procedures:

• Changing a Window Name

• Adding a Deduplication Window for an Applet

• Configuring a Real-Time Deduplication Window for Child Applets

Changing a Window Name

Use the following procedure to change the name of a window displayed.

To change the name of the window displayed

1. Login to Web Tools, open workspace.

2. In the Object Explorer, select the Applet, and then select the applet of interest, for example, Contact List Applet.

3. In the Object Explorer, select Applet User Prop.

4. Select the DeDuplication Results Applet user property and change its value as required.

5. Save the changes and submit the workspace for delivery.

Adding a Deduplication Window for an Applet

Use the following procedure to add a Deduplication Window for an applet.

To add a Deduplication Window for an applet

1. Login to Web Tools, open workspace.

2. In the Object Explorer, select the Applet object, and then select the applet of interest, for example, Account Form Applet

3. In the Object Explorer, select Applet User Prop.

4. Add a new record with the following settings:

   • Name. DeDuplication Results Applet

   • Value. DeDuplication Results (Account) List Applet

5. Save the changes and submit the workspace for delivery.

Configuring a Real-Time Deduplication Window for Child Applets

Configuration changes are required in Siebel Tools to set up the real-time Deduplication Window on child applets.

To configure the real-time Deduplication Window for a child applet, an applet user property must be added to the respective applet where the Deduplication Window is required. For example, to generate a window from the Account Contact view, add the applet user property to Account Contact List Applet, as described in the following procedure.

To configure the real-time Deduplication Window for a child applet (Account Contact view)

1. In Web Tools, open the workspace and query for the following applet:

   Account Contact List Applet

2. Add the following user property to this applet:

   • Name. DeDuplication Results Applet

   • Value. DeDuplication Results (Contact) List Applet

3. Save the changes and submit the workspace for delivery.

Configuring the Mandatory Fields for Fuzzy Query

For a business component you can configure the mandatory fields for fuzzy query, or query. These fields must include values for the Siebel application to use in Fuzzy Query mode. Identifying Mandatory Fields for Fuzzy Query shows the preconfigured mandatory fields that Oracle provides.

Use the following procedure to configure the mandatory fields for a business component.

To configure the fields that are mandatory for fuzzy query

1. Login to Web Tools, open the workspace.

2. In the Object Explorer, expand Business Component and then select the business component of interest in the Business Components pane.

3. In the Object Explorer, select Business Component User Prop.

   Tip: If the Business Component User Prop object is not visible in the Object Explorer, you can enable it in the Development Tools Options dialog box (View, Options, Object Explorer). If this is necessary, you must repeat Step 2 of this procedure.

4. In the Business Component User Properties pane, select Fuzzy Query Mandatory Fields, and enter the required field names in the Value column.

Data Quality User Properties

This topic provides information about data quality user properties, including deduplication and data cleansing business service user properties. Information about the following is included in this topic:

• Account - Business Component User Properties

• Contact - Business Component User Properties

• List Mgmt Prospective Contact - Business Component User Properties

• DeDuplication - Business Service User Properties

• Data Cleansing - Business Service User Properties

• DQ Sync Services - Business Service User Properties

• ISS System Services - Business Services User Properties

Account - Business Component User Properties

Data quality uses the Account business component user properties listed in the following table.

Table Account - Business Component User Properties

Name	Value	Comment
DQ Business Object	DQ Vendor	These business component user properties for Account specify the business object and business component used in the data quality Administration views in Siebel business application.
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Mapping Config BC	DQ Mapping Config
DQ Vendor Info BC	DQ Vendor Info
DQ Key BusComp	Account Key	For the Universal Connector, DQ Key BusComp is used to specify the Name of the buscomp that stored the deduplication key generated in Siebel.
DeDuplication Key BusComp	DeDuplication - SSA Account Key	For SDQ Matching Server, DeDuplication Key BusComp is used to specify the Name of the buscomp that stored the dedup key generated by SSA.
DeDuplication Results BusComp	DeDuplication Results (Account)	Specifies the Name of the buscomp that will store the returned duplicated record data.
DeDuplication Results List Applet	DeDuplication Results (Account) List Applet	Specifies the Name of the pick applet used to prompt the user to resolve duplicates.
Fuzzy Query Mandatory Fields	"Name"	Specifies the mandatory fields for Fuzzy Query; that is, the query fields that must include values so that the Siebel application can use the fuzzy query mode.
DQ Associate BC 1	CUT Address: Address Id	Specifies the Name of the child MVG buscomp, and the field in the parent buscomp that comes from this MVG. This business component applies to the data quality Multiple Address Deduplication feature. Note: MVG stands for multiple value group.

For each field used in Multiple Address Deduplication that comes from the child MVG buscomp, a field user property is specified to map it to the child business component field, as shown in the following table.

Table Account Business Component - Field User Properties for Multiple Address Deduplication

Field	Name	Value
Primary Account City	DQ Associate BC Map	DQ Associate BC 1: City
Primary Account Country	DQ Associate BC Map	DQ Associate BC 1: Country
Primary Account Postal Code	DQ Associate BC Map	DQ Associate BC 1: Postal Code
Primary Account State	DQ Associate BC Map	DQ Associate BC 1: State
Primary Account Street Address	DQ Associate BC Map	DQ Associate BC 1: Street Address

Contact - Business Component User Properties

Data quality uses the Contact business component user properties listed in the following table.

Table Contact - Business Component User Properties

Name	Value	Comment
DQ Business Object	DQ Vendor	These business component user properties for Contact specify the business object and business component used in the data quality Administration views in Siebel business application.
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Mapping Config BC	DQ Mapping Config
DQ Vendor Info BC	DQ Vendor Info
DQ Key BusComp	Contact Key	For the Universal Connector, DQ Key BusComp is used to specify the Name of the buscomp that stored the deduplication key generated in Siebel.
DeDuplication Key BusComp	DeDuplication - SSA Contact Key	For SDQ Matching Server, DeDuplication Key BusComp is used to specify the Name of the buscomp that stored the dedup key generated by SSA.
DeDuplication Results BusComp	DeDuplication Results (Contact)	Specifies the Name of the buscomp that will store the returned duplicated record data.
DeDuplication Results List Applet	DeDuplication Results (Contact) List Applet	Specifies the Name of the pick applet used to prompt the user to resolve duplicates.
Fuzzy Query Mandatory Fields	"Last Name", "First Name"	Specifies the mandatory fields for Fuzzy Query; that is, the query fields that must include values so that the Siebel application can use the fuzzy query mode.
DQ Associate BC 1	CUT Address: Personal Address Id	Specifies the Name of the child MVG buscomp, and the field in the parent buscomp that comes from this MVG. This business component applies to the data quality Multiple Address Deduplication feature. Note: MVG stands for multiple value group.

For each field used in Multiple Address Deduplication that comes from the child MVG buscomp, a field user property is specified to map it to the child business component field, as shown in the following table.

Table Contact Business Component - Field User Properties for Multiple Address Deduplication

Field	Name	Value
Primary Personal City	DQ Associate BC Map	DQ Associate BC 1: City
Primary Personal Country	DQ Associate BC Map	DQ Associate BC 1: Country
Primary Personal Postal Code	DQ Associate BC Map	DQ Associate BC 1: Postal Code
Primary Personal State	DQ Associate BC Map	DQ Associate BC 1: State
Primary Personal Street Address	DQ Associate BC Map	DQ Associate BC 1: Street Address

List Mgmt Prospective Contact - Business Component User Properties

Data quality uses the List Mgmt Prospective Contact business component user properties listed in the following table.

Table List Mgmt Prospective Contact - Business Component User Properties

Name	Value	Comment
DQ Business Object	DQ Vendor	These business component user properties for List Mgmt Prospective Contact specify the business object and business component used in the data quality Administration views in Siebel business application.
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Mapping Config BC	DQ Mapping Config
DQ Vendor Info BC	DQ Vendor Info
DQ Key BusComp	Prospect Key	For the Universal Connector, DQ Key BusComp is used to specify the Name of the buscomp that stored the deduplication key generated in Siebel.
DeDuplication Key BusComp	DeDuplication - SSA Prospect Key	For SDQ Matching Server, DQ Key BusComp is used to specify the Name of the buscomp that stored the dedup key generated by SSA.
DeDuplication Results BusComp	DeDuplication Results (Prospect)	Specifies the Name of the buscomp that will store the returned duplicated record data.
DeDuplication Results List Applet	DeDuplication Results (Prospect) List Applet	Specifies the Name of the pick applet used to prompt the user to resolve duplicates.
Fuzzy Query Mandatory Fields	"Last Name", "First Name"	Specifies the mandatory fields for Fuzzy Query; that is, the query fields that must include values so that the Siebel application can use the fuzzy query mode.

DeDuplication - Business Service User Properties

Data quality uses the DeDuplication business service user properties listed in the following table.

Table DeDuplication - Business Service User Properties

Name	Value	Comment
DQ Vendor BO	DQ Vendor	These business service user properties for DeDuplication specify the business object and business component used in the data quality Administration views in Siebel business application.
DQ Vendor BC	DQ Vendor Info
DQ Mapping Config BC	DQ Mapping Config
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Vendor Param BC	DQ Vendor Parameter

Data Cleansing - Business Service User Properties

Data quality uses the Data Cleansing business service user properties listed in the following table.

Table Data Cleansing - Business Service User Properties

Name	Value	Comment
DQ Vendor BO	DQ Vendor	These business service user properties for Data Cleansing specify the business object and business component used in the data quality Administration views in Siebel business application.
DQ Vendor BC	DQ Vendor Info
DQ Mapping Config BC	DQ Mapping Config
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Vendor Param BC	DQ Vendor Parameter

DQ Sync Services - Business Service User Properties

The DQ Sync Services business service is used when synchronizing data between the Siebel application and Oracle Data Quality Matching Server (Informatica Identity Resolution). The Siebel application uses it to insert records into the NSA table belonging to the Oracle Data Quality Matching Server.

Data quality uses the DQ Sync Services business service user properties listed in the following table.

Table DQ Sync Services - Business Service User Properties

Name	Value	Comment
Account Integration Object Name	SyncAccount	These business service user properties specify the Integration Objects and Components used by the Siebel application to synchronize with Oracle Data Quality Matching Server (Informatica Identity Resolution).
Account Address Component Name	Account_Business Address
Contact Integration Object Name	SyncContact
Contact Address Component Name	Contact_INS Personal Address
Prospect Integration Object Name	SyncProspect
ISS System Name	siebeldq	These business service user properties specify the default Informatica Identity Resolution system name and IDT table names.
Account IDT Name	IDS_01_IDT_ACCOUNT
Contact IDT Name	IDS_01_IDT_CONTACT
Prospect IDT Name	IDS_01_IDT_PROSPECT
Account Record Length	1090	These business service user properties specify the Account record fields, data type, and length.
Account_DeDupFlds	Name|DUNS Number|Id
Account_DataType	W|W|C
Account_ExtLen	200|120|30
Contact Record Length	1850	These business service user properties specify the Contact record fields, data type, and length.
Contact_DeDupFlds	Birth Date|Cellular Phone #|Email Address|First Name Last Name|Home Phone #|Middle Name|Account|Id|Social Security Number|Work Phone #
Contact_DataType	W|W|W|W|W|W|W|C|W|W
Contact_ExtLen	120|120|120|200|120|200|200|30|120|120
Prospect Record Length	1770	These business service user properties specify the Prospect record fields, data type, and length.
Prospect_DeDupFlds	Account|Cellular Phone #|City|Country|Email Address|First Name Last Name|Home Phone #|Middle Name|Postal Code|Social Security Number|State|Street Address|Work Phone #|Id
Prospect_DataType	W|W|W|W|W|W|W|W|W|W|W|W|W|C
Prospect_ExtLen	200|120|120|60|120|200|120|200|40|120|40|200|200|30
Account_Business Address_DeDupFlds	City|Country|Postal Code|State|Street Address|Address Id	These business service user properties specify the Account Business Address record fields, data type, and length.
Account_Business Address_DataType	W|W|W|W|W|C
Account_Business Address_ExtLen	200|120|120|40|200|60
Contact_INS Personal Address_DeDupFlds	INS Personal City|INS Personal Country|INS Personal Postal Code|INS Personal State|INS Personal Street Address|INS Personal Address Id	These business service user properties specify the Contact INS Personal Address record fields, data type, and length.
Contact_INS Personal Address_DataType	W|W|W|W|W|C
Contact_INS Personal Address_ExtLen	120|40|40|40|200|60
Filter Characters	<Enter characters separated by a single space> Note: ^ (code separator)| (code separator)\r (carriage return)\n (new line)\t (horizontal tab)\f (form feed)	This business service user property is used to specify any special characters that need to be removed from data sent to the Oracle Data Quality Matching Server. Note: Enter all filter characters separated by a single space. For control characters, enter the ASCII code in the following format: ^nnn (where nnn is the code in decimal).
IIR Server on Little Endian Operating System	Yes	This business service user property is used to specify the Endian of the Operating System where the Oracle Data Quality Matching Server is installed.

ISS System Services - Business Services User Properties

When synchronizing data in Multiple Languages Support mode between the Siebel application and Oracle Data Quality Matching Server (Informatica Identity Resolution), the ISS System Services Business Service is used to specify the system name and database number in Informatica Identity Resolution, where each system corresponds to a specific country or language.

Siebel Data quality uses the ISS System Services business service user properties listed in the following table.

Table ISS System Services - Business Service User Properties

Name	Value	Comment
Account Default System	siebeldq	These business service user properties specify the default Informatica Identity Resolution system name for each support object.
Contact Default System	siebeldq
Prospect Default System	siebeldq
siebeldq	01	These are sample business service user properties. You must enter the actual Informatica Identity Resolution system name and corresponding database number. The default system has a database number of 01.
siebeldq_Denmark	02
siebeldq_UNITED_STATES	03

Related Topic

Configuring Multiple Language Support for Data Matching

Optimizing Data Cleansing Performance

The following are recommendations for achieving good performance with data cleansing when working with large volumes of data:

• Include only new or recently modified records in the batch data cleansing process.

• Cleansing all records in the Siebel database each time a data cleansing is performed can cause performance issues. Include an Object WHERE clause when you submit your batch job, as shown in the following table. Split the tasks into smaller tasks and run them concurrently.

Table Recommended Data Cleansing Object WHERE Clause Solutions

To Cleanse	Use This in Your Object WHERE Clause
Updated records	[Last Clnse Date] < [Updated]
New records	[Last Clnse Date] IS NULL
Updated and new records	[Last Clnse Date] < [Updated] OR [Last Clnse Date] IS NULL

To speed up the data cleansing task for large databases, run batch jobs to cleanse a smaller number of records at a time using an Object WHERE clause. For more information about data cleansing for large batches, see Cleansing Data Using Batch Jobs.

Optimizing Data Matching Performance

The following are recommendations for achieving good performance with data matching when working with large volumes of data:

• Work with a database administrator to verify that the table space is large enough to hold the records generated during the data matching process.

  During the batch data matching process, the information on potential duplicate records is stored in the S_DEDUP_RESULT table as a pair of row IDs of the duplicate records and the match scores between them. The number of records in the results table S_DEDUP_RESULT can include up to six times the number of records in the base tables combined. Remember that:

  • If the base tables contain many duplicates, more records are inserted in the results table.

  • If different search types are used, a different set of duplicate records might be found and will be inserted into the results table.

  • If you use a low match threshold, the matching process generates more records to the results table.

• Remove obsolete result records manually from the S_DEDUP_RESULT table by running SQL statements directly on this table.

  When a duplicate record is detected, the information about the duplicate is automatically placed in the S_DEDUP_RESULT table, whether or not the same information exists in that table. Running multiple batch data matching tasks therefore results in a large number of duplicate records in the table. Therefore, it is recommended that you manually remove the existing records in the S_DEDUP_RESULT table before running a new batch data matching task. You can remove the records using any utility that allows you to submit SQL statements.

  Note: When truncating the S_DEDUP_RESULT table, all potential duplicate records found for all data matching business components are deleted.

• Match performance is slow when the SOH string is set as follows:

  S_POSTN_CON.CON_LAST_NAME = 'SOH' 
  

  Setting the following values improves match performance:

  • Navigate to the Contact Business Component.

  • Add the following user property and value under the Last Name field:

    User Property	Value
    Sort Search Optimization	FALSE

For more information about running batch data matching, see Matching Data Using Batch Jobs.