History installation worksheet

Use this worksheet to record parameters for your history trigger configuration.

History triggers are used by physical MDM operational servers.

There are two sets of triggers that generate data for physical MDM database history tables. The first set is for the core and domain tables. The second set is for the configuration management tables. Each set consists of history triggers and delete triggers.

The parameters that are listed in the following table equate to prompts or fields that you see in IBM® Installation Manager.

Table 1. History installation worksheet
Parameter Description Your value
Industry Specify the industry type that is supported in this implementation. You can specify only one type.
There are four supported industry types. Each option installs the code tables and data for that industry type.
  • Insurance - Choose this option for lines of business such as Life, Health, Annuities, Pensions, Property and Casualty, and others.
  • Banking - Choose this option for lines of business such as Retail Banking, Commercial Banking, Credit Cards, Loans, and others.
  • Telecommunication - Choose this option for lines of business such as Wireless, Cable Television, Satellite Television, Internet, Telephone Services, and others.
  • Manufacturing - Choose this option for lines of business such as Precision Tools, Aerospace, Electrical, Heating, Mechanical, and others.
  
History triggers There are three history trigger options. You can specify only one.
  • None. Choose this option if you do not want to install any triggers. Choosing this option prevents history from being stored in the database.
  • Simple. Choose this option to install only the update triggers. When a record is updated in the database, a copy of that record (before the update) is added to the history table. Past versions of the record are stored in the history table.
  • Compound. Choose this option if you want to install both insert and update triggers. When a record is added to the database, or when a record is updated in the database, a copy of the record is added to the history table. Copies of both the current and past versions of the record are stored in the history table.
 
Case sensitive searches By default, name searches for contracts, products, and categories are not case-sensitive. Check the Enable case-sensitive searches check box only if you want to place case-sensitive restrictions on your searches.

Once this feature is activated, database objects are created and you cannot deactivate the option.

  
Code table languages Translated code table values used for predefined lists and error messages are included with the physical MDM operational server.

English is the default language.

 
Application resource language Specify the corresponding language translations for the user interface to install.