IRE support for non-CMDB tables

Apply Identification and Reconciliation Engine (IRE) processes to supported non-CMDB tables to ensure data integrity and health of those tables.

Starting with the Australia release, IRE supports some non-CMDB tables. You can use all IRE features with some non-CMDB tables after creating identification rules (CI identifiers and identifier entries) for those tables. Non-CMDB tables supported for IRE features include:

• In an application-specific scope: All non-CMDB tables
• In the global scope: Only non-CMDB tables that are preset in the base system. In the Australia release for example, the Location [cmn_location], Department [cmn_department], Cost Center [cmn_cost_center], Building [cmn_building], User [sys_user], and Group [sys_user_group] non-CMDB tables are supported.

You can't use the CI Class Manager to manage any IRE-related rules for non-CMDB tables. Instead, you must work directly with the respective tables in list views to create and manage those rules as described in the following procedures:

• Create an identification rule for a non-CMDB table
• Create a reconciliation rule for a non-CMDB table
• Create an IRE data source rule for non-CMDB tables
• Create a data refresh rule for a non-CMDB table
• Create an identification inclusion rule for a non-CMDB table
• Simulate payload execution using identification simulation
• Use partial payloads
• Review and process de-duplication tasks

You can use the following store apps with supported non-CMDB tables:

• CMDB 360 in CMDB Workspace
• IntegrationHub ETL

IRE processes are applied to supported non-CMDB tables with the following differences:

• IRE doesn't populate the discovery_source, last_discovered, and the first_discovered attributes if those attributes don't exist in the non-CMDB table.
• IRE uses the non-CMDB table’s class name as sys_class_name if the table doesn't include a sys_class_name attribute.
• IRE payloads don't support relationships with non-CMDB tables.

Note: Although IRE-related user interface and accompanying documentation might reference CMDB and CMDB elements, most of those references also apply to any supported non-CMDB tables.

• Create an identification rule for a non-CMDB table
  To use Identification and Reconciliation Engine (IRE) features with supported non-CMDB tables, you must first create identification rules that uniquely identify the table records. Each non-CMDB table can be associated with a single identification rule.
• Create a reconciliation rule for a non-CMDB table
  Create a static or a dynamic CI reconciliation rule for a non-CMDB table.
• Create a data refresh rule for a non-CMDB table
  To apply Identification and Reconciliation Engine (IRE) features to supported non-CMDB tables, create data refresh rules for those tables. Data refresh rules are used to determine if a record is stale for a specific data source. Such records can then be updated by a lower-priority authorized data source.
• Create an identification inclusion rule for a non-CMDB table
  Narrow the scope of records that are included in the identification process of non-CMDB records by creating an identification inclusion rule.
• Create an IRE data source rule for non-CMDB tables
  When using Identification and Reconciliation Engine (IRE), you can prevent a specific data source from inserting new records for a specific non-CMDB table. Create IRE data source rules for data sources that you don't trust in creating records but continue to trust in updating those records that exist.

Parent Topic:CMDB Identification and Reconciliation (IRE)