1 / 24

WS-* Specifications Update

WS-* Specifications Update. Producing proven, well-engineered, quality Web services specifications. Jorgen Thelin Senior Program Manager - Interoperability Standards Connected Systems Division Microsoft Corporation. Partner. Clearing House. SAP. Services. Database.

hea
Download Presentation

WS-* Specifications Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WS-* Specifications Update Producing proven, well-engineered, quality Web services specifications Jorgen Thelin Senior Program Manager - Interoperability Standards Connected Systems Division Microsoft Corporation

  2. Partner Clearing House SAP Services Database Many Systems == Development & Management Complexity Your Enterprise HIPAA EDI Siebel Oracle LOB RosettaNet HL7 JD Edwards SAP Swift (etc.) FTP TCP/IP SNA WS-* HTTP LDAP MQI Oracle DB Tibco XML TN3270 DRDA Teradata IBM DB2 Remote Store UPnP Clarify RLIO IBMMainframe Directory

  3. Agenda • Overview of Microsoft’s WS Strategy • WS-* Specification Development Process • WS-* Workshops • WS-* Spec Progress • Delivering WS-* Implementations • Microsoft Customer Interop Executive Council (IEC)

  4. It gives customers control over the data they create and want to share The nature of software allows for translatability in lieu of uniformity Vendors create innovative solutions that bridge technologies to address real customer needs in an innovative manner Interoperability means connecting people, data, and diverse systems

  5. Why Interoperability? • Interoperability is • Connecting People, Data and Diverse Systems • http://www.microsoft.com/interop/ • Interoperability is now as important to must customers as security or reliability • But interoperability is still just a means to an end • Interoperability helps to: • Reduce costs / Improve operational efficiencies • Open access to new markets / Enable new business opportunities / Increase agility • Maximize choice of solutions and vendors • Ensure access to data across all applications

  6. Data Formats Protocols Metadata Enabling Wire Interoperability

  7. Microsoft’s Commitment to Interoperability • Bill Gates’ Executive E-mail – February 2005 – “Building Software That Is Interoperable By Design” http://www.microsoft.com/mscorp/execmail/2005/02-03interoperability.asp • Plus deep commitment at the execution level • Specification development and standardization • WS-* Spec authorship • Participation in Standards bodies – W3C, OASIS, DMTF, etc, etc • Participation in WS-I – Web Services Interoperability Organization • Shipping products: • Early WS-* implementations (WSE) • Strategic WS-* platform (WCF – Windows Communication Foundation) • Easy-to-use development environment (Visual Studio) • Community feedback and testing • WS-* Workshop Process • Plug-fests - Product testing of multi-vendor interop • Adopting XML and WS-* as the universal glue • eg. Systems Management, Connected Devices, Identity Management

  8. Feedback and Interop Workshops Specification Published Revise spec Standards Org WS-I, ITU, ACORD WSP Idea Increasing Industry Participation WS-* Specifications Process Step 1 InitialDevelopment Step 2Broader Community Participation Step 3 Standardization Step 4 Profiling • Process reconciles conflicting goals • Quality of engineering • Time to market • Breadth of industry support

  9. Why WS-* Workshop Process? • Main reason for the WS-* workshop process • Produce well-engineered, quality specifications • Secondary benefits of WS-* workshops: • Proof of the interoperability of the WS-* specifications • Discover inconsistencies with other WS-* specifications • Gain implementation experience earlier • Foster community involvement • Apply software testing disciplines to specs • Determine readiness for standardization

  10. Workshop Types • Feedback Workshops • Open to everyone • Obtain community feedback on specifications • Interoperability Workshops • Open to teams with implementations • Demonstrate / prove spec interoperability • Refine the important spec scenarios • Ground the spec development efforts

  11. WS-* Specs & Workshops Typical Steps: • Spec is developed among a small number of companies • 1st Publication – publicly available • Feedback Workshop • 2nd Publication – publicly available • Interop Workshop • 3rd Publication – publicly available • Submission to standards org

  12. WS-* Workshop Process History The SOAP and WSDL specifications proceeded through a prototype version of the workshop process during 2001 and 2002 This experience led to the refined and formalized WS-* workshop process now in use.

  13. 80+ WS-* Workshop Participants

  14. Workshop Results • Workshop Results – WS-RM • 1 Feedback Workshop • 3 Interop Workshops • 14 Workshop Participants • Apache, BEA, Blue Titan, Fujitsu, IBM, Iona, Microsoft, NEC, RogueWave, SAP, SeeBeyond, Sonic, Systinet, TIBCO • 9 Workshop Implementations • Apache Axis, BEA, Blue Titan, IBM, Microsoft, SAP, Sonic, Systinet, TIBCO • 7 Main Interop Scenarios (plus variants) • At least 7 Shipping Products • Apache Axis, BEA, Blue Titan, Cape Clear, IBM, Microsoft, Systinet • Spec submitted to OASIS TC – June 2005 • Workshop Results – It works! • Independent comment on the effectiveness of the WS-* Workshops Process for developing better specs: • “Early discussions and workshops … led to some detailed changes in the [WS-RM] specification, and therefore animproved specification to submit to a standards body.” Peter Abrahams, Bloor Researchhttp://www.it-analysis.com/article.php?articleid=12692

  15. Step 2 – Workshops & Community Dev WS-* Spec Status Step 3 – Standardization Step 4 – Approved Standard Infrastructure and Profiles Metadata WS-Federation WS-Management Devices Profile WS-Metadata Exchange Assurances WS-Secure Conversation WS-Business Activity WS-Discovery WS-Trust WS-Atomic Transaction UDDI WS-Security WS-Reliable Messaging WS-Coordination WS-Policy Messaging WS-Transfer WS-Enumeration WS-Eventing WSDL SOAP WS-Addressing MTOM XML Schema Foundation XML Infoset SOAP / UDP XML 1.0 XML Namespaces MIME SOAP / HTTP

  16. WS-* Protocols - Industry Adoption WS-D DPWS WS-RM WS-AT Devices Assurances SOAP/WSDL WS-SecureConv MTOM Messaging WS-Security WS-Trust WS-Fed Security MEX UDDI WS-P Metadata WS-XFer / Enum WS-Man System Mgmt © 2003-2007 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view at the time of publication and is subject to change.

  17. Delivering WS-* - Microsoft • Microsoft is delivering implementations of all WS-* specs • WSE 2.0 / 3.0 • Interim coverage of evolving security and policy specs • WCF – Windows Communication Foundation / .NET Framework 3.0 / 3.5 • Full coverage of all SRTP Advanced Web Services specs • Security • Reliable Messaging • Transactions • Policy • Web Services Protocols Supported in WCF 3.5 • http://msdn2.microsoft.com/en-us/library/ms730294(vs.90).aspx • Windows Server 2003 Release 2 • WS-Management stack for interoperable system management • Windows Vista • Includes .NET Framework 3.0 / WCF pre-loaded • WS-Devices stack for printer and networked device connectivity

  18. Key Products Shipping WS-* Support • BEA – WebLogic App Server • IBM – WS-* Feature Pack for WebSphere • Novell – Open Enterprise Server • Oracle – Oracle App Server Containers for JavaEE (OC4J) • Red Hat – JBoss App Server • SAP – NetWeaver App Server • Sun – GlassFish / Web Services Interoperability Technologies (WSIT/Tango) • Apache Group – Axis 2 • WSO2 – Axis 2 / WSO2 Web Services App Server

  19. Interoperability Executive Customer Council • Bob Muglia, SVP Server & Tools is host and member • 30+ members, 2 plenary meetings, 20+ tech meetings • Aetna • American Express • Bank of America • Boeing • Booze Allen Hamilton • Carnival Cruise Lines • Danish Ministry of Finance • European Commission • Fidelity • Ford • Fraunhofer-Institute FOKUS • Goldman Sachs • Hesse Ministry of Finance • Hong Kong Government • Johnson & Johnson • Kohls • Lexis Nexis • NATO • Novartis • PriceWaterhouseCoopers • Raytheon • Sao Paolo Ministry of Justice • Siemens • Societe General • Swedish Social Insurance Administration • UNICEF • World Health Organization

  20. IEC Workstreams Workstream In progress Resolved

  21. IEC Major Findings & Open Issues Presence of Java on mainframe/UNIX/Linux alongside .NET • Run multiple frameworks on a single runtime environment • Allow .NET framework to run on non-Windows platform (mono) • Built-in support for third-party tools in Visual Studio and other products • Need for ECM features (workflow, search, record management) to work across multiple servers • Management of virtualization environments from a single console and integration with VMWare • Need evidence of wider support and adoption of WS-* standards and high-performance implementations • SAML and other standards support Need for interoperability among multiple development tools Interest in development of WS-* standards Desire to federate user identity across heterogeneous environments Presence of multiple document and content management servers Eagerness to optimize management of heterogeneous environments

  22. Summary • All WS-* specs are progressing through the WS-* Workshop Process • WS-* Workshops Process drives specification revision • Yields well-engineered specifications in a timely manner • Microsoft is delivering implementations for the WS-* specs • Many other vendors also delivering implementations for WS-* specs too • WS-* specs becoming part of the normal plumbing for connected systems dev

  23. Links • WS-* Workshop Process Overview • http://msdn.microsoft.com/library/en-us/dnwebsrv/html/wkshopprocess.asp • WS-* Workshops home page • http://msdn.microsoft.com/webservices/community/workshops/ • Microsoft Interoperabilty home page • http://www.microsoft.com/interop • WS-* Specifications index page • http://msdn.microsoft.com/webservices/understanding/specs/ • MSDN Web Services Developer Center • http://msdn.microsoft.com/webservices/

  24. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related