Siebel Data Quality Administration Guide > Universal Connector API >

Vendor Libraries

Vendors must follow these rules for their DLLs or shared libraries:

• The libraries must be thread-safe. A library can support multiple sessions by using different unique session IDs.
• The libraries must support UTF-16 (UCS2) as the default Unicode encoding.
• If there is a single library for all supported languages, the libraries must be named as follows:
  • BASE.dll (on Windows)
  • libBASE.so (on AIX and Oracle Solaris)
  • libBASE.sl (on HP-UX)

    where BASE is a name chosen by the vendor. If a vendor has many solutions for different types of data, they can use different base names for different libraries.

• If there are separate libraries for different languages, the library name must include the appropriate language code. For example, for Japanese (JPN), the libraries must be named as follows:
  • BASEjpn.dll (on Windows)
  • libBASEjpn.so (on AIX and Oracle Solaris)
  • libBASEjpn.sl (on HP-UX)

The Siebel application loads the libraries from the locations described in Table 11.

The mapping of Siebel application field names to vendor field names is stored as values of the relevant Business Component user properties in the Siebel CRM repository. Storage of these field values is mandatory.

Any other vendor-specific parameter required (for example, port number) for the vendor's library must be stored outside of Siebel CRM.

Terminology

The following terms are used in this appendix:

• Driver record. The record the user just entered in real time or the record for which duplicates have to be found.
• Candidate records. The records that potentially match the driver record.
• Duplicate records. The subset of candidate records that actually match the driver record after the matching process.
• Master record. The record for which data matching was performed.