1. Identifying the Building Blocks of Web Services Web Services can convert your application into a Web-application, which can publish its function or message to the rest of the world.

2. Describe Service Oriented Architecture SOA provides a set of principles or governing concepts used during phases of systems development and integration. SOA implementations rely on a mesh of software services. Services comprise unassociated, loosely coupled units of functionality that have no calls to each other embedded in them. The technology of Web services is the most likely connection technology of service-oriented architectures. Web services essentially use XML to create a robust connection.

3. SOA: A conceptual model

4. SOA: guiding principles reuse, granularity, modularity, composability, componentization and interoperability. standards-compliance (both common and industry- specific). services identification and categorization, provisioning and delivery, and monitoring and tracking.

5. SOA: architectural principles Service encapsulation Service loose coupling Service contract Service abstraction Service reusability Service composability Service autonomy Service optimization Service discoverability Service relevance

6. Architectural template for a SOA

7. Layer 1: Operational systems layer This consists of existing custom built applications, otherwise called legacy systems, including existing CRM and ERP packaged applications, and older object- oriented system implementations, as well as business intelligence applications. The composite layered architecture of an SOA can leverage existing systems and integrate them using service-oriented integration techniques.

8. Layer 2: Enterprise components layer This is the layer of enterprise components that are responsible for realizing functionality and maintaining the QoS of the exposed services. These special components are a managed, governed set of enterprise assets that are funded at the enterprise or the business unit level. As enterprise-scale assets, they are responsible for ensuring conformance to SLAs through the application of architectural best practices. This layer typically uses container-based technologies such as application servers to implement the components, workload management, high-availability, and load balancing.

9. Layer 3: Services layer The services the business chooses to fund and expose reside in this layer. They can be discovered or be statically bound and then invoked, or possibly, choreographed into a composite service. This service exposure layer also provides for the mechanism to take enterprise scale components, business unit specific components, and in some cases, project-specific components, and externalizes a subset of their interfaces in the form of service descriptions. Thus, the enterprise components provide service realization at runtime using the functionality provided by their interfaces. The interfaces get exported out as service descriptions in this layer, where they are exposed for use. They can exist in isolation or as a composite service.

10. Level 4: Business process composition or choreography layer Business process composition or choreography layer. Compositions and choreographies of services exposed in Layer 3 are defined in this layer. Services are bundled into a flow through orchestration or choreography, and thus act together as a single application. These applications support specific use cases and business processes.

11. Layer 5: Access or presentation layer Although this layer is usually out of scope for discussions around a SOA, it is gradually becoming more relevant. I depict it here because there is an increasing convergence of standards, such as Web Services for Remote Portlets Version 2.0 and other technologies, that seek to leverage Web services at the application interface or presentation level. You can think of it as a future layer that you need to take into account for future solutions. It is also important to note that SOA decouples the user interface from the components, and that you ultimately need to provide an end-to-end solution from an access channel to a service or composition of services.

12. Level 6: Integration (ESB) This layer enables the integration of services through the introduction of a reliable set of capabilities, such as intelligent routing, protocol mediation, and other transformation mechanisms, often described as the ESB (Enterprise service bus). Web Services Description Language specifies a binding, which implies a location where the service is provided. On the other hand, an ESB provides a location independent mechanism for integration.

13. Level 7: QoS This layer provides the capabilities required to monitor, manage, and maintain QoS such as security, performance, and availability. This is a background process through sense-and-respond mechanisms and tools that monitor the health of SOA applications, including the all important standards implementations of WS-Management and other relevant protocols and standards that implement quality of service for a SOA.

14. Java Business Integration It is a specification developed for an approach to implementing a service-oriented architecture (SOA). JBI is built on a Web Services model and provides a pluggable architecture for a container that hosts service producer and consumer components. Apache ServiceMix is one open-source software JBI based ESB implementations available.

15. Define a web service A software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically Web Services Description Language WSDL). 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.

16. Web service: Styles of use RPC Uses XML messages that follow the SOAP standard. In such systems, there is often a machine-readable description of the operations offered by the service written in the WSDL. SOA Used to implemented an architecture according to SOA concepts. REST RESTful Web services have been regaining popularity, particularly with Internet companies. By using the PUT, GET, POST and DELETE HTTP methods, are often better integrated with HTTP and web browsers than SOAP-based services. They do not require XML messages or WSDL service-API definitions.

17. Identify the characteristics of a web service Web services are application components Web services communicate using open protocols Web services are self-contained and self-describing Web services can be discovered using UDDI (Universal Description, Discovery and Integration) Web services can be used by other applications XML is the basis for Web services (???)

18. Web Services Stack

19. Explore the need for web services Connect existing software Web Services take Web-applications to the Next Level Reusable application-components

20. Discuss web services as a realization of SOA Web services can implement a service-oriented architecture. Web services make functional building- blocks accessible over standard Internet protocols independent of platforms and programming languages. These services can represent either new applications or just wrappers around existing legacy systems to make them network-enabled.

21. Explain the advantages of web services- based SOA approach Help businesses respond more quickly and cost-effectively to changing market-conditions. Promotes reuse at the macro (service) level rather than micro (classes) level. Simplify interconnection to – and usage of – existing IT (legacy) assets. Systems achieve the goals of increased interoperability (information exchange, reusability, and composability), increased federation (uniting resources and applications while maintaining their individual autonomy and self-governance), and increased business and technology domain alignment. Promotes the goal of separating users from the service implementations. Services can therefore be run on various distributed platforms and be accessed across networks. This can also maximize reuse of services.

22. Web service initiatives, specifications, and Application Programming Interfaces XML Specifications –XML Messaging Specifications –SOAP Metadata Exchange Specifications –WSDL 2.0 Web service frameworks –Apache Axis2 Java Business Integration (JBI) (SOA frameworks) –Apache ServiceMix

23. Examine the Java technologies for web services development The Java Architecture for XML Web Services (JAX-WS) The Java Architecture for XML Binding (JAXB) The StAX APIs and the Sun Java Streaming XML Parser implementation SOAP with Attachments API for Java (SAAJ) The Java Architecture for XML Registries (JAXR)

24. Web Services Interoperability Organization (WS-I) Basic Profile It is an industry consortium chartered to promote interoperability amongst the stack of web services specifications. WS-I does not define standards for web services; rather, it creates guidelines and tests for interoperability. The organization's deliverables include profiles, sample applications that demonstrate the profiles' use, and test tools to help determine profile conformance.

25. WS-I Basic Profile It is a specification from the WS-I, provides interoperability guidance for core Web Services specifications such as SOAP, WSDL, and UDDI. The profile uses WSDL to enable the description of services as sets of endpoints operating on messages. To understand the importance of WSI-BP, note that it defines a much narrower set of valid services than the full WSDL schema. Many common platforms support WSI-BP but do not support services outside of it. Compare the WSDL 1.1 specification to the subset permitted in WSI-BP.