Sunday, Sep 05, 2010
Login

Category: CMDB

Extending the CMDB

O

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.


Walking the Service-now.com CMDB Relationship Tree

O

ne of the great features of Service-now.com is its CMDB and relational mapping.  You can easily set up relationships between any CIs in the system.  Once the relationships are defined, it becomes very simple to pull up a visual representation of a CI and its dependencies by using Service-now BSM maps.  Using this feature allows an end user to look at that CI and identify what else in the environment is impacted by an outage or a change to that CI.


 

Recent Comments

  • Scott Stechmesser: Awesome script to use. Works great. How would you modify it to be able to copy a Catalog UI Policy?
  • Tulio: Perfect!!! Thanks for this.
  • Ron Methias: Another reason why I have stopped going to the official SN documentation sites and make the GURU my...
  • Richard Huss: Ingenious – and somewhat simpler than the way the Incident Resolution best practice plugin does...
  • valor: Joe, that’s one of the reasons why I’m parsing out the URL instead of trying to get the page...