Rest API integration with BT Diamond IP and ServiceNow for CMDB update/Insert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2022 02:22 AM
Hi All,
I am new to rest API integration in ServiceNow. I want to integrate the BT diamond IP (IP management tool) with ServiceNow to update and insert record in CMDB. What will be the steps we can perform to achieve this integration?
Have anybody encountered similar kind of integration ? It would be great if someone can share their thoughts.
Thanks.
Abby
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-12-2022 08:37 AM
I'd recommend taking at look at the Integration Hub ETL for this purpose. There are a few things that you'll want to keep in mind when doing any CMDB integration:
- ALWAYS use the Identification and Reconciliation Engine (IRE). There are a couple more parts to configure to use it (reconciliation definitions, IRE Data Source Rules, Identification rules, etc).
- Integration Hub ETL uses the IRE by default
- You can call the IRE in an inBefore script in a transform if you choose not to use Integration Hub ETL.
- See rule #1 again.
- Just making sure...did you see rule #1?
- Use OOB tables when possible, making sure that CMDB CI Class Models app is up-to-date before starting.
- Verify that you're following rule #1
- Study demo data for the target classes in your PDI before you start. To make sure your implementation plays nice with other CMDB integrations and Discovery should you use those later.
- You'll want to make sure that things like storage units and memory units match the demo data. That may mean converting RAM from gigabytes to megabytes.
- Make sure Operating system, OS Version, etc are populated correctly. Don't just take what the tool outputs and let it add new choices without first.
- Always convert your data to match OOB fields and formatting rather than changing CMDB labels and fields to match your data.
- Don't try to house multiple values in a field meant for one.
- Don't change the length of baseline fields
- Don't create a new class just because someone doesn't like what the baseline class is called
- When you have the data, populate related records for Network adapters, IP addresses, etc. These are of great value when you need to reconcile data from other sources in the future (you'll eventually add or replace a tool for populating the CMDB)
- Don't create CIs that you aren't going to be able to identify later (ie. if all you have is an IP address and OS).
Now that I've given some important tips (pay special attention to #1), I'd recommend this good video on how to use Integration Hub ETL and this series with our friend Chuck Tomasi:
- Creating an Integration Hub Custom action
- Data Stream Actions
- Learn Integrations on the Now Platform
(The whole Playlist "Learn Integrations on the Now Platform" is really good.