System Definition

Duplicate Detect may be customized to fit business needs. It allows the user to control the fields included when checking for duplicate entries, which entries are excluded from duplicate checking, the expiration time for entries, and whether items are sent for review. The user must provide an XML description of the system, including the database schema and table names, expiration criteria, and exclusion criteria. The XML files are stored in the DUPDETECT.NAMESPACE_DEFS table. When the Duplicate Detect engine starts, it reads the XML data from the NAMESPACE_DEFS table in order to know the definition of each of the user’s namespaces. Insert one row into the NAMESPACE_DEFS table for each namespace on which to perform duplicate checking.

If the system definition is modified, it must be reloaded in the database to take effect. Delete the corresponding row from DUPDETECT.NAMESPACE_DEFS table and insert the XML again. The ReferenceInsertNamespace.ddl can be used to insert the XML back in the NAMESPACE_DEFS table. After updating the database, the Duplicate Detect engine applications should be stopped and restarted from the WebSphere® administrative console.