Modification of your data model
This use case describes how to extend your data model with the class manager in BMC CMDB.
As you evaluate your business environment and plan your data model, you might determine that the Common Data Model (CDM) installed with BMC CMDB is not sufficient to store information for some of your assets.
Data model modification scenarios
Workflow of data model modification by creating or modifying classes
|Component | Console||User||Action||Reference|
|BMC CMDB class manager||CMDB Administrator||Define the properties of the class, which include its type, how it stores data, and (for relationship classes) the relationship type.|
Creating or modifying classes by using Class Manager
|(optional) Specify permissions. If you do not specify permissions for a class, BMC CMDB assigns default permissions.|
|Define one or more CI and relationship class attributes.|
|(optional) Propagate attributes in a weak relationship. This step is necessary only if you have created a relationship class that has a weak relationship in which the attributes from one class should be propagated to another class.|
|(optional) Specify indexes. Indexing can reduce database query time, so index attributes that you expect users to use in queries frequently.|
|optional) Configure instance auditing for the class. Auditing enables you to track the changes made to instances of a class.|
Audit of the results
The Calbro Services administrator knows that changes to the service model can be disruptive to the customers using those services. To help identify all of the changes to business services and the supporting technical services, the administrator decides to audit the
Copy auditing this class should not affect overall system performance because changes to the
BMC_BusinessServiceclass should be few in number. Copy auditing also enables greater ability to search for changes to the class. For these reasons, the administrator configures copy auditing instead of log auditing.