New comparison operator additions

This section describes how support for a custom operator can be added to the spec value search capabilities of InfoSphere® MDM.

To add a custom operator, the following must be done:
  • a new type code must be added to the CDXMLCOMPOPTP table
  • a method must be overridden at the search query construction level of the application, and
  • the class containing this method must be defined in configuration in order to be instantiated instead of the default class

The standard code table services can be used to add the custom type code (and its translated values) to the CDXMLCOMPOPTP code table. See the IBM® InfoSphere Master Data Management Common Data Dictionary for details. There are primarily two attributes for this new type code: the type code itself and the name.

Depending on the database platform configured to work with InfoSphere MDM, the corresponding spec value search query class should be subtyped:
Table 1. Query class name subtypes by database platform
Database Query Class Name (in com.ibm.mdm.common.spec.search.sql)
DB2® V9.5 for Linux®, Unix, and Windows NativeDBSpecValueSearchSQLDB2
DB2 V9.7 for Linux, Unix, and Windows NativeDBSpecValueSearchSQLDB2
Oracle 11g NativeDBSpecValueSearchSQLOracle
DB2 V9 for z/OS® NativeDBSpecValueSearchSQLDB2v90z
DB2 V8 for z/OS EntityIndexTableSpecValueSearchSQL

The fully qualified name of the custom class should then be stored in the /IBM/Product/SpecValueSearch/SpecValueSearchSQL/className configuration item. Note that there is a default value for the class, configured dynamically by InfoSphere MDM at runtime; however, you can define a static class if you know which database you are using.

Finally, the processCustomizeOperation method should be implemented to handle the custom operator type. It should include validations specific to this operator, handle the construction of the query snippet given the requirements of the new operator.