Configuring evergreening processes

Name standardization

These configuration items are controlled through the InfoSphere® MDM Configuration and Management component.

/IBM/Party/ExcludePartyNameStandardization/enabled

• Description – Determines whether name standardization is excluded. If this value is false, the standardized name fields will be added or updated in PERSONSEARCH and ORGNAME tables whenever name records are persisted, and the standardized names will be used in search transactions. If this value is true, the PERSONSEARCH table and the standardized name fields in ORGNAME will not be populated.
• Value – false
• Comments – The batch processor checks the standardization indicators in PERSONSEARCH and ORGNAME tables when searching for non-standardized Person and Organization names to standardize. It also updates the standardization indicators based on the result of name standardization. To ensure that the PERSONSEARCH table is populated, when party names are loaded into InfoSphere MDM, this configuration element needs to be set to false. If name records should be loaded without standardization using a name standardizer, the InfoSphere MDM default standardizer should be configured. The InfoSphere MDM default standardizer will add a record to PERSONSEARCH, but will not set the standardFormattingIndicator to Y.

/IBM/Party/Standardizer/Name/className

• Description – Specifies the name standardizer class.
• Value – varies
• Comments – When loading party name records into InfoSphere MDM, if a party name standardizer is not available, then it will use the default value of the configuration (the default value is com.dwl.tcrm.coreParty.component.TCRMPartyStandardizer). The default standardizer standardizes last names by converting them to upper case and stripping out any spaces. For instance, when the name "Mac Donald" is entered, it is standardized to "MACDONALD". For organization names, the default standardizer changes all letters to upper case. Prior to running bulk name standardization, the configuration element should be updated with the desired name standardizer, such as IBM® InfoSphere QualityStage®.

Address standardization

/IBM/ThirdPartyAdapters/IIS/StandardizeAddress/StandardFormattingIndicator/enabled

• Description – Determines whether the address standardization indicator is enabled. If this value is true, after successful address standardization, the StandardFormattingIndicator is set to Y and is persisted in the database. Otherwise, the StandardFormattingIndicator will retain its input value.
• Value – true
• Comments – The batch processor checks the standardization indicators when searching for non-standardized addresses to standardize. It also updates the standardization indicator based on the result of address standardization.

/IBM/Party/Standardizer/Address/class

• Description – Specifies the address standardizer class.
• Value – varies
• Comments – When loading address or contact method records into InfoSphere MDM, if an address or contact method standardizer is not available, then it will use the default value of the configuration (the default value is com.dwl.tcrm.coreParty.component.TCRMAddressStandardizer). The default standardizer stores elements in the same form in which they are entered. Prior to running bulk address standardization, the configuration element should be updated with the desired standardizer, such as IBM InfoSphere QualityStage.

Contact Method standardization

/IBM/ThirdPartyAdapters/IIS/StandardizePhoneNumber/StandardFormattingIndicator/enabled

• Description – Determines whether the contact method standardization indicator is used. If this value is true, after successful phone number standardization, the StandardFormattingIndicator is set to Y and is persisted in the database. Otherwise, the StandardFormattingIndicator will retain its input value.
• Value – true
• Comments – The batch processor checks the standardization indicators when searching for non-standardized phone numbers to standardize. It also updates the standardization indicator based on the result of contact method (phone number) standardization.

/IBM/Party/Standardizer/Address/class

• Description – Specifies the address standardizer class.
• Value – varies
• Comments – When loading address or contact method records into InfoSphere MDM, if an address or contact method standardizer is not available, then use the default value of the configuration (the default value is com.dwl.tcrm.coreParty.component.TCRMAddressStandardizer). The default standardizer stores elements in the same form in which they are entered. Prior to running bulk address standardization, the configuration element should be updated with the desired standardizer, such as IBM InfoSphere QualityStage.

Suspect processing

Prior to running suspect processing tasks, you must configure suspect processing in InfoSphere MDM.

Activity Dashboard

/IBM/DWLBusinessServices/Task/Search/maxResults

• Description – Specifies the maximum number of records returned from a searchTask transaction.
• Value – 100 (default)
• Comments – The batch processor uses the SearchTask transaction to retrieve tasks associated with standardization and suspect processing requests. Since a request can result in one or more tasks in the system, you might need to increase the maxResults for task searches from the default value of 100 to enable the Activity Dashboard to display all requests created through the Batch Console sample application.

/IBM/DWLBusinessServices/TaskChain/Search/maxResults

• Description – Specifies the maximum number of records returned from a searchTaskChain transaction.
• Value – 100 (default)
• Comments – The batch processor uses the SearchTaskChain transaction to retrieve tasks associated with standardization and suspect processing requests. Since a request can result in one or more tasks in the system, you might need to increase the maxResults for task searches from the default value of 100 to enable the Activity Dashboard to display all requests created through the Batch Console sample application.