MOMs the word for a federated CMDB

How many CMDBs does it take to manage an SOA?

Industry analysis by Beth Schultz, plus the latest news headlines.

Long before MOM became an acronym for Microsoft's Operations Manager, it was a generic term applied to a vendor-agnostic group of enterprise management products. In this capacity, the acronym stands for Manager of Managers, and describes an architecture exemplified by CA's Aprisma. Aprisma's MoM event console is an approach to scaling and managing multiple distributed instances of Aprisma. The tiered design minimizes SNMP traffic across the WAN while providing a single enterprise view of the infrastructure environment. What would happen if this same design was applied to the problem of integrating multiple information stores into a federated CMDB consolidation product?

In a recent article, I discussed software-oriented architecture's loose coupling and the fact that it is likely one more reason why a federated CMDB will become increasingly fundamental to managing SOA and Web services. That article described a federated CMDB as providing the "missing link" for automating the process of mapping virtualized business services to underlying technology. Especially as more enterprises roll out Web services-based SOAs, an alternative to today's manual mapping techniques will become vital to managing these loosely coupled systems.

WebMethods' recent acquisitions demonstrate that powerful information repositories are part of vendor product strategies as well. On Sept. 11, just weeks after announcing its acquisition of Cerebra, webMethods announced the purchase of Infravio. The close proximity of these two buys isn't a coincidence. WebMethods' simultaneous courtship and acquisition of both companies is an indication of its intent to pursue the SOA big picture, which will likely include extensive external and cross-industry integrations.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

Long before MOM became an acronym for Microsoft's Operations Manager, it was a generic term applied to a vendor-agnostic group of enterprise management products. In this capacity, the acronym stands for Manager of Managers, and describes an architecture exemplified by CA's Aprisma. Aprisma's MoM event console is an approach to scaling and managing multiple distributed instances of Aprisma. The tiered design minimizes SNMP traffic across the WAN while providing a single enterprise view of the infrastructure environment. What would happen if this same design was applied to the problem of integrating multiple information stores into a federated CMDB consolidation product?

In a recent article, I discussed software-oriented architecture's loose coupling and the fact that it is likely one more reason why a federated CMDB will become increasingly fundamental to managing SOA and Web services. That article described a federated CMDB as providing the "missing link" for automating the process of mapping virtualized business services to underlying technology. Especially as more enterprises roll out Web services-based SOAs, an alternative to today's manual mapping techniques will become vital to managing these loosely coupled systems.

WebMethods' recent acquisitions demonstrate that powerful information repositories are part of vendor product strategies as well. On Sept. 11, just weeks after announcing its acquisition of Cerebra, webMethods announced the purchase of Infravio. The close proximity of these two buys isn't a coincidence. WebMethods' simultaneous courtship and acquisition of both companies is an indication of its intent to pursue the SOA big picture, which will likely include extensive external and cross-industry integrations.

Infravio's products address SOA governance and metadata management, while Cerebra addresses taxonomies, or relationships, between organizational assets such as XML schemas and Business Process Execution Language (BPEL) documents. The combination of these functionalities will be critical to cross-industry integration. For example, integrating the healthcare industry to the insurance industry isn't a straightforward proposition. Both industries have their own XML schemas, document formats, governance and security requirements. What happens when they are linked in an SOA and have to "talk" electronically? With these acquisitions, webMethods is positioning for just such a scenario.

Our industry tends to be one of evolution rather than revolution. From this perspective, applying the MoM tiered architecture to the federated CMDB could be one way to approach a CMDB federation that yields a bird's eye-view of multi-dimensional relationships. Adding the information provided by webMethods' new capabilities to a federated CMDB could result in an integrated data store that exposes technology relationships in context with registries, repositories, and unstructured assets such as XML schemas. This could eventually enable not only automated mapping of virtualized services to technology, but could also provide the governance and metadata bases for cross industry integration.

Schultz is a longtime IT journalist. You can email her or find her here.