Siebel Data Quality Administration Guide > Data Quality Configuration Options >

Configuring the Siebel Data Quality Universal Connector

This section provides procedures for configuring the Siebel Data Quality Universal Connector. For more information about these procedures, see the specific topic discussed elsewhere in this chapter.

Three processes are needed to support data quality features using the Siebel Data Quality Universal Connector. These processes are divided into the following three phases:

Each phase contains a set of instructions or steps. Perform the phases and the steps in the order provided.

NOTE:  These processes do not cover vendor-specific configuration. You should work with Siebel-certified alliance partners to enhance data quality features for your applications. For more information, contact Siebel Technical Support.

Phase 1: Creating a Connector Configuration

The connector configuration is done in the Business Service user property.

To support:

To configure a connector

  1. Determine vendor name and vendor's solution names for the connector.

    2. User Property:
    VendorName Connector x
    Property Value:
    SolutionName
    where x is a number starting from 1

    NOTE:  A vendor may have more than one solution for either data cleansing or data matching.

  2. For each solution, you need to configure the following attributes:

    3. User Property:
    SolutionName Attribute - Library Base Name
    User Property:
    SolutionName Attribute - Language Dependent
    User Property:
    SolutionName Parameter x
    where x is a number starting from 1.

    TIP:  A solution may have more than one parameter.

    The Library Base Name tells the Siebel application how to load the vendor's dynamic-link library (DLL). The vendors follow Siebel naming convention to build the DLLs. They first pick a base name for their libraries, for instance BASE. Then, the Windows DLL must be called BASE.dll. In AIX and Solaris, the libraries must be called libBASE.so. In HP-UX the libraries must be called libBASE.sl. The Siebel application loads the DLL from the \bin subdirectory under the Siebel installation directory ($SIEBEL_ROOT/bin) for Windows or the /lib directory for UNIX.

For information about the preconfigured attributes for the Firstlogic connectors, see Preconfigured Universal Connector Properties for Firstlogic Applications.

CAUTION:  The Business Service user properties 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 properties must be provided by Siebel Systems and third-party vendors. Usually these values cannot be changed because specific values are required by each software vendor.

Phase 2: Associating the Connector to a Business Component

In this phase you associate the connector to a Siebel business component.

To associate the connector to a business component

  1. Use one of the following business component user properties to associate a connector to a business component:
  2. Configure a user property to assign a type name to your business component.

    3. For example, assign SolutionName Type to the user property.

    NOTE:  This user property is not required, however it does provide a way for the DLL to recognize the type of records the Siebel application passes to it. The vendor can require this type as a predefined keyword. If it is not required as a keyword, developers can instead make the type a unique word so that the DLL identifies the type change when switching from one type to another in Siebel eBusiness Applications.

For information about the preconfigured settings, see Preconfigured Universal Connector Properties for Firstlogic Applications.

Phase 3: Mapping Connector Fields to Business Component Fields

In this phase you map the connector fields to Siebel business component fields.

To map connector fields to business component fields

  1. Define the data cleansing fields in the business component user properties as follows:

    2. User Property:
    SolutionName DataCleansing Field x
    Value:
    "Siebel Field", "Vendor Input Field", "Vendor output field"
    or
    Value:
    "Siebel Field", "Vendor Input Field"
    where x is the number starting from 1.

    TIP:  You can have more than one field mapping.

    NOTE:  If you do not specify the Vendor output field, the Siebel application does not update the cleansed value to the field. In this case. this field is used only for input information. For example, in the Siebel application, the address records may have a predefined LOV (list of values) of State Names and Country Names, so that users can pick a value from the picklist. When you configure these fields as data cleansing fields, you do not want them updated. Instead, you should let the Siebel application pass these fields to the vendor DLL to make the cleansing more accurate.

  2. Define the deduplication fields as follows:

    3. User Property:
    SolutionName DeDuplication Field x
    Value:
    "Vendor Input Field", "Siebel Field"
    where x is the number starting from 1.

    TIP:  You can have more than one field mapping.

NOTE:  You should contact the specific vendor for the list of fields they support for data cleansing and data matching.


 Siebel Data Quality Administration Guide 
 Published: 15 May 2003