Guidelines for adding attributes and subclasses
If you decide to add attributes or subclasses, follow these guidelines:
Perform the work using the Class Manager, an API program, or the
cmdbdrivercommand. Modifying the BMC Atrium Configuration Management Database (BMC Atrium CMDB) data model requires more than just editing a form, and you might break some functionality. You can use BMC Remedy Developer Studio to modify field layout and labels.
Never make those changes directly on class forms using BMC Remedy Developer Studio.
- Because a CMDB gets its value by sharing data among applications, make your extensions as widely useful as possible, so that they can meet multiple needs. Avoid extensions that narrowly cater to one application, even for high-volume uses.
- Do not create classes more than five database join levels deep. For information about the classes that use joins, see BMC Atrium CMDB data storage methods.
Determine whether you want to store configuration data or lifecycle data for the CI in the new attribute. You must add a new attribute to a class to store only configuration data about a CI. To store lifecycle data for a CI, you must add a field on the AST:Attributes form that is installed by BMC Remedy IT Service Management version 8.0 and later. For more information on Adding data to AST:Attributes in relation to CIs, see .
In versions prior to 8.0, BMC Remedy IT Service Management extended CI lifecycle data as attributes in BMC Atrium CMDB. With multiple datasets, multiple copies of the CI lifecycle data were created and stored in BMC Atrium CMDB. However, CI lifecycle data is not discovered and does not have to be reconciled across multiple datasets. Because of this, version 8.0 of BMC Remedy IT Service Management moved the CI lifecycle data out of BMC Atrium CMDB and included the data as fields in the BMC Remedy ITSM Foundational form, AST:Attributes. When creating the Remedy Asset Management UI, the CMDB2ASSET process joins the BMC Atrium CMDB class table and the AST:Attributes table.
The change in the process of storing the CI lifecycle data greatly improves the performance of BMC Atrium CMDB, creates only a single instance of CI lifecycle data, and gives control of the CI lifecycle data to the Asset Manager instead of the Configuration Manager. For detailed information about the changes, see .