List of Figures

Preface

Figure P.1: UML Class Diagram
Figure P.2: UML Sequence Diagram
Figure P.3: UML Use Case Diagram

Chapter 1: Web Services Overview

Figure 1.1: The transformation in computer system deployment.
Figure 1.2: The monolithic approach to software development.
Figure 1.3: Client-server computing separated data management from application logic.
Figure 1.4: N-tier development created a business-logic layer that accessed data.
Figure 1.5: Services use open protocols that can be accessed through the Internet.
Figure 1.6: Structured design involves decomposing larger processes into smaller ones.
Figure 1.7: Object-oriented development encapsulates both data and behavior into classes and objects.
Figure 1.8: Component-based development involves a small group of objects with a contractually specified interface, working together to provide an application function.
Figure 1.9: In service-based development, services are usually components wrapped in a service layer.
Figure 1.10: Web services technology stack.
Figure 1.11: The enterprise application integration hub-and-spoke topology.
Figure 1.12: The enterprise application integration Web services topology.
Figure 1.13: A simple Web service scenario.
Figure 1.14: A composite Web service scenario.
Figure 1.15: A middleware Web service scenario.
Figure 1.16: A service bus.

Chapter 2: Service-Oriented Architecture

Figure 2.1: Software architecture describes a system's components and connectors.
Figure 2.2: Web services are one set of technologies for implementing service-oriented architecture.
Figure 2.3: The "find-bind-execute" paradigm.
Figure 2.4: A service proxy.
Figure 2.5: A conceptual service model.
Figure 2.6: Fine-grained distributed objects.
Figure 2.7: Coarse-grained services.
Figure 2.8: Degrees of granularity.
Figure 2.9: Multi-grained services.
Figure 2.10: A method that returns only account-holder information.
Figure 2.11: A method that returns both the account-holder's information and address.
Figure 2.12: A method that returns either the account-holder's information or address.
Figure 2.13: A method that returns just the attributes requested.

Chapter 3: Component-Based Service Development

Figure 3.1: Development lifecycle of a component-based service.
Figure 3.2: The requirements analyst creates a set of artifacts that describes the application.
Figure 3.3: Degrees of modifiability.
Figure 3.4: One way to improve integrability is to adapt the service for use over different protocols.
Figure 3.5: Architecture refers to core assets grouped into three viewpoints.
Figure 3.6: The conceptual architecture for a typical component-based service consists of six layers.
Figure 3.7: A typical session façade and business logic layer.
Figure 3.8: Example functional and technical services.
Figure 3.9: The IEEE Maintenance Process Activities diagram.

Chapter 4: SOAP

Figure 4.1: SOAP and the enterprise
Figure 4.2: The Web services communication stack
Figure 4.3: SOAP nodes
Figure 4.4: SOAP message structure
Figure 4.5: Mapping of Listing 4.1a to elements of the SOAP message structure
Figure 4.6: SOAP nodes and intermediaries
Figure 4.7: The SAAJ object model

Chapter 5: WSDL

Figure 5.1: WSDL document- a conceptual representation
Figure 5.2: Dynamic interaction of a service and its consumer
Figure 5.3: A logical class diagram of the key WSDL elements
Figure 5.4: BillPayservice service WSDL mapped to the WSDL conceptual model
Figure 5.5: The definitions element
Figure 5.6: The types element
Figure 5.7: The message element
Figure 5.8: The schema for the operations element
Figure 5.9: A one-way operation
Figure 5.10: A request-response operation
Figure 5.11: A solicit-response operation
Figure 5.12: A notification operation
Figure 5.13: The portType element
Figure 5.14: The binding element
Figure 5.15: The SOAP header
Figure 5.16: The multipartRelated element
Figure 5.17: (a) RPC and (b) document styles
Figure 5.18: The service element
Figure 5.19: Vendor tool tasks
Figure 5.20: Tasks performed by Hvendor tools for WSDL
Figure 5.21: xrpcc can read an XML configuration file to generate client-side code.

Chapter 6: UDDI

Figure 6.1: UDDI interaction
Figure 6.2: Creating a business entity
Figure 6.3: Details for the business entity
Figure 6.4: Creating a business service
Figure 6.5: Creating a binding template
Figure 6.6: Creating a tModel
Figure 6.7: UDDI core data structures
Figure 6.8: businessEntity
Figure 6.9: businessService
Figure 6.10: bindingTemplate
Figure 6.11: tModel
Figure 6.12: Binding template activity
Figure 6.13: UDDI interoperability

