Best Practices for CI Import
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2022 09:54 PM
You want to import the various types of CI output from external systems into ServiceNow in a single import.
When using an import set, you can
Is there a way to register CIs from a single Excel file output from an external system into multiple target tables?
Or is there any other easy way to import besides an import set?
Thank you in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2022 10:10 PM
Best would be to go for ServiceNow discovery, and get the true data directly from the network, which will keep updating itself regularly. It also uses inbuilt identification and reconciliation engine which helps to manage duplicate records and can manage different data sources for populating the cmdb
Import sets are the only option if you are not using discovery. You need to upload for each table. You cannot put all the CI data at once.
To get more insights go through the below document
https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/configuration-management/concept/c_OptionsToPopulateCMDB.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2022 12:30 AM
ディスカバリーの利用が推奨されていることはよくわかります。
ただし、私の環境では、同じネットワークに接続された CI 情報が MID サーバーに登録されていないため
、ディスカバリーは使用できません。
インポートセットを使用する以外に他の方法はありますか?
このような状況ではインポートセットを使用するのが最善ですか?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2022 12:58 AM
I understand that the use of Discovery is recommended.
However, in my environment, CI information connected to the same network is not registered with the MID server, so
and discovery cannot be used.
Is there another way besides using an import set?
Is it best to use an import set in this situation?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2022 12:23 AM
Hi
of course it would be possible to import an Excel file and import the data into different tables in one batch. You just have to define several Transform Maps which are executed one after another during the import.
But for the CMDB it is not recommended to go the usual import way. The reason is, that no CMDB rules are considered and in the worst case you have duplicate CIs.
The recommended way is using the IRE and this is done automatically by leveraging the IntegrationHub ETL application (see https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/configuration-management/...)
There is a lot of documentation available for that tool and also videos are offered at YouTube.
Kind regards
Maik