1. Service Oriented Architecture Terry Woods Session 50

2. 2 Agenda The Problem What is Service-Oriented Architecture? Change is Inevitable What is an Enterprise Service Bus? Summary

3. The Problem

4. 4 Legacy Business Process

5. 5 Architectural Choke Point Monolithic Extremely complex Very tightly coupled Difficult to find clean integration points Lack of standards makes it difficult to integrate Rigid architecture makes even small changes complex and costly

6. 6 SOA Business Process

7. What is Service-Oriented Architecture?

8. 8 Service-Oriented Architecture (SOA) is an architectural style. Applications built using an SOA style deliver functionality as services that can be used or reused when building applications or integrating within the enterprise or trading partners.

9. 9 What is a Service? A service provides a discrete business function that operates on data. Its job is to ensure that the business functionality is applied consistently, returns predictable results, and operates within the quality of service required.

10. 10 Characteristics of a Service Supports open standards Loose coupling Stateless Location agnostic

11. Change is Inevitable

12. 12 IT is like an Ecosystem COBOL C++ Java J2EE Networks TCP/IP Web Service Mid-Tier Servers.NET Messaging HTML Operating Systems CICS Routers Databases Mainframes

13. 13 Managing the Ecosystem Technology Management Product duplication Standards Product/Vendor lock-in Support skill sets Version Management Managed Evergreening Limited versions in production

14. 14 Legacy Integration

15. 15 SOA Integration

16. 16 Integration Stack Industry Standards Language Standards Custom API’s Native Interfaces

17. Enterprise Service Bus

18. 18 What is an Enterprise Service Bus (ESB)? An ESB implements an SOA through middleware that offers virtualization and management of service interactions between communication participants. Thus, this flexible connectivity layer could help connect and integrate an organization's IT infrastructure across many differing systems and locations reliably and securely while reducing the number, size and complexity of application interfaces. ComputerWorld (http://www.computerworld.com/developmenttopics/development/webservices/story/0,10801,108478,00.html)

19. 19 Key Characteristics of an ESB Streamlines development Supports multiple binding strategies Performs data transformation Intelligent routing Real time monitoring Exception handling Service security

20. 20 Mediation Source: Getting Started with WebSphere Enterprise Service Bus V6 http://www.redbooks.ibm.com/redbooks/SG247212/wwhelp/wwhimpl/java/html/wwhelp.htm

21. 21 Manage Subscriptions to Organization Data

22. 22 Distribute New Organization Data

23. 23 Distribute New Organization Data with Human Interaction

24. 24 Service Enablement of Managed File Transfer

25. 25 Schema Validation Approaches

26. 26 Understanding the Technology Stack

27. 27 ESB Conceptual Architecture

28. 28 Describing Services to Machines Web Services Description Language Open Standard for describing Interfaces to Services (http://www.w3.org/TR/wsdl) Characteristics –Describes data expected to be sent and received –Describes what the service can do –Describes how to reach the service WSDL description is an XML document

29. 29 ESB Summary Loose Coupling Location Transparency Transport Neutral

30. 30 Summary The Problem What is Service-Oriented Architecture? Change is Inevitable What is an Enterprise Service Bus? Summary

31. 31 I appreciate your feedback and comments. I can be reached at: Name: Terry Woods Phone: 202-377-3023 Email: Terry.Woods@ed.gov Contact Information