IBM InfoSphere MDM Custom Domain Hub, Version 10.1

Setting up code table data

InfoSphere® MDM Custom Domain Hub is shipped with code table values and error messages translated in each of the available languages. The code table values and error messages are stored in various database tables.

These tables can be classified as one of two types:

Language independent code table
Language dependent code table

A language independent code table holds data in only one language. The data is used mainly to configure the application and ideally should be in the language that best suits the language of the system administrators. At installation time, the installer must select one language to populate these tables with. An example of such a table is COMPONENTTYPE. This table stores the Java™ objects that InfoSphere MDM Custom Domain Hub supports, and the descriptions of these records are in the language that is intended for the system administrator.

A language dependent code table holds data in one or more languages. The data is used to provide translated values in the language of the end user. By default, English data is always populated in these tables. At installation time, the installer can select one or more languages that the installation base expects to support. An example of such a table is CDADDRUSAGETP. This table stores the address usage types that InfoSphere MDM Custom Domain Hub supports and they should include the various languages corresponding to the end users.

For the language dependent code tables, they have lang_tp_cd which maps to lang_tp_cd column in the CDLANGTP table. Fallback logic is applied when caching these code table records.

The caching mechanism relies on the language and locale to build a language and locale hierarchy. This hierarchy contains all the records in the CDLANGTP table that have a null expiry_dt or if the expiry_dt is in the future and CODE_TABLE_TRANSLATION has value as ‘Y'.

The language dependent code table records are cached for the languages in the hierarchy. For example, for CDIDTP, the records are cached for supported languages that have CODE_TABLE_TRANSLATION flag set to ‘Y' in CDLANGTP. For the other languages that have CODE_TABLE_TRANSLATION flag set to ‘N', you can add a record to CDIDTP, but they are not in cache and cannot be retrieved. In order to use them, you must set the CODE_TABLE_TRANSLATION flag to ‘Y' for that language.