Chapter 7: ebXML

Figure 7.1: ebXML frameworks (adapted from the ebXML Business Process Specification Schema)
Figure 7.2: Design-time and runtime components
Figure 7.3: Graphic process modeling and the Business Process Specification Schema
Figure 7.4: Use cases map to collaborations grouped as discrete transactions (adapted from the ebXML Business Process Specification Schema)
Figure 7.5: The XML elements in a Collaboration-Protocol Profile
Figure 7.6: A Collaboration-Protocol Agreement is agreed upon based on the Collaboration-Protocol Profile documents
Figure 7.7: The XML elements in a Collaboration-Protocol Agreement
Figure 7.8: Design-time and runtime components in detail
Figure 7.9: Relationships in the Registry Information Model
Figure 7.10: ebXML Registry Information Model (source- ebXML RIM specifications)
Figure 7.11: Registry interfaces
Figure 7.12: Registry bindings
Figure 7.13: The ebXML message (source- ebXML Message Service Specification)
Figure 7.14: ebXML messaging system modules
Figure 7.15: ebXML messaging
Figure 7.16: A business collaboration scenario

Chapter 8: Java Web Service Developer Pack

Figure 8.1: Java WSDP components
Figure 8.2: The Tomcat Web server administration console
Figure 8.3: Sample tasks for creating a JAX-RPC server
Figure 8.4: The wsdeploy tool
Figure 8.5: Sample tasks for creating a JAX-RPC client
Figure 8.6: The registry browser

Chapter 9: JAXP

Figure 9.1a: Logical JAXP architecture
Figure 9.1b: JAXP architecture
Figure 9.2: Schema showing tree structure of DOM
Figure 9.3: The org.w3c.dom package
Figure 9.4: XML validation with JAXP 1.2
Figure 9.5: XSLT transformation process
Figure 9.6: XML transformed into HTML
Figure 9.7a: Transcoding XML into different formats
Figure 9.7b: Logical tiering
Figure 9.8: JAXP and XSLT
Figure 9.9: XSLTc architecture
Figure 9.10: Class diagram for JDOM. Note the lack of relationships between classes.

Chapter 10: JAX-RPC

Figure 10.1: The JAX-RPC model
Figure 10.2: JAX-RPC client-server interaction
Figure 10.3: (a) RPC style. (b) Document style.
Figure 10.4: Service deployment
Figure 10.5: xrpcc artifacts
Figure 10.6: WSDL elements and dynamic interaction of a service and its consumer.
Figure 10.7: Handler architecture
Figure 10.8: Fault handling in handlers
Figure 10.9: Handler example
Figure 10.10: Using XML attachments with JAX-RPC for asynchronous invocation
Figure 10.11: Serializers and deserializers
Figure 10.12: The type mapping system
Figure 10.13: EJB endpoint for JAX-RPC
Figure 10.14: EJB invoking other Web services

Chapter 11: JAXM

Figure 11.1: MOM
Figure 11.2: Centralized MOM topology
Figure 11.3: Decentralized MOM topology
Figure 11.4: Hybrid MOM topology
Figure 11.5: Synchronous Web services
Figure 11.6: Asynchronous Web services
Figure 11.7: Conceptual model for JMS
Figure 11.8a: Point-to-point messaging
Figure 11.8b: Publish-subscribe messaging
Figure 11.9: The JMS API
Figure 11.10: JMS messaging
Figure 11.11: Sending messages with point-to-point messaging
Figure 11.12: Conceptual JavaMail model
Figure 11.13: The JavaMail API
Figure 11.14: Sending mail using JavaMail
Figure 11.15: Message structure for (a) simple messages and (b) multipart messages
Figure 11.16: Retrieving mail using JavaMail
Figure 11.17: Asynchronous B2B messaging using JavaMail
Figure 11.18: Conceptual model for JAXM
Figure 11.19: Architectural stack for JAXM
Figure 11.20: SOAP message structure with a profile
Figure 11.21: Point-to-point messaging from a client without a provider
Figure 11.22: Synchronous messaging with response
Figure 11.23: Synchronous messaging with acknowledgment
Figure 11.24: Provider roles in asynchronous messaging
Figure 11.25: Asynchronous messaging with response
Figure 11.26: Asynchronous messaging with acknowledgment
Figure 11.27: Asynchronous one way messaging
Figure 11.28: SAAJ model in the javax.xml.soap package
Figure 11.29: Synchronous messaging
Figure 11.30: Implementing a synchronous service
Figure 11.31: Asynchronous messaging
Figure 11.32: Sequence diagram of provider-to-provider communication
Figure 11.33: Sequence diagram of provider-to-provider communication
Figure 11.34: JAXM Provider Administration in the reference implementation
Figure 11.35: Realizing an asynchronous JAXM service
Figure 11.36: JAXM, JAX-RPC, and relationship to SAAJ
Figure 11.37: JAXM interoperability scenarios
Figure 11.38: JMS providers using SOAP

Chapter 12: JAXR

Figure 12.1: Registry usage
Figure 12.2: JAXR Architecture
Figure 12.3: The core JAXR information model
Figure 12.4: Inheritance relationships in the information model
Figure 12.5: Classification of registry objects
Figure 12.6: The basic subdivisions of matter
Figure 12.7: NAICS code assignment
Figure 12.8: Classification with an internal taxonomy
Figure 12.9: An example of an external taxonomy
Figure 12.10: Classification with an internal taxonomy
Figure 12.11: An extramural association between two organizations
Figure 12.12: JAXR API
Figure 12.13: The LifeCycleManager and the BusinessLifeCycleManager
Figure 12.14: The QueryManager and the BusinessQueryManager
Figure 12.15: The DeclarativeQueryManager for level 1 providers
Figure 12.16: Flute Bank as registered in the IBM UDDI registry
Figure 12.17: WSDL representation in UDDI
Figure 12.18: WSDL information published in UDDI
Figure 12.19: ebXML registry browser

Chapter 13: JAXB

Figure 13.1: JAXB architecture
Figure 13.2: The binding compiler
Figure 13.3: Declaration scope

Chapter 14: Transaction Management

Figure 14.1: The two-phase commit protocol
Figure 14.2: Nested transactions
Figure 14.3: JTS transaction manager components
Figure 14.4: Atomicity relaxed, travel agency example
Figure 14.5: Application and BTP elements overview
Figure 14.6: Application and BTP elements in an atom/cohesion
Figure 14.7: BTP and application elements
Figure 14.8: BTP actors and messages overview
Figure 14.9: A simple atom example illustrating the BTP two-phase protocol
Figure 14.10: Cohesion completion
Figure 14.11: BTP element tree
Figure 14.12: Roles played by superiors and inferiors
Figure 14.13: BTP SOAP message shown pictorially
Figure 14.14: Relationship between WS-Coordination and WS-Transaction

Chapter 15: Security

Figure 15.1: Secure Sockets Layer
Figure 15.2: SAML
Figure 15.3: SAML assertion
Figure 15.4: SAML assertion response
Figure 15.5: WS-I specifications
Figure 15.6: Married couple interaction
Figure 15.7: JAAS pluggable authentication
Figure 15.8: Bank wire transfer process
Figure 15.9: Mobile access through gateways
Figure 15.10: Security federations
Figure 15.11: Delegation of trust
Figure 15.12: Federated network identity

Chapter 16: Practical Considerations

Figure 16.1: Accounting service
Figure 16.2: XMLPay flow
Figure 16.3: Downtime cost as a function of impact
Figure 16.4: Redundant infrastructure for high availability
Figure 16.5: Typical J2EE architecture
Figure 16.6: Cluster architecture
Figure 16.7: Web services using grid computing
Figure 16.8: Web services summary

Chapter 17: Future Standards

Figure 17.1: The service description stack
Figure 17.2: BPEL process and partner services
Figure 17.3: Core elements of a BPEL process document
Figure 17.4: Basic structure of a BPEL document
Figure 17.5: WS-routing and SOAP intermediaries

Appendix A: XML Schema

Figure A.1: Role of XML Schema and schema validators
Figure A.2: Simple DTD for the employeeList document
Figure A.3: XML Schema for the employeeList document
Figure A.4
Figure A.5
Figure A.6: Extending XML schema using the appinfo element

Appendix B: JSTL

Figure B.1: The outout from the JSTL example