1. SOA-6: Standards for Service-Oriented Architecture Glen Daniels Standards Strategist, Sonic

2. © 2006 Progress Software Corporation2 SOA-6: Standards for SOA Agenda  SOA in a Nutshell  The Need for Standards  The Standards Landscape  Key Standards for SOA Today  Mediation : A Brief Interlude  Key Standards for SOA Tomorrow  Summary

3. © 2006 Progress Software Corporation3 SOA-6: Standards for SOA SOA in a Nutshell (“ities”)  “Same Old Architecture”?  Modularity  Composability  Interoperability  Coarse-grained business components  OpenEdge Reference Architecture.NET Java OpenEdge

4. © 2006 Progress Software Corporation4 SOA-6: Standards for SOA Shared Models = Interoperability  Physical communication channels  Data formats  Protocol framing / MEPs  QoS (security, reliability, etc)  Component interfaces  Policies  Semantics  ALL of this needs to be agreed upon!

5. © 2006 Progress Software Corporation5 SOA-6: Standards for SOA The Need for Standards  Standards provide the common structure components require in order to work together  Standards are the fuel which makes SOA go

6. © 2006 Progress Software Corporation6 SOA-6: Standards for SOA Agenda  SOA in a Nutshell  The Need for Standards  The Standards Landscape  Key Standards for SOA Today  Mediation : A Brief Interlude  Key Standards for SOA Tomorrow  Summary

7. © 2006 Progress Software Corporation7 SOA-6: Standards for SOA Landscape: Types of Standards  De Facto / De Jure  Wire-level standards (WS-*, EDI)  Data standards (XML, SQL, ProDataSet™)  API standards (DOM, JAX-RPC, Apache)  Metadata standards (WSDL, WS-Policy)  Design standards (UML)

8. © 2006 Progress Software Corporation8 SOA-6: Standards for SOA Landscape: Who’s Working on What?  World Wide Web Consortium (W3C) XML, Web Services core, Semantic Web  OASIS WS-*  IETF Email, HTTP, TCP, etc.  WS-I Interoperability “profiles”  JCP Java APIs  Open Source Communities De facto “standards” (Apache, Eclipse, etc)

9. © 2006 Progress Software Corporation9 SOA-6: Standards for SOA Specifications != Standards  Open Standards consortia are the best places to get tech IPR policy is clear Community has had a chance to vet specs  …but innovation requires that consortia aren’t the only place to get tech Individual companies or small groups publish specs before “de jure” standardization Distributed evolution

10. © 2006 Progress Software Corporation10 SOA-6: Standards for SOA Agenda  SOA in a Nutshell  The Need for Standards  The Standards Landscape  Key Standards for SOA Today  Mediation : A Brief Interlude  Key Standards for SOA Tomorrow  Summary

11. © 2006 Progress Software Corporation11 SOA-6: Standards for SOA SOA and Web Services  Web Services have broad industry agreement  Based on XML, common data model  Composability baked in to the core Versioning Distributed evolution

12. © 2006 Progress Software Corporation12 SOA-6: Standards for SOA Web Service Patterns : Bindings  Web services can be “bound” to different underlying protocols  Bindings also provide the ability to control policy/metadata  Separation of concerns  This provides a lot of flexibility – the same abstract model can be used while the underlying implementation is switched/updated over time Binding Service Abstract OpenEdge Concrete SOAP HTTP WS-Security

13. © 2006 Progress Software Corporation13 SOA-6: Standards for SOA Web Service Patterns : MustUnderstand  Extensions can be optional (this is available) or mandatory (you must do this).  Allows extensions to CHANGE critical behaviors in a safe way  Must understand allows distributed extensibility Different extensions at different times, from different sources  This model allows “fast fail”, which really helps us humans do debugging

14. © 2006 Progress Software Corporation14 SOA-6: Standards for SOA Key Standards For SOA Today : WSDL  Web Service Description Language  W3C  Machine readable contract  Metadata about services  Address of endpoints  Interface  Message structure  Data types

15. © 2006 Progress Software Corporation15 SOA-6: Standards for SOA Key Standards For SOA Today : SOAP  W3C  XML Envelope with Headers and Body  Headers contain extensions – security, transactions, etc…  Processing Model with mandatory or optional extensions  Bindings to protocols like HTTP, Email, JMS, etc…

16. © 2006 Progress Software Corporation16 SOA-6: Standards for SOA Key Standards For SOA Today : WS-Addressing  W3C  SOAP version of familiar concepts : TO, FROM, REPLY- TO, etc…  Endpoint References can contain policies, metadata, “cookies” (Reference Parameters)  Allows responses to be delivered along separate connections (asynchronously)  Allows composition of multiple interactions (process)

