We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

XML is fast becoming the universal data exchange format, and there would seem to be a natural and obvious synergy between XML and databases. Databases are central to most enterprises’ IT infrastructure, and integrating them must be key to any transition to XML or Web services.



At first glance, this seems to be a solved problem: XML databases have been available for some time; relational database vendors are also adding XML data type support to their offerings. What’s striking is that these products have so far gained only limited acceptance. This is less surprising when one realizes that the majority of relational databases are already running business-critical applications that need to be integrated with, not changed or replaced. Over time, XML may become the data format of choice for these applications, but for the foreseeable future the data will remain in the existing native formats and won’t be stored as XML.

This article focuses on what at first seems like a simple problem but turns out to be much more complex.

A Not-So-Simple Example

Imagine the simplest XML or Web services-based integration problem: An existing order processing database application needs to receive orders from another department or another company. The purchase order will have a number of segments, such as the sender’s contact details, the list of ordered items, order references and other terms.

Each order is part of an exchange of documents, and response documents such as acknowledgments or rejections must be returned to the requester before the transaction is completed. As you will see, even in this simple case there are potential “icebergs” that can sink the integration project.

The icebergs appear because the order processing application was originally designed to operate within a closed environment where the clients were coupled to the application. The set of messages between client and server is typically defined to closely match the database design. Moving to any integration-based architecture introduces a level of decoupling, as the messages being sent between the integrated systems are less likely to be directly mappable into the existing data definitions, since these predate the integration.

Moving to XML-based integration takes this decoupling further. The XML documents exchanged are typically defined entirely independently of the database design. This is because the documents are either industry-defined (e.g., FpML for financial services products such as foreign exchange contracts), based on company-wide standards or defined as part of an intercompany service agreement for B2B integration. This means the database application no longer has control of the incoming data that will need to be processed, and this data will no longer directly match its own data structures.

-1-

1  2  3  

   Next Page

Explore Our Topics

  • EDITOR'S BRIEFING
  • Virtual Conferences
  • Webinars
  • Roundtables

BPM in Action

March 10, 2011

The sixth annual BPM in Action 2011 Virtual Conference will explore cutting-edge market developments in BPM and describe how to leverage them for improved business operation and performance. More

View All Virtual Conferences

Smart Case Management: Why It's So Smart.

Date:Nov 05, 2009
Time:12:00 PM ET- (17:00 GMT)

REGISTER TODAY!

Date:Oct 29, 2009
Time:15:00 PM ET- (19:00 GMT)

REGISTER TODAY!
View All Roundtables
  • Research Library
  • Podcasts
  • News

Joe McKendrick: Part II of II: Designing Evolve-ability into SOA and IT Systems

In part two of Joe McKendrick's recent podcast with Miko Matsumura, chief strategist for Software AG, they talk about how SOA and IT systems need to change and grow and adapt with the organization around it.

Listen Now

Phil Wainewright: Helping Brands Engage with Social Media

Phil Wainewright interviews David Vap, VP of products at RightNow Technologies, and finds out how sharing best practices can help businesses understand how best to engage with online communities.

Listen Now

Peter Schooff: Making Every IT Dollar Result in a Desired Business Outcome: Scott Hebner of IBM Rati

Scott Hebner, Vice President of Marketing and Strategy for IBM Rational, discusses a topic on the top of every company's mind today: getting the most from IT investments.

Listen Now

Jessica Ann Mola: Where Will BI Fit In? Lyndsay Wise Explains

In BI, this tough economy and the increasing role of Web 2.0 and MDM are certainly topics on people's minds today. WiseAnalytics' Lyndsay Wise addresses each of them in this informative podcast.

Listen Now

Dennis Byron: Talking with...Deepak Singh of BPM Provider Adeptia

Deepak Singh, President and CTO of Adeptia, joins ebizQ's Dennis Byron in a podcast that gets its hand around the trend of industry-specific BPM.

Listen Now
More Podcasts
  • Most Popular
  • Quick Guide
  • Most Discussed

Quick Guide: What is BPM?

Learn More

Quick Guide: What is Event Processing?

Smart event processing can help your company run smarter and faster. This comprehensive guide helps you research the basics of complex event processing (CEP) and learn how to get started on the right foot with your CEP project using EDA, RFID, SOA, SCADA and other relevant technologies. Learn More

Quick Guide: What is Enterprise 2.0?

A lot of people are talking about Enterprise 2.0 as being the business application of Web 2.0 technology. However, there's still some debate on exactly what this technology entails, how it applies to today's business models, and which components bring true value. Some use the term Enterprise 2.0 exclusively to describe the use of social networking technologies in the enterprise, while others use it to describe a web economy platform, or the technological framework behind such a platform. Still others say that Enterprise 2.0 is all of these things. Learn More