|
Siebel Data Quality Administration Guide > Configuring Data Quality >
Configuring Multiple Language Support for Data Matching
When using Oracle Data Quality Matching Server for data matching, you can configure different match rules for different languages. This is useful when you have multiple geographical implementations, and for each implementation, you want to use country-specific match rules. The solution involves creating multiple systems in Informatica Identity Resolution, where each system corresponds to a specific country or language. Records with a specific language or country are routed to the corresponding system. Because each system is linked to a population, the respective country-specific population rules are used for matching the records. To use this feature, add the Append BC Record Type Field x vendor parameter for UI entry and the Batch Append BC Record Type Field x vendor parameter for batch mode. This vendor parameters is used to specify a field in the BC, which has the country or language information. The BC name can be Account, Contact, or Prospect where x represents the sequence number. For example: Batch Append Account Record Type Field 1. You must add similar vendor parameters to the Business Service User Property of the ISS System Services business service to represent the IDT number corresponding to the Language. When you create multiple systems in Informatica Identity Resolution, you must specify a unique database number for each system which is used as part of the unique IDT table name in Informatica Identity Resolution. You must enter this same number into the Business Service User Property of the ISS System Services business service for each system. The name of the user property is the same as the name of the system created in Informatica Identity Resolution, and the value of the user property is the database number (for example, see Figure 2).
Figure 2. ISS System Services User Properties
|
NOTE: In order to pick up all the records that belong to the same country when running a data quality batch processing task, it is mandatory to define a search specification (to pick up the records belonging to the same country). You can define a search specification by navigating to the Administration - Server Management screen, then the Jobs view.
This feature can be extended as follows:
- Extended to have different match rules depending on the source of data (for example the Siebel application or other application).
- Extended to have different match rules depending on the mode of data entry (for example, real-time or batch processing mode). The procedure in Configuring Multiple Mode Support for Data Matching describes how to configure multiple mode support for data matching when using the Oracle Data Quality Matching Server for data matching.
Use the following procedure to configure multiple language support for data matching when using the Oracle Data Quality Matching Server for data matching. To configure the Siebel Server for Informatica Identity Resolution multiple language support
- Create systems on the Informatica Identity Resolution server.
- Create separate SDF files for each Country (Population). Informatica provides Standard Populations for most of the countries. Standard Populations are distributed as part of SSA-NAME3 installation and can be copied separately if not selected when installing NAME3 server.
NOTE: For more information about installing populations from the Windows Fix CD and adding populations to an existing installation, see the relevant documentation included in Siebel Business Applications Third-Party Bookshelf in the product media pack on Oracle Software Delivery Cloud.
- Once all populations are in place, check and note the filename of each population, as this is the same name that is used in the SDF file.
You can change System Name and System ID within the system definition file as follows:
system-definition
*=================
NAME= siebeldq_XXXX
ID= sYY
Replace XXXX with Country, and YY with any number between and including 02 and 99. System ID 01 is reserved for Default System. For example, for Japanese population:
filename : siebeldq_Japan.sdf
Population files :
japan.ysp
Changes to SDF file:
system-definition
*=================
NAME= siebeldq_Japan
ID= s05
System ID 01 is reserved for Default System
Replace all occurrences of Population(usa) to Population(japan).
Similar changes are required for each sdf file.
- Configure the ssadq_cfg.xml configuration file in the
<siebsrvr>/SDQConnector folder.
For example, add the following parameter to the ssadq_cfg.xml file:
<Parameter>
<Record_Type>
<Name>Account_Japan</Name>
<System>siebeldq_Japan</System>
<Search>search-org</Search>
<no_of_sessions>25</no_of_sessions>
</Record_Type>
</Parameter>
For a sample ssadq_cfg.xml file, see Sample Configuration and Script Files.
- In your Siebel application, navigate to the Administration - Data Quality screen, then the Data Quality Settings view and in the value field for the parameter shown in the following table, specify the following setting:
|
|
Enable DQ Multiple Languages |
Yes |
- Enable multiple language support for real-time flow:
- Navigate to Administration - Data Quality screen, then Third Party Administration view in your Siebel application.
- Select ISS as the third party vendor.
- Add the vendor parameters shown in the following table:
|
|
Append Account Record Type Field 1 |
Primary Account Country |
Append Contact Record Type Field 1 |
Primary Personal Country |
- Enable multiple language support for batch flow:
- Navigate to Administration - Data Quality screen, then Third Party Administration view in your Siebel application.
- Select ISS as the third-party vendor.
- Add the vendor parameters shown in the following table:
|
|
Batch Append Account Record Type Field 1 |
Country |
Batch Append Contact Record Type Field 1 |
Primary Personal Country |
- Add the user property to the ISS System Services business service.
The user property that you add must correspond to the system name created in Informatica Identity Resolution for the respective country. For example, if the system created for Japan is siebeldq_Japan and the ID is set to 5, then the user property name must be siebeldq_Japan and the value 05, as shown in the following table.
|
