Common Information Model

How can you minimize dependencies when integrating applications that use different data formats? 

Use a common information model to minimize application integration dependencies. By designing a common information model that is independent from any specific application, you can require each application to produce and consume messages in this common format.

But first... What is a Common Model?

A common information or common data model (CDM) is a common model that represents the semantic structure that is common to multiple data sources and data services. Class maps (a specification of correspondences between properties of one class and properties of another class) define correspondences between the common data model's domain schema and the schemas in data sources and data services. For more information, listen to the podcast, What is a Common Model?

Include a Common Information Model Strategy into Your SOA Plans

As organizations attempt to figure out the data in the context of service-oriented architecture (SOA), they are often driven to the notion of a common way to view data as a part of the architecture. This becomes a crucial aspect of designing an SOA because different services, and applications, need to share semantics so that they deliver accurate and reliable results. Many pioneers of SOA are finding that the single most important component of an SOA is the data, which means you need to think carefully about how the data is managed and ultimately resolved. And while some SOA infrastructures are successful when they first are piloted, IT managers and developers should try to face the data first and define a common information model so that the services are not bound to a particular schema.

If you do not have a common information model, then you simply won't be able to effectively achieve the reusability benefits of an SOA. In order to achieve the benefits of an SOA, a common data model forces a foundation for data interoperability, and maintaining data integrity has historically been a huge issue across service providers. If all systems map to a common information model, then when one system changes, others don't need to, thereby providing a protection mechanism to ensure that the enterprise is not hamstrung by vendors who all maintain different information models. When organizations seek the software to support their SOA infrastructure for better application integration, they turn to Progress Software for the answer.

Progress has the Technology You Need to Build a Common Data Model

Progress® DataXtend™ Semantic Integrator (SI) addresses the common information model challenges in SOA. The DataXtend SI product uses industry standard models to manage the validation and transformation of data so it can be shared between applications that require different information or formats. By providing an automated, model-based approach to data integration, the DataXtend SI product helps customers reduce the cost, time and complexity of integrating systems. While conventional data integration approaches simply manage format integrity, the DataXtend SI product delivers breakthrough technology that addresses the far costlier challenge of enabling companies to build a common information model that delivers semantic consistency of data shared between applications across distributed enterprises.

Some of the common information model frameworks already available include:

• ACORD - Insurance
• ETIS - Telecommunications
• FpML - OTC Derivatives 
• ISO - Financial Services
• SEPA - European Financial Services
• SWIFT - Financial Telecommunications
• TM Forum - Telecommunications

In addition to semantic data integration software solutions, Progress Software also delivers the industry's first enterprise service bus, and soa management, data replication, BPEL orchestration, and a complete SOA Portfolio.