Integration Hub ETL - How to add a non-CMDB class

Go to solution
senon
Tera Sage

‎07-26-2024 01:18 AM

Hello experts!

I am doing some testing using Integration Hub ETL. I am investigating whether IH-ETL can be used to import CIs and asset items at the same time.

I know that IH-ETL supports non-CMDB classes since version 3.2, Utah version.

■Problem
I am investigating with PDI and the version is Washington DC and the IH-ETL version is 3.2.
I have referred to the following video and document, but I am unable to select a non-CMDB class.
Using the IRE for non CMDB data - YouTube
Create an ETL transform map (servicenow.com)


Even if I search for a non-CMDB class on the Add-Class popup, it does not appear.

senon_0-1721981590021.png


As shown in the image, in addition to the OOTB definitions, the system property [glide.identification_engine.non_cmdb_tables] also includes the [alm_xxx] table names.

senon_1-1721981617417.png

 

Any configs or ideas to get the non-CMDB classes to show up?

Best regard.


senon

 

  • 1,219 Views
1 ACCEPTED SOLUTION

Go to solution
Marshall Parker
Tera Guru

‎08-01-2024 09:33 AM

To enable using a non-CMDB table in Integration Hub ETL requires a couple of steps of pre-work per table you want to target.

 

The first step is to add the table to the IRE system property [glide.identification_engine.non_cmdb_tables], which it looks like you have already done.

 

The next step is to create a CMDB Identifier for that table, so the IRE knows what the identification rules will be for the non-CMDB table. The YouTube video demo that you linked contains some description of this (Special considerations slide at time stamp 6:13 or so, then demo of adding an identifier for the location table from timestamp 11:24 - 15:30).

 

High Level steps:

1) For the non-CMDB table, determine what key identification field(s) you want to use to identify these records, considering your input source.

2) Create an identifier record for the table level on cmdb_identifier

3) Create an identifier entry for this table (cmdb_identifier_entry related list)

4) Navigate to IH-ETL and you can now see this table mentioned in the Add Classes list

View solution in original post

2 REPLIES 2

Go to solution
Marshall Parker
Tera Guru

‎08-01-2024 09:33 AM

To enable using a non-CMDB table in Integration Hub ETL requires a couple of steps of pre-work per table you want to target.

 

The first step is to add the table to the IRE system property [glide.identification_engine.non_cmdb_tables], which it looks like you have already done.

 

The next step is to create a CMDB Identifier for that table, so the IRE knows what the identification rules will be for the non-CMDB table. The YouTube video demo that you linked contains some description of this (Special considerations slide at time stamp 6:13 or so, then demo of adding an identifier for the location table from timestamp 11:24 - 15:30).

 

High Level steps:

1) For the non-CMDB table, determine what key identification field(s) you want to use to identify these records, considering your input source.

2) Create an identifier record for the table level on cmdb_identifier

3) Create an identifier entry for this table (cmdb_identifier_entry related list)

4) Navigate to IH-ETL and you can now see this table mentioned in the Add Classes list

Go to solution
senon
Tera Sage
In response to Marshall Parker

‎08-04-2024 06:22 PM

Hi, Marshall Parker
Thanks for the reply. I'll try this!