|
ITIL v3 defines a CMDB as "A database used to store Configuration Records throughout their Lifecycle. The Configuration Management System maintains one or more CMDBs, and each CMDB stores Attributes of CIs, and Relationships with other CIs." A federated CMDB provides users a unified, consistent mechanism to utilize data that may be residing in disparate data sources seamlessly, without having to understand exactly where the data resides or the technology behind accessing the data. RapidCMDB is designed from the ground up as a federated CMDB. RapidCMDB includes object data store that can be used as a data store on it own, however through federation, it ensures scalability and provides access to data in existing sources, eliminating problems associated with rip and replace, data duplication, synchronization, etc. CMDB Federation workgroup published a draft specification which appears to be designed to enable one CMDBs to exchange data with other CMDB implementations from different vendors. RapidCMDB's approach is somewhat different. RapidCMDB is not a traditional CMDB. It is designed specifically to create a unified CMDB through federation leveraging existing data sources that are not necessarily databases. IT organizations already have number of tools that hold valuable configuration data, and moving this data from these tools to traditional CMDBs and keeping the data in te CMDB up to date can be significant undertaking. RapidCMDB can not only federate data from other CMDBs but also data that may reside in other management systems, etc.
|
Add Comment