Changes to the BMC Atrium CMDB for BMC Remedy ITSM
Version 8.0 of BMC Remedy IT Service Management (BMC Remedy ITSM) made important changes in the way BMC Remedy ITSM stores the attributes that it uses to describe configuration items (CIs).
Earlier versions of BMC Remedy ITSM extended the BMC Atrium Configuration Management Database (BMC Atrium CMDB) data model by adding a number of attributes that were used to track Asset Management CI data. These attributes included information about costs, and foundational data such as company and location. BMC Atrium CMDB also included lifecycle information. Lifecycle information, however, was not discovered and you did not need to reconcile it across multiple sources. As a result, the system did not need to store lifecycle information in multiple BMC Atrium CMDB data sets.
For this reason, and because some customers needed to maintain separate permissions on these attributes, the 8.0 release of BMC Remedy ITSM introduced a new data model for the Lifecycle data.
Standard integration points and application forms were redesigned to accommodate the updates, so most customers who upgraded to version 8.0 or later were not directly affected by this change. However, you should read this topic to ensure that you understand how the change might have an impact on your environment.
If you have customized functions or integrations that use lifecycle data, read this section.
Also, review the compatibility matrix for supported versions of BMC products at http://www.bmc.com/support/product-availability-compatibility.
For more information about the changes, see the following topics in the BMC Remedy ITSM Suite 8.0 online technical documentation:
- Data structure change
- Code changes
- Understanding how upgrades occur
- Integration and customization impact
- Updates to CI lifecycle data attributes
- BMC Remedy ITSM attributes that remain in the BMC Atrium CMDB
- Join architecture
- Backward compatibility for the BMC Atrium CMDB API
For information related to fields used in the system, see Finding whether and where fields are used in the system