Comparison of features in CMDB 1.0 and 2.0

The following table compares how different features are implemented in CMDB 1.0 and 2.0:

FeatureCMDB 1.0CMDB 2.0
Reporting

You cannot create a custom report that involves more than two classes (objects).

For example, to generate a report in CMDB that gives data about which LAN endpoints are used by which computers, you must refer to three objects: 

Base Element, Computer System, and LANEndPoints.

All classes are part of one object (as field sets), therefore, you can create reports that involve any number of classes.
Field definition of a classThe CMDB_AttributeDefinition class is used to recognize attributes (fields) that belong to a class (object).The field sets and field definition of the Base Element object provide the field definition of a class.
Data importRecords are first imported in a flat table, called staging table, and then saved in the individual objects. Therefore, the batch size is small.Records are imported directly into the Base Element object; therefore, the time required to import data is less. Pentaho packages for importing data into BMC Remedyforce are available on BMC Communities. The folders for CMDB include 2.0 in the names.
Data exportExporting data is difficult because one configuration item record is saved in more than one object.Exporting data is easy because all records are saved in the Base Element object.
Custom fields

Custom fields are added in the required class.

You can then access them in the class by navigating to the Remedyforce Administration > Configure CMDB 1.0 > CMDB Custom Attributes page.

Custom fields appear on the Custom tab on the Instance Editor.

Custom fields are added to the Base Element object and then to the field set of the required class.

  • Custom fields that are added to the Base Element field set are shown on the General tab on the Instance Editor.
  • Custom fields that are added to any other field set of the Base Element object are shown on the Specifications tab on the Instance Editor. The Custom tab has been removed for CMDB 2.0.
Instance EditorCustom fields appear on the Custom tab, and you cannot add or remove the fields on the General tab.To add or remove a field from the General tab, add or remove the field from the Base Element field set. To add or remove a field from the Specifications tab, add or remove the field from the field set of the required class.
Field trackingYou can track fields that belong to the Base Element object, shown on the General tab on the Instance Editor. You cannot track fields on the Specifications and Custom tabs.Because fields of different classes are stored in the Base Element object, you can track any field. However, Salesforce allows you to track only 20 fields in one object.
SearchYou can search fields of the Base Element object only. Therefore, search is limited.All fields (or attributes) are stored in the Base Element object, and the fields of the Base Element object are searched. Therefore, you can search data for all classes.
Data storage

Different objects are created for different classes; attributes that are common in all classes are stored in the Base Element object. This object is linked with other objects by using the Instance ID field of a configuration item (CI). Hierarchy is built by using the CMDB_Class object.

When a record is saved, data is saved in the Base Element object, all parent classes (if any), and the class for which the record is created. For example, if you create a Computer System record, data is saved in the Base Element, System, and Computer System objects.

All information is stored in the Base Element object. Classes are implemented as field sets in the Base Element object. Hierarchy is built by using the CMDB_Class object.

When you save a record, the record is created only in the Base Element object.

Was this page helpful? Yes No Submitting... Thank you

Comments