17. © 2006 Progress Software Corporation17 SOA-6: Standards for SOA Key Standards For SOA Today : WS-Policy  W3C (finally!)  Capabilities and Requirements metdata  “I support reliability”  “I require authentication”  Group sets of assertions into policies  Refer to policies from WSDL, in EPRs, etc. …

18. © 2006 Progress Software Corporation18 SOA-6: Standards for SOA Key Standards For SOA Today : WS-Security  OASIS  Message-level security  Encryption  Authentication (XML Digital Signature)  End-to-end, not point-to-point  Profiles for simple uname/password, SAML, Kerberos, etc

19. © 2006 Progress Software Corporation19 SOA-6: Standards for SOA Key Standards For SOA Today : WS-RM  OASIS  Builds reliable sequences of messages over unreliable transports  Needed to ensure duplicate detection, ordering, etc… A B

20. © 2006 Progress Software Corporation20 SOA-6: Standards for SOA “Where’s My Flying Car?”  How far along is all this anyway? Basic WS mostly works today “Advanced” WS almost there  Policy-driven process-oriented integration will take a little longer  Even when a “stack” has stabilized, change will be a factor (thank goodness!)…

21. © 2006 Progress Software Corporation21 SOA-6: Standards for SOA Mediation : A Brief Interlude Consumer Intermediary Service

22. © 2006 Progress Software Corporation22 SOA-6: Standards for SOA Mediation : Benefits  Limits unnecessary tight coupling Separates concerns  Manages evolution Insulates you from external changes Allows you to make internal changes  Leverage existing assets in new ways  Adapts message patterns, protocols, data formats, etc.

23. © 2006 Progress Software Corporation23 SOA-6: Standards for SOA Mediation : The Enterprise Service Bus SONIC ESB ® ENTERPRISE SERVICE BUS OPENEDGE APPLICATION PACKAGED APPLICATION & LEGACY SYSTEMS.NET™ APPLICATION PARTNER SYSTEM WEB SERVICE

24. © 2006 Progress Software Corporation24 SOA-6: Standards for SOA Agenda  SOA in a Nutshell  The Need for Standards  The Standards Landscape  Key Standards for SOA Today  Mediation : A Brief Interlude  Key Standards for SOA Tomorrow  Summary

25. © 2006 Progress Software Corporation25 SOA-6: Standards for SOA WS-Eventing / WS-Notification Asynchronous event processing Specs will eventually merge Consumer Event Generator Service 1. Subscribe() 2. Notify()

26. © 2006 Progress Software Corporation26 SOA-6: Standards for SOA Management (WSDM/WS-Management) Interoperable control and monitoring Specs will eventually merge

27. © 2006 Progress Software Corporation27 SOA-6: Standards for SOA WS-SecureExchange (WS-SX)  WS-SecureConversation Secure “sessions”  WS-Trust Allow different domains to “vouch” for users  In OASIS now

28. © 2006 Progress Software Corporation28 SOA-6: Standards for SOA WS-Transactions (WS-TX)  Coordinating multiple resources over SOAP  AtomicTransactions == 2-phase commit  BusinessActivity == long running transactions  In OASIS now

29. © 2006 Progress Software Corporation29 SOA-6: Standards for SOA Business Process Execution Language (BPEL) Process definition/execution language Allows sharing process descriptions OASIS

30. © 2006 Progress Software Corporation30 SOA-6: Standards for SOA SCA Language-neutral application assembly model

31. © 2006 Progress Software Corporation31 SOA-6: Standards for SOA XQuery Rich language for manipulating XML data Turing-complete (control flow, functions, etc)

32. © 2006 Progress Software Corporation32 SOA-6: Standards for SOA Progress Plays Here  Participants from the Progress family are active in many of these specs/groups  As the landscape evolves, we’ll help you get there

33. © 2006 Progress Software Corporation33 SOA-6: Standards for SOA In Summary  SOA is an architectural pattern that needs standards to make it real and interoperable  Web Services are the way that happens (for today)  Architecture lasts, though individual standards will evolve Use OpenEdge Reference Architecture Progress/Sonic has your back Mediate and insulate!

34. © 2006 Progress Software Corporation34 SOA-6: Standards for SOA Relevant Exchange Sessions  SOA-12: OpenEdge Web Services David Lund  INNOV-10: Introduction to XQuery Gus Bjorklund

35. © 2006 Progress Software Corporation35 SOA-6: Standards for SOA Questions?

36. © 2006 Progress Software Corporation36 SOA-6: Standards for SOA Thank you for your time

37. © 2006 Progress Software Corporation37 SOA-6: Standards for SOA