ne of the most basic needs that a customer has when building out their CMDB is extending it to match the types of CIs that they’re currently using in their company.Â This is especially true when bringing data in from a 3rd-party CMDB (such as IBM’s CCMDB, HP’s uCMDB, etc) with Service-now.Â Some of these CMDBs have hundreds of class types with scores of fields for each class.Â How can you get the 3rd-party data into Service-now when the schema is so different?
There are essentially four main steps to accomplish this: decide what classes and fields need to be brought across, create a mapping document, extend the Service-now CMDB to accept the new classes, and send the data from the 3rd party CMDB to Service-now.
1) Decide what classes and fields should be included in Service-now
Every integration discussion starts out the same, “Can Service-now receive my 200+ different CI class types and how long will it take for us to do this?”Â While it is good to know the capabilities of Service-now before embarking on such a task, perhaps the more important question that product managers should be asking is, “out of these 200 class types, what are the +/- 20 classes that make sense to integrate with our service desk?”Â The first answer is usually, “All of them!”Â However, when looked at more carefully, it usually makes sense to only bring over a small subset of the entire collection.
2) Create a mapping document
The difficulty of this step largely depends on the number of classes and fields that were decided in step one.Â Again, you’ll want to pear down the number of fields in each class to be small and relevant.Â The more common items such as IP address and MAC address will be similarly named in each system.Â Determine what fields are missing in SN in this step so that you know which fields need to be added in step 3.
3) Extend the Service-now CMDB
If steps 1 and 2 were done correctly, this step should be straightforward.Â The attached video is a demonstration that I put together to show how simple it is to extend the CMDB and how to go about doing it.Â You should use your mappingÂ document to show you which classes need to be added and what fields need to be in those classes.Â For the classes that already exist, you will simply be adding the new fields to the already existing class.
4) Send the data to Service-now
This is the step that scares some people and is mistakenly seen and the most difficult and time consuming step.Â However, when the previous steps are completed beforehand, this step is actually the simplest of them all.
The most common method of bringing CMDB CI data into Service-now is by using a CSV/XML file. This is a perfect choice when you’re wanting to do a one-time load of CI data into your system. This can be done by creating a new data source and attaching your CSV / XML file to the record. More details on this can be found here: http://wiki.service-now.com/index.php?title=Importing_Data_Using_Import_Sets
In a CMDB integration, the most common way of sending data to Service-now from a 3rd-party is by using JDBC connection to the source of record.Â A simple (or not so simple) SQL statement retrieves the classes that you’re interested in and sends them to Service-now to be mapped.
Another common way of sending data to SN is by using web services.Â If your CMDB or discovery solution supports sending SOAP, then you might consider this option as well.Â I cover this in the attached video as well.
A CMDB integration can be daunting.Â However, if you follow this guide, you should have a good idea how to approach it in a way that encourages a successful and timely outcome!