Insert data in non-cmdb table using IH ETL

pratiksha5
Mega Sage


Insert data in non-cmdb table using IH ETL

 

Starting from the Utah release, IRE now provides support for certain non-CMDB tables. To utilize all IRE features with these tables, you must first establish identification rules (CI identifiers and identifier entries) specific to those tables. The non-CMDB tables that are supported for IRE features encompass the following:

 

In an application-specific scope: All non-CMDB tables are supported.


In the global scope: Only non-CMDB tables that come pre-configured in the base system are supported. For instance, in the Utah release, the supported non-CMDB tables include Location [cmn_location], Department [cmn_department], Cost Center [cmn_cost_center], Building [cmn_building], User [sys_user], and Group [sys_user_group].

 

I am sharing one example of how you can do that. Let’s take example of location table. 

 

Step one : - Create an identifier for the location table 

 

pratiksha5_0-1689853465080.png

 

 

Step two : - Create identifier entry for above identifier. 

 

pratiksha5_1-1689853465231.png

 




Step three: Your table is ready for insert.

 

pratiksha5_2-1689853465329.png

 


Don't forgot to make my article  Helpful

 

 

8 REPLIES 8

Thota Naga Jyo1
Tera Contributor

Thank You for this

Najmuddin Mohd
Mega Sage

Was looking for this. Thank you for the detailed explanation!

lamiaboumou
Tera Expert

Hello, 

 

Thank for the explanation.

I have completed all of these steps for both user and location table, and now I can select them as a class in the IntegrationHub ETL.

The problem arises when I attempt to map, as the activation slider is always grayed out.

Lamia_Boumour_1-1704854071823.png

also now I have a button "add associated CI" that displays the message "This non-CMDB class must be associated with a CMDB class." but with an empty dropdown list.

 

Lamia_Boumour_0-1704854050618.png

Even if I want to associate my table with a CI, I cannot do it.

Do you have any insights into what might be causing this problem?

Make sure you have created the identifier entries properly.