1. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 1 Fundamentals of SOA

2. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 2 Business flexibility depends on flexible IT Systems, processes and relationships Business Increasing desire for some business activities to change direction rapidly Desire for more flexible business models and footprints The freedom to innovate and involve others in innovation IT Shifting focus of enterprise automation requirements Support product and service differentiation Support management and strategy Align sourcing and spend with business priorities Source: MWD

3. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 3 So what are we working with … Build Core systems Corporate payments Claims management Billing system 19701990 1980 1960 IT Focus Buy Supporting systems HR Payroll CRM Compose Business Infrastructure Process Automation SOA and Governance Integration Modernisation Web Services Integration 2000 20102020

4. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 4 The Philosophy of Services Oriented Architecture (SOA) SOA is about building systems out of parts. ¬ Parts provide some business logic. ¬ Parts expose application and data operations. ¬ Parts should be loosely coupled. IT & Business share common view of business process.

5. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 5 What is a service … a mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description.

6. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 6 SOA Defined: Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. OASIS SOA Reference Model Technical Committee

7. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 7 SOA Defined: Part One Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. OASIS SOA Reference Model Technical Committee

8. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 8 Stuff we need … 1. Service Enablement

9. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 9 Technical Services Finely Grained Application Semantics Leave and Layer May include application processes Application platform providers Bottom up Cataloging Technical Services You already have these In your network Whether you know it or not…

10. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 10 Business Services Coarsely Grained Business Semantics Enables Business Processes Top Down Decomposition Technical Services Requires deliberate design… 1 1 1 2 3 22 2 33 4 4 Business Services

11. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 11 SOA Defined: Part Two Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. OASIS SOA Reference Model Technical Committee

12. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 12 SOA Defined: Part Three Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. OASIS SOA Reference Model Technical Committee

13. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 13 Stuff we need … 1. Service Enablement 3. Service Registry 2. Service Access/Interaction

14. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 14 Finding and Using Services "SOA is a mess waiting to happen. By encouraging widespread reuse of scattered software components, SOA threatens to transform the enterprise network into a complex, sprawling, unmanageable mesh. Left ungoverned, SOA could allow anyone anywhere to deploy a new service any time they wish, and anyone anywhere to invoke and orchestrate that service--and thousands of othersinto ever more convoluted messaging patterns." James Kobielus, principal analyst at Current Analysis SOA could allow anyone anywhere to deploy a new service any time they wish, and anyone anywhere to invoke and orchestrate that service

15. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 15 Interdependence Can Destroy Agility Logical Unit of Business Work Start End ServiceEvent Handler (Sink) Event Notification (Alert) How can you change anything once everything is tied together?

16. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 16 The Dangers of Service Spaghetti "SOA is a mess waiting to happen. By encouraging widespread reuse of scattered software components, SOA threatens to transform the enterprise network into a complex, sprawling, unmanageable mesh. Left ungoverned, SOA could allow anyone anywhere to deploy a new service any time they wish, and anyone anywhere to invoke and orchestrate that service--and thousands of othersinto ever more convoluted messaging patterns." James Kobielus, principal analyst at Current Analysis complex, sprawling, unmanageable

17. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 17 Why all this complexity ?

18. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 18 Governance is key for SOA lack of working governance mechanisms in midsize-to-large (greater than 50 services) post-pilot SOA projects will be the most common reason for project failure … Jess Thompson, Research Director, Gartner

19. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 19 Stuff we need … 1. Service Enablement 3. Service Registry 2. Service Access/Interaction 4. SOA Governance

20. SOA Masterclass - Fundamentals of SOA |11 February 2009 | Page 20 Services (SOA Backplane) SAPLogistic Partner Rules Key applications … GUI Process