SERVICE ORIENTED ARCHITECTURE

Transcription

1 Oriented Architecture SERVICE ORIENTED ARCHITECTURE Developing applications based on common services Authentication / Authorization services Shared customer profile service Digital signature services Report services Interoperable on multiple platforms Java /.Net / Legacy Principle of SOA Layers of SOA Loosely Coupled All are services Distributed on multiple servers Open Standards Proven technology Simplify integration Composite s of service Composite Simple App App Base Infrastructure / Platform 1

2 Common SOA Architecture Why SOA? Portal Process Process <xml> Text </xml> Improve agility by reusing Smaller efforts Shorter development time Allow quick response to business changes Ability to adjust without re-coding the whole system Reduce implementation risk Use iterative process Focus on core processes with high ROI SOA Example: Ticket Reservation Case Study: Dealersphere Internet Authenticate Ticket/Booking info National Auto Dealer Association. Car dealers to communicate with other companies via ebxml and SOAP. Features? Handling credit checks. Getting the exact color and car options. Locating the car at another dealer. Front-Office Payment 2

3 Case Study: Singapore egovernment Common SOA Architecture Public e Infrastructure (PSi) ida Singapore. Integrate over 600 online services from several government agencies. Example services Request for a new driver s license. provided by Land Transport Authority of Singapore. However, citizen information is needed from Citizen Department. And payment must be made online. Other services also need these information. Portal Process Process <xml> Text </xml> Pains in SOA RPC Middleware Base on 10+ standards, support by 100+ vendors, moving into 1,000+ direction Standards are constantly changed Tools from different vendors are not quite compatible Tools even from same vendor but different version may not be compatible Implementing SOA system requires lots of planning and designing Call ABC(X, Y, Z) Client Stub Interface Definition Language (IDL) Skeleton ABC(X, Y, Z) Server ABC(int X, string Y, pointer Z) return float 3

4 What is a Web? A Basic Web A Web is any service that: Is available over the Internet or private (intranet) networks Uses a standardized XML messaging system Is not tied to any one operating system or programming language REST: Lightweight Web s REpresentational State Transfer Lightweight and simple Only XML on HTTP Utilize HTTP methods instead of using envelope style URI as method identifation Emulate CRUD operations HTTP CRUD POST GET PUT DELETE Create, Update, Delete Read Create, Overwrite/Replace Delete REST Concept Operation getuser() adduser() removeuser() updateuser() getlocation() addlocation() removelocation() updatelocation() listusers() listlocations() findlocation() finduser() REST URL for each user - where {user} is either the user name or the user id) on} (one for each location - - where {location} is either the location name or the location id) 4

5 REST Examples Web s Standards Blogsphere RSS / Atom Flickr Amazon Web s Basic Standards Web s Defined a web service should be self describing Describe public interfaces of the service For SOAP, in standard XML format (WSDL) a web service should be discoverable Must have a simple way to advertise or publish your service so others can find or discover it 5

6 Web s Architecture SOAP Structure Publish Find Bind. UDDI Registry WSDL Find Publish Requestor Bind Provider SOAP Sample SOAP Request Sample SOAP Response <?xml version= 1.0 encoding= UTF-8?> <SOAP-ENV:Envelope SOAP- ENV:encodingStyle= xmlns:xsd= xmlns:soap-env= xmlns:xsi= <SOAP-ENV:Body> <CalculatorAdd> <arg0 xsi:type= xsd:int >30</arg0> <arg1 xsi:type= xsd:int >40</arg1> </CalculatorAdd> </SOAP-ENV:Body> </SOAP-ENV:Envelope> <?xml version= 1.0 encoding= UTF-8?> <SOAP-ENV:Envelope SOAP-ENV:encodingStyle= xmlns:xsd= xmlns:soap-env= xmlns:xsi= <SOAP-ENV:Body> <CalculatorAddResponse> <result xsi:type= xsd:int >70</doCheckResult> </CalculatorAddResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> 6

7 Web s QoS Standards Web s Enterprise Standards Towards Composite Applications Example of Composite Application Example: Modern Web Application Telco Activation s SMS Activation Manager GPRS Activation Manager China Roaming Activation Manager Automatic Payment Approval Not Available Exception Process Flow Orchestration Billing s Payment s Credit Card Payment s 7

8 What Is BPEL? BPEL is: A markup language for composing a set of discrete services into an end-to-end process flow A mechanism for asynchronous interactions, parallel processing, and exception management BPEL Tool SalesDB Router Start End Duplicate number! Billing <process> <partnerlinks> <partnerlink name="servicename"... /> </partnerlinks> <variables> <variable name="var-name" messagetype="type"/> </variables> <sequence name="main"> <receive.../> <assign.../> </process> BPEL source Benefits of BPEL BPEL: Integrates a set of services to implement business processes Defines a sequence of activities, called a process flow, using a standard XML application language Supports definition and invocation of synchronous and asynchronous services Enables structured message data to be exchanged with invoked services May be constructed visually with designer tools, such as JDeveloper BPEL Designer Provides its process flow as a service Business Process Execution Language Portal Web Browser Management? BPEL.NET, Web User Workflow Database ERP Adapters 8

9 Loan Flow Example CLIENT LOAN FLOW BPEL PROCESS receive Oracle ebusiness Suite getssn CLIENT SCOPE getrating FLOW United Load American Loan invoke invoke receive receive select 5-15 min Web s Interface: XML, SOAP, WSDL, WSIF Credit Rating.NET Exception Workflow Java Web review end Loan Providers 9