CMDB setup

[Money]

Hello everyone.
I am looking for some opinions in setting up a CMDB. Is there anyone that is sticking to more of the out of box Service-Now configuration? Is there anyone that has experienced a custom CMDB where you have created from scratch?

We are leaning towards a custom CMDB for various reason. We are looking to map out our items by different class levels and we are not looking to house those levels on different tables. For example, a CI's Hardware classification would be a level 1. From there that same CI's classification of the type of hardware would be level 2. For example, computer. We are looking to possibly go down 4 levels and not have to worry about there being separate tables (for instance hardware and computer). Just some thoughts or experiences regarding the CMDB...

[SHA3]

Hi mdouglass,

I am working on a similar requirement.

I need to create a wsdl to be used by BMC Atrium so that they can pull all the values needed in a single wsdl. Rather than creating wsdl for each CI Type [integration].

Please let me know if you have found a way to complete this requirement. If you too havent found, i will post my findings on the same when i get some result.

[diabloooo]

Just thinking will it be an idea to create a new table to represent the flatted cmdb_ci_* structure and use a scheduled job to replicate the data from cmdb_ci_* table to the new table every day? this way you can just provide the WSDL of this new table.

[Gabe1]

The cmdb_ci table shows all CI records (including records that are part of extended tables).   So if you're just looking for a single view of all CI's, open the cmdb_ci table.   Also I highly recommend reviewing what Jacob Andersen commented in this thread, it's great information for someone new to ServiceNow's approach to CMDB data structure.

[diabloooo]

I guess the problem here is the field that is CI type specific, for e.g. those fields that are only available on cmdb_ci_network... these are not available on cmdb_ci table.

[grumbl]

But as these tables and thus fields extend from cmdb_ci, this would not be an issue.

If you modify or add classes, reporting on the CI's has to include these of course.   So what is the problem ?