UnitAssembleanddeploy.pptVIP

Getting Started with SOA Unit 8. Assemble and deploy Unit objectives After completing this unit, you should be able to: Describe the need for an SOA programming model Define Service Component Architecture (SCA) Describe the components of SCA: Service module, mediation modules, service component and mediation flow component Describe the support for QoS within SCA Describe the WebSphere Integration Developer platform architecture Explain the role of WebSphere Integration Developer in enabling development and assembly of services based on SCA Illustrate the capabilities of IBM WebSphere deployment platforms that support SCA Why the need for an SOA programming model? SOA: A service is an abstraction that encapsulates a discrete unit of functionality, referred to as a service component Problem: How do you build an application using these components? Solution: Assemble services into a composite application using a standard model SOA: Developers should be free to use a range of implementation technologies for their services Problem: How do you achieve this? Solution: Use a model which clearly separates the means to invoke a service from the mechanism for implementing it SOA: Services need a standard data representation format for communication and ease of integration Problem: How do you achieve this without locking into a particular technology or language? Solution: Use a technology-agnostic, standardized data model Benefits of an SOA programming model Separation of concerns Separate business logic from implementation technology SOA developers can focus on solving a business problem rather than thinking about the language they have to code in Integration is simplified - implementation details are hidden A single abstraction model for invoking service components Consistent approach for exposing service interfaces independent of the underlying implementation technology For example, define an interface in WSDL and implement in BPEL A standardized client programming model Invo