11.07.2015 Views

y - Net Developer

y - Net Developer

y - Net Developer

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

amrameshreddy.blog.comTable 13-1. Vendor Implementation of WS-* StandardsVendor/Product MTOM? WS-Security? WS-ReliableMessaging?Microsoft Yes Yes YesIBM No Yes YesBEA Yes Yes YesSun Yes Yes NoApache Yes Yes YesTibco No Yes NogSOAP Yes Yes NoOne of the earliest interoperability efforts was to implement the WS-I Basic Profile. Whatis the WS-I Basic Profile? You’ll dive into that topic now.Interoperability with WS-I Basic ProfileIn the beginning stages of the industry’s implementation of the standards, people recognizedthat many of the stacks had been built upon an inconsistent foundation of technologies. Somevendors had chosen different versions of WSDL or SOAP as examples. Even how SOAP faultswere returned by each implementation had been done differently in each implementation. So,getting interoperability amongst different implementations was a substantial challenge. Inmany instances, it was impossible without a significant amount of custom coding. Given theamount of coding required, it precluded the need for a vendor implementation and threw thewhole “build vs. buy” question heavily in favor of in-house development when interoperabilitywas required.The early vendor SOA frameworks did not conform to common open standards (in otherwords, they were vendor specific). This was mostly because of both customer and marketdemands. However, this was a major obstacle to achieve “true” interoperability betweenmultiple vendors.The major industry participants combined resources forming the Web Services Interoperability(WS-I) Organization to facilitate and move web service standards forward in a nonproprietaryand open manner. WS-I consists of a mix of products, services, and most important,user corporations—the primary focus of why we as solution architects exist. Currently,approximately 90 organizations are participating, with nearly 30 percent comprised of usercorporations. 6 We’ll discuss the core components of the Basic Profile in the next section.Core ComponentsCHAPTER 13 ■ IMPLEMENTING SOA INTEROPERABILITY 403In April 2004, WS-I released Basic Profile 1.0. 7 This set of specifications laid the groundwork forvendors and customers to begin from a sound base. The specification represents the first generationof interoperable web service specifications. The importance of the Basic Profile cannot beminimized because with the initial release, many product companies and open source groupsrecognized that the market will no longer allow stand-alone proprietary interoperability stacks.ramrameshreddyramrameshreddy6. This is based upon WS-I.org information as of June 12, 2006.7. You can find the WS-I Basic Profile 1.0 home page at http://www.ws-i.org/Profiles/BasicProfile-1.0.html.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!