1. 2005 Adobe Systems Incorporated. All Rights Reserved. 1 The OASIS Reference Model for SOA Duane Nickull Senior Technical Evangelist Adobe Systems, Inc.

2. 2005 Adobe Systems Incorporated. All Rights Reserved. 2 Bio  Past:  Chief Architect - ebXML Technical Architecture (first major SOA)  Contributor - W3C Web Services Architecture  Chief Architect/Chair - United Nations CEFACT Technical Architecture (SOA)  Chair - OASIS eBusiness SOA Technical Committeee  Current  Chair - OASIS SOA Reference Model Technical Committee (OASIS Standard as of 2006)  Community Member - Ontolog Forum  Contributor - OASIS SOA Reference Architecture Technical Committee  Author (books, white papers, technical articles0  Speaker (Conferences, Universities …)

3. 2005 Adobe Systems Incorporated. All Rights Reserved. 3 Before we talk about SOA and where we want to go…  The tough questions:  If SOA is architecture, how do we express it as architecture?  Is it sufficiently different from other types of architecture?  If SOA is “X”, what is !(SOA || X ) ?

4. 2005 Adobe Systems Incorporated. All Rights Reserved. 4 1996 –remember this slide THING ONE THING TWO THING THREE The Internet

5. 2005 Adobe Systems Incorporated. All Rights Reserved. 5 This is what is looked like in 1998 THING ONE THING TWO THING THREE XML

6. 2005 Adobe Systems Incorporated. All Rights Reserved. 6 2002 – WS here to do the magic THING ONE THING TWO THING THREE Web Services

7. 2005 Adobe Systems Incorporated. All Rights Reserved. 7 2004 – SOA has arrived! THING ONE THING TWO THING THREE SOA

8. 2005 Adobe Systems Incorporated. All Rights Reserved. 8 2005 – now ESB will save us THING ONE THING TWO THING THREE ESB Event Driven Architecture Model Driven Architecture Ontology Semantic Web RIA’s Web 2.0, 3.0, 4.0 … Buzzwords Galore!

9. 2005 Adobe Systems Incorporated. All Rights Reserved. 9 So what is SOA exactly?  An Architectural Paradigm for organizing and using distributed capabilities that may be under the control of different ownership domains.  A framework for matching needs and capabilities.  A view of architecture focusing on “Services” as a mechanism to allows interactions between those with needs and capabilities.

10. 2005 Adobe Systems Incorporated. All Rights Reserved. 10 Core Model for SOA Starbucks?

11. 2005 Adobe Systems Incorporated. All Rights Reserved. 11 Primary Concepts for SOA (Semantics)  Service: A mechanism by which needs and capabilities are brought together.  Service Description: Artifact declaring all relevant aspects of a service required to interact with the service.  Capability: an ability to perform a specific set of functions resulting in a real world effect.  Visability: The capacity for those with needs and those with capabilities to see each other and interact.

12. 2005 Adobe Systems Incorporated. All Rights Reserved. 12 Core Concepts of SOA (DRAFT)  Execution Context: Set of technical/business elements that form path between those with needs and capabilities. Permits information to be exchanged, actions to be performed and provides a decision point for any policies and contracts that may be in force.  Policy: A set/range of constraints imposed on any entity when invoking a service. If ignored, the invocation request may be denied.

13. 2005 Adobe Systems Incorporated. All Rights Reserved. 13 Core Concepts of SOA (DRAFT)  Real World Effect: The result of an interaction with a service.  Interaction: the models for using the service.

14. 2005 Adobe Systems Incorporated. All Rights Reserved. 14 Service Interaction -> Behavior & Information Models Data Modeling is core. Ontological considerations are a primary concern!

15. 2005 Adobe Systems Incorporated. All Rights Reserved. 15 Real World Effect

16. 2005 Adobe Systems Incorporated. All Rights Reserved. 16 The OASIS Reference Model for SOA…  Is not architecture for a single SOA system.  It is not even architecture – it is a model!  Is an ABSTRACT model for a range of Service Oriented architectures and analysis / comparison thereof.  Is a framework for understanding significant relationships among the entities in a SOA environment.  Industry standard - widely used (OASIS standard - 2006)

17. 2005 Adobe Systems Incorporated. All Rights Reserved. 17 How does a Reference Model relate to other stuff? Web Services live here.

18. 2005 Adobe Systems Incorporated. All Rights Reserved. 18 Using a singular point of reference is good! Reference: A Reference Model acts as a point of reference for a domain. Durability: By not tying it directly to existing technologies it can be reused over a maximum set of environments.

19. 2005 Adobe Systems Incorporated. All Rights Reserved. 19 What does SOA enable? SOA + Platform + Patterns = Web 2.0

20. 2005 Adobe Systems Incorporated. All Rights Reserved. 20 Why we need this SOA aligns Technical and Business goals

21. 2005 Adobe Systems Incorporated. All Rights Reserved. 21 Abstract Model for Engagement Existing enterprise infrastructure Programming models and languages. Connectivity (Standards, Protocols and Technologies) Consistent architectural Models Consistent event and object Models Engagement Targets Service Tier Client side Technologies SOA Considerations: Governance Semantics/Ontology Security Policies Patterns Design/Human Interaction Search/Visibility Technology choices Granularity Transacted Services …

22. 2005 Adobe Systems Incorporated. All Rights Reserved. 22 Adding Design tools (Important Implementation idea) Existing enterprise infrastructure Programming models and languages. Connectivity (Standards, Protocols and Technologies) Consistent architectural Models Consistent event and object Models Target Service Tier Client side Technologies Technology Platform + Patterns of Interaction (MEP’s) ___________ = Web 2.0 Design Tools

23. 2005 Adobe Systems Incorporated. All Rights Reserved. 23 Service Capabilities Service Consumers What about BPM? Core SOA Business Process, State alignment, orchestration, choreography, etc.. Applications, ECM, DB, … In a layer diagram, layer “n” is only visible to layers (n +1) and (n – 1) VisibleVisible Not visible What services are used for Sources, functionality for capabilities

24. 2005 Adobe Systems Incorporated. All Rights Reserved. 24 End User Applications Service Endpoints Services Admin & Monitor Databases ECM Repository Message Queues Legacy Systems Customer Applications/System s Service Container Registry Repository Orchestration Job Management Monitoring Auditing Versioning Core Libraries Expense Approval Mortgage Loan Directories SPI Extensibility Reader Extend Secure Document Generate PDF Assemble Docs Forms … … Invocation Layer... Web Admin Web Services Watch Folders JMS Queues Email Flex Reader Portals IDE Architectural Best Practices Java SDK Client SDK FDS Adapters -RPC -Messaging -DataSync Form Design Process Modeling EIS

25. 2005 Adobe Systems Incorporated. All Rights Reserved. 25 Patterns and Ontological considerations  SOA is more than Request Response!  Auditable Event Subscription, Push, pull, drag, mine, broadcast, unicast, multicast, mashups, probe & match, ….  Inference based event notification  CEP - causality relationship (orthogonal n-ary relationship inference)  STRONG REQUIREMENT FOR FIRST ORDER OF LOGIC!  Example of specific types of relationships from SUMO (expressed in SUO-KIF)  ( (Symmetric R) (forall (?x ?y) (=> (R ?x ?y) (R ?y ?x)))) ( (Coreflexive R) (forall (?x ?y) (=> (R ?x ?y) (= ?x ?y))))

26. 2005 Adobe Systems Incorporated. All Rights Reserved. 26 I.D.E.A. UML Class view diagram (high level only) Model for computational intelligence enabled by SOA

27. 2005 Adobe Systems Incorporated. All Rights Reserved. 27 Future of OASIS SOA Work The OASIS SOA Reference Architecture

28. 2005 Adobe Systems Incorporated. All Rights Reserved. 28 OASIS SOA RA - What is it?  200 ++ concerned community members working on a reference architecture.  Mapping SOA to concrete technology families.  Tackling:  Service Description, Governance, Ontologies, Semantics, Service Level Agreement, …. (LOTS more)  An activity that benefits from larger input.

29. 2005 Adobe Systems Incorporated. All Rights Reserved. 29 SLA  Definition of Services  Problem Management  Performance Management  Customer Duties and Responsibilities  Warranties and Remedies  Service quality  Indemnities  Third party claims  Remedies for breaches  Exclusions  Force majeure  Security  Information Security Policies  Security Audit and Internal Audit  Disaster Recovery  Termination

30. 2005 Adobe Systems Incorporated. All Rights Reserved. 30 Q&A  Q&A?

31. 2005 Adobe Systems Incorporated. All Rights Reserved. 31 References  OASIS SOA RM TC - http://www.oasis- open.org/committees/tc_home.php?wg_abbrev=soa-rmhttp://www.oasis- open.org/committees/tc_home.php?wg_abbrev=soa-rm  Free SOA White Papers - http://www.adobe.com/cfusion/search/index.cfm?loc=en_us&term=soa http://www.adobe.com/cfusion/search/index.cfm?loc=en_us&term=soa  Adobe LiveCycle - http://www.adobe.com/products/livecycle/ http://www.adobe.com/products/livecycle/

32. 2005 Adobe Systems Incorporated. All Rights Reserved. 32 Adobe’s Exchange Platform.  Thank you

33. 2005 Adobe Systems Incorporated. All Rights Reserved. 33