Web Service and Service Oriented Architecture

1. Literature Review for CSC8350 Web Service and Service Oriented Architecture Students: Hailong Hou and Yiwei Wu Instructor: Xiaolin Hu

2. Outline SOA What & Why SOB Concepts Safeco Case Study

3. Conventional approach

4. Problems of application integration • Core legacy applications supporting the business are old, inflexible, and brittle • Minimal system documentation • Skill drain for qualified support staff • Monolithic silos of application development • No standards for design or architecture • No standards for data storage and data movement between systems • Tight integration of systems with high degrees of interdependence • Long development cycles for applications and enhancements

5. Pictorial View of SOA SOA is a journey not a destination.

6. Introduction to Web Service • A Web Service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-process able format. Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.

7. Benefits of Web Service Integration

8. What’s SOA • A service-oriented architecture is an information technology approach or strategy in which applications make use of web services. • A service-oriented architecture is a way of sharing functions (typically business functions) in a widespread and flexible way.

9. Relation between Web service and SOA • SOA is also often equated with Web services, and the terms used interchangeably. • SOA is an approach to designing systems—in effect the architectural drawings or blueprint—that directs how IT resources will be integrated and which services will be exposed for use. • Web services is an implementation methodology that uses specific standards and language protocols to execute on a SOA solution.

10. SOA infrastructure

11. Three phases of SOA development

12. Why SOA makes Sense: Technical view • Building business processes faster and cheaper -Applications can access their services in standard way. -Existing services can more easily be reused. • Applications can be exposed more easily to diverse clients

13. Why SOA Makes Sense: Business Benefits • Business people understand services. -So IT people can talk with them more easily. • Business processes become explicit. -So they can more easily be understood and improved • Applications or business processes might be more easily outsourced. -Because they’re well-defined and discrete.

14. Benefits of SOA

15. Benefits of SOA

16. Challenges associated with SOA • Insufficient attention to governance—the management and monitoring of services, their performance and reliability, and especially their security • Reuse of services, once touted as a primary SOA advantage, is really a byproduct of the approach rather than the goal itself. • requires accurately predicting what future needs will be

17. Concept of Service Oriented Business • Service-Oriented Business (SOB) refers to a business process using the principles of Service Oriented Architecture (SOA) to Business Applications. Motivated by the key concepts for service-oriented business thinking through a range of examples that give a flavor of a range of businesses. • Three Key concepts of SOB • Service Agreement • Service Transaction • Service Function

18. Concept of Service Oriented Business • Service Agreement:-It contains all the details of the contract that the two parties need to enter into in order to have a service business relationship. This includes description of all the services that may be obtained (these are Service Functions), the pricing as well as the billing mechanisms, and the required quality of services. In short, this will include what in business is thought of as “terms and conditions”. • Service Transaction:-Once a service agreement has been activated, business can start. Services can now be obtained as per the terms laid out in the agreement. We use the term Service Transaction as a business analog for the well known notion of database transactions.

19. Concept of Service Oriented Business • Service Functions:-They are the operational pieces that are used to create a service transaction. These are the basic building blocks of a business that is realized entirely through the execution of service transactions.

20. Service design for SOB(service oriented business) Relation between consumer and service provider

21. Service design for SOB(service oriented business)

22. Case study: Composite Applications at Safeco • Safeco is an Insurance company, headquartered in Seattle which provides auto, homeowners and small-business policies. • In early 2006, Safeco initiated the development of a Service Oriented Architecture to support the business in two strategic areas: new product development and business process improvements.

23. Case study (cont.) In the context of this project, Safeco has chosen Microsoft Windows Communication Foundation for the Enterprise Services tier, IBM WebSphere Process Server for the process tier and ASP.Net for the presentation tier

24. Case study (cont.) The current Motor Vehicle Registry (MVR) system Verification Unit

25. Case study (cont.) • The proposed MVR system

26. Case study (cont.) • Five Steps: • 1. MVR Reconciliation Solution • 2. Process Modeling, Simulation, Execution • 3. MVR Record merging • 4. Microsoft / IBM interoperability • 5. Security Interoperability

27. Case study (cont.) • First step: MVR Reconciliation Solution • 1. Develop a To-be-Is model: The To-Be business process was imported to create the initial BPEL implementation of the process. Two main services participated in the solution: the MVR record matching service and the Policy service. • 2. Each day an MVR file is uploaded in one of the legacy system. Every morning the WebSphere Message Broker processes this file and invokes the Process Server instance to create a business process instance for each policy identified by an MVR record.

28. Case study (cont.) • The MVR Solution Technical Architecture

29. Case study (cont.) • Step2: Process Modeling, Simulation, Execution

30. Case study (cont.) • In real applications, some processes enable paradigm 12 better than others. Because of the nature of the MVR process, (driver merge, specific business logic for service invocations,...) the business view and the resulting BPEL diverged significantly.

31. Case study (cont.) • Step3: MVR Record merging • The first activity initiates a business process instance when the Process Server receives a new MVR record. As part of the receive in the processMotorVehicleReport operation, developer establish the correlation set necessary to direct other MVR records with the same policy number to this new process instance. • The BPEL continues with a while-loop which receives the other messages correlated to this process instance or times out once the batch file processing is complete. Once all records have been received they are processed.

32. Case study (cont.) BPEL Implementation of the MVR record merge

33. Case study (cont.) • Step 4: Microsoft / IBM interoperability • At present, WebSphere Process Server can only interoperate with WCF's basicHttpBinding. The most advanced features of WCF, such as the use of WS-Policy or SOAP 1.2 cannot be leveraged. Developers inquired this with IBM and Microsoft and solved this issue. • Developers also encountered problems relative to the way each product handles namespaces. Developers had to tweak the WCF generated namespaces to make the resulting WSDL consumable by Process Server.

34. Case study (cont.) • Step5: Security Interoperability • Web Services Security is based on the concept of message based security: the SOAP envelope of the message is sent in clear, but the SOAP body is transmitted in an encrypted form. • On the WCF side, Message based security can be accomplished in a number of ways; some of them are:

35. Conclusion • Web service • Service-Oriented Architecture • Service-Oriented Business • Case study

36. Thank you Questions?