XML to the rescue: Data governance in SOA

Amidst all the hype and buzzwords that surround SOA nowadays, it's still far too common for organizations that seek to integrate service-oriented architecture into their IT infrastructure to omit issues related to data integration, management and governance in their designs. As they roll out and learn to live with an SOA, however, they often discover that interoperability with other systems and solutions poses interesting problems. In fact, these problems can make interaction between systems and SOA components both vexing and time consuming.

The key is to recognize the value of the organization's data, wherever it may reside—that is, either beneath or outside the SOA umbrella—and to come up with methods that enable them to capture and transport data between its producers and consumers with a minimum of muss and fuss. This creates what Gartner calls a data-services-oriented view of SOA, and that firm predicts that this view is bound to become a critical component in SOA initiatives going forward, as well as a critical upgrade for existing ones that failed to take this view properly into account.

By creating metadata and data representations using XML, and then building XSLT applications to transport them into and out of SOA components, developers gain numerous advantages:

XML and messaging protocols such as SOAP indeed make it easier to abstract the data and move it around. But they also raise the importance of where data resides, how it gains (or retains) proper context, and how to associate specific syntax, semantics and accuracy checks against the real-world information it represents. This creates the need for what som

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Data governance and management for SOA Kapow bows data-driven server for the enterprise SOA needs a Product Manager Medical imaging group build HL7 messaging hub with InterSystems Ensemble New TOGAF framework released Podcast: SearchSOA tips on software architect skills Domain bridging, skills of abstraction define the software architect Amazon Mechanical Turk Web services app touts improved development GUI REST architecture integrates data services to SaaS Architecture 101: Why SOA needs an enterprise focus SOA ends era of big apps, opens door for Ruby on Rails XML and XML schema SOA pattern of the week (#7): policy centralization Try XML-based Extensible Business Reporting Language (XBRL) for accounting reports What's new at the W3C Ganymede: Modeling tools target SOA, UML Data services mashups emerge for SOA Making sense of data services mashups XML turns 10 SOA helps save 100-year-old business Oracle maps heterogeneous data services strategy for SOA Handling XML with Ajax Guest Commentary Getting a grip on JavaFX 1.2 for Rich Internet Applications (RIA) On the road to SOA – Part 1, Boubez on early insights On the road to SOA – Part 2, Governance is fundamental SpringSource approach to adding enterprise class management and deployment features to Tomcat SOA Pattern of the Week (#6): Canonical Schema Legacy: Can't Live With It, Can't Live Without It Review of protocols for cloud services - Part 1 SOA and TOGAF: A Good Fit? Using atomicity to gain SOA granularity Too Many Servers: A Case for Enterprise Architecture and TOGAF 9

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary class diagram  (SearchSOA.com) Fast Infoset (FI)  (SearchSOA.com) GeoRSS  (SearchSOA.com) Keyhole Markup Language  (SearchSOA.com) RELAX NG  (SearchSOA.com) state diagram  (SearchSOA.com) Universal Business Language  (SearchSOA.com) Vector Markup Language  (SearchSOA.com) XML infoset  (SearchSOA.com) XML pipeline  (SearchSOA.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

e experts call "XML-centric composite data services" which handle the primitives needed to make data available in an SOA environment, including data access, integration, transformation (federation, abstraction, filtering, etc.), validation and verification, quality control, and governance. This approach lets organizations use XML-centric, data-driven workflow design tools that may then be deployed and managed using an XML-centric workflow engine.

In addition to using the right tools and applying the right business rules, it's also important for organizations to recognize that XML-based descriptions only work as well as the people who design them make them work. This means that talented, capable data architects and data governance professionals must be involved in creating the right kind of representations, as well as the processes whereby data is captured, validated, maintained and distributed. In addition to XML representation, XML-oriented databases, XQuery, and a formal data service approach to handling data within the SOA framework, as well as a dedicated team of data specialists and stewards to make sure that what's available matches what's needed, and to keep data repositories cleaned-up, refreshed and accurate over time.

About the author

Ed Tittel is a full-time writer and trainer whose interests include XML and development topics, along with IT Certification and information security topics. Among his many XML projects are XML For Dummies, 4th edition, (Wylie, 2005) and the Shaum's Easy Outline of XML (McGraw-Hill, 2004). E-mail Ed at etittel@techtarget.com with comments, questions or suggested topics or tools for review.