Two Ways To Deal With SOA's Data Integration Challenge

Service-oriented architecture blurs distinctions between data and apps; integrating the results is what matters.

Charles Babcock, Editor at Large, Cloud

July 6, 2007

3 Min Read

Not everyone is a fan of the iWay approach to integrating data across services. "I have always been somewhat skeptical," says ZapThink's Schmelzer, because it is too close to the old application-to-application integration of yesteryear, where each connection has to be set up individually and is inflexible.

Services need to be architected so that they yield data that can be consumed by various applications, although iWay's Service Manager manages much of that task. Companies also need to be able to change how data is presented without altering the service interface. IWay, however, often requires an interface for each presentation rather than producing data that can be easily used across all of them, Schmelzer says.

An alternate way to integrate data across Web services is provided by open source and proprietary products. Open source Jitterbit can take an application message, transform it into XML, and map and deliver it to a target system over the Web. It relies on Web standards and an ability to transform data between systems. Apatar and Talend have similar open source products. DataDirect and MetaMatrix have proprietary ones, though MetaMatrix is being acquired by Red Hat, and its products will become part of open source JBoss.

Open source Apatar is being evaluated by AutoDesk, which makes computer-aided design and engineering software. It also offers collaborative construction project management in the form of software as a service that integrates data through a Web portal for the contractors on a project. Major construction projects can involve 40 or more contractors.

AutoDesk's offering uses Apatar as the integration agent, says Jason Pratt, technical services manager for collaborative project management. Apatar can map data between systems and take advantage of Web services to export data to business partners. It can perform extract, transform, and load functions between systems so that two companies that have not built point-to-point connectors can still arrange to share each other's data. And unlike custom-built point-to-point connectors, Apatar connection code relying on Web standards doesn't require testing to ensure that it will work, says Renat Khasanshyn, founder and CEO.

A typical transformation through the Autodesk service would have the JD Edwards accounting system of one contractor exporting data into the scheduling system of another, so different aspects of the job can be executed on schedule.

Apatar provides "the plumbing for all the data, a pipeline from one system to another, like Legos," Pratt says. It's a great way to to get more flexibility without building middleware, he adds.

Take your pick. IWay and other vendors have adapted point-to-point connectivity to the services world. And now open source products are making it possible to integrate data at a higher level across services. Whichever way you go, you're closer to implementing a successful SOA.

About the Author(s)

Charles Babcock

Editor at Large, Cloud

Charles Babcock is an editor-at-large for InformationWeek and author of Management Strategies for the Cloud Revolution, a McGraw-Hill book. He is the former editor-in-chief of Digital News, former software editor of Computerworld and former technology editor of Interactive Week. He is a graduate of Syracuse University where he obtained a bachelor's degree in journalism. He joined the publication in 2003.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights