The document provides an overview of Service Oriented Architecture (SOA) concepts including web services frameworks, service descriptions, message exchange patterns, coordination, and atomic transactions. Key points covered include the roles of services, components of web services frameworks, how services relate and communicate using descriptions and messages, and how coordination establishes context management for complex service activities.

1. Service Oriented Architecture [email_address] VA-12/05

3. What is SOA VA-12/05

12. Composition of services VA-12/05 Service Oriented Architecture Select Music for Download Create total bill Prompt user for credit card details Credit Card Approved Process credit card approval Allow Download Validate credit car details Successful Process transaction Valid Card Transaction Successful Transaction Failed Yes Yes No No

24. SOA vs. Client Server Architecture VA-12/05 Service Oriented Architecture SOA Client Server Architecture Presentation layer is detached from services themselves Application logic resides in client software. Client needs to control user experience, back-end resources Highly distributed processing, services themselves may be distributed over many servers Client is responsible for most of the processing, 80/20 rule was used as a rule of thumb Complex security model but provides flexibility For simple scenario, implements a very easy security model Also has high maintenance costs and requires powerful administration tools Very high maintenance costs of maintaining client server applications

25. SOA vs. Distributed Internet Architecture VA-12/05 Service Oriented Architecture SOA Distributed Internet Architecture Standardized interfaces, Self sufficient messages All the logic exists in server side. Some very insignificant logic may exist in client. Proprietary interfaces in place Message based communication, promotes creation of autonomous services Can support stateful and stateless components, data exchange is primarily synchronous Messages contain header blocks where security logic can be stored Exclusive connection maintains context. In non-exclusive connections, user credentials have to be sent across each request Higher administration costs Simple to maintain, HTTP server needs to be built for scalability

26. Web Services Framework VA-12/05

46. WSDL Example 1/3 VA-12/05 Service Oriented Architecture

47. WSDL Example 2/3 VA-12/05 Service Oriented Architecture

48. WSDL Example 3/3 VA-12/05 Service Oriented Architecture

49. SOAP Example VA-12/05 Service Oriented Architecture

54. UDDI record example VA-12/05 Service Oriented Architecture

55. Message Exchange Patterns VA-12/05

63. Coordination VA-12/05

79. WS-Coordination example VA-12/05 Service Oriented Architecture

80. WS-Coordination example VA-12/05 Service Oriented Architecture

81. Orchestration VA-12/05

86. WS-BPEL Example VA-12/05 Service Oriented Architecture

87. WS-BPEL Example VA-12/05 Service Oriented Architecture

88. WS-BPEL Example VA-12/05 Service Oriented Architecture

104. Choreography VA-12/05

115. WS-CDL Example VA-12/05 Service Oriented Architecture

116. WS-CDL Example VA-12/05 Service Oriented Architecture

117. WS-CDL Example VA-12/05 Service Oriented Architecture

118. WS-CDL Example VA-12/05 Service Oriented Architecture

119. WS-CDL Example VA-12/05 Service Oriented Architecture

120. WS-CDL Example VA-12/05 Service Oriented Architecture

121. WS-CDL Example VA-12/05 Service Oriented Architecture

122. Addressing VA-12/05

126. Reliable Messaging VA-12/05

135. Policy VA-12/05

143. WS-Policy Example VA-12/05 Service Oriented Architecture

144. Metadata Exchange VA-12/05

151. WS-MetadataExchange examples VA-12/05 Service Oriented Architecture

152. Security VA-12/05

160. WS-Security Example VA-12/05 Service Oriented Architecture

161. SAML single sign-on block Example VA-12/05 Service Oriented Architecture

162. SAML sign-on block Example VA-12/05 Service Oriented Architecture

163. Notification & Eventing VA-12/05

169. Notification Message Example VA-12/05 Service Oriented Architecture

170. Subscription Request Example VA-12/05 Service Oriented Architecture

171. Subscription Response Example VA-12/05 Service Oriented Architecture

172. WS-I Profiles VA-12/05

179. Service Design Guidelines VA-12/05

183. SOA platforms VA-12/05

184. J2EE Platform VA-12/05 Service Oriented Architecture Different Operating Systems Java Runtime J2EE class library JAX-RPC Runtime Service oriented solution Web Container EJB Container Servlets EJB

186. .NET Platform VA-12/05 Service Oriented Architecture Windows Operating Systems Common Language Runtime .NET class library Assemblies Service oriented solution ASP.NET Web Services Enhancements(WSE)

188. [email_address] VA-12/05