Chapter Eleven. XML, XSLT, and Application Integration

XML is clearly a component of application integration and not a replacement, as once thought. XML's value is that it promotes a self-defining message structure that most organizations can agree upon, and many application integration architects are using it as a standard format for information exchange.

However, the real value of XML may not be XML itself, but XML derivatives such as ebXML, SOAP, and XML. These standards are still evolving, but they already add value in application integration problem domains.

In this chapter we'll explore the strategic value of XML as well as its transformation standard, XSLT, and their use in the world of application integration. This is a jumping-off point for the following chapters that will explore the ins and outs of XML-related standards.

Since its inception, Extensible Markup Language (XML) was designed as a standard for information interchange on the Internet; thus, its natural application in the world of application integration. Those interested in application integration look to leverage the power of XML, making this new standard a common point of integration for source and target applications.

For some time, XML was a bit confusing. Indeed, I've attended meetings where XML was thought to be the "magic" that will drive application integration, intra- and intercompany, for some enterprises. While XML is a powerful standard for structuring and exchanging information, its value within the world of application integration has proven to be more tactical than strategic. However, this does not mean that we should discount XML; indeed, it will always hold a place as both an information-exchange standard and a jumping-off point for additional standards, including ebXML, RosettaNet, and BizTalk all covered in this book.