List of Figures
- Screenshot P.1: UML Class Diagram
- Screenshot P.2: UML Sequence Diagram
- Screenshot P.3: UML Use Case Diagram
Web Services Overview
- Screenshot: The transformation in computer system deployment.
- Screenshot: The monolithic approach to software development.
- Screenshot: Client-server computing separated data management from app logic.
- Screenshot: N-tier development created a business-logic layer that accessed data.
- Screenshot: Services use open protocols that can be accessed through the Internet.
- Screenshot: Structured design involves decomposing larger processes into smaller ones.
- Screenshot: Object-oriented development encapsulates both data and behavior into classes and objects.
- Screenshot: Component-based development involves a small group of objects with a contractually specified interface, working together to provide an app function.
- Screenshot: In service-based development, services are usually components wrapped in a service layer.
- Screenshot: Web services technology stack.
- Screenshot: The enterprise app integration hub-and-spoke topology.
- Screenshot: The enterprise app integration Web services topology.
- Screenshot: A simple Web service scenario.
- Screenshot: A composite Web service scenario.
- Screenshot: A middleware Web service scenario.
- Screenshot: A service bus.
Service-Oriented Architecture
- Screenshot: Software architecture describes a system's components and connectors.
- Screenshot: Web services are one set of technologies for implementing service-oriented architecture.
- Screenshot: The "find-bind-execute" paradigm.
- Screenshot: A service proxy.
- Screenshot: A conceptual service model.
- Screenshot: Fine-grained distributed objects.
- Screenshot: Coarse-grained services.
- Screenshot: Degrees of granularity.
- Screenshot: Multi-grained services.
- Screenshot: A method that returns only account-holder information.
- Screenshot: A method that returns both the account-holder's information and address.
- Screenshot: A method that returns either the account-holder's information or address.
- Screenshot: A method that returns just the attributes requested.
Component-Based Service Development
- Screenshot: Development lifecycle of a component-based service.
- Screenshot: The requirements analyst creates a set of artifacts that describes the app.
- Screenshot: Degrees of modifiability.
- Screenshot: One way to improve integrability is to adapt the service for use over different protocols.
- Screenshot: Architecture refers to core assets grouped into three viewpoints.
- Screenshot: The conceptual architecture for a typical component-based service consists of six layers.
- Screenshot: A typical session façade and business logic layer.
- Screenshot: Example functional and technical services.
- Screenshot: The IEEE Maintenance Process Activities diagram.
SOAP
- Screenshot: SOAP and the enterprise
- Screenshot: The Web services communication stack
- Screenshot: SOAP nodes
- Screenshot: SOAP message structure
- Screenshot: Mapping of Listing 4.1a to elements of the SOAP message structure
- Screenshot: SOAP nodes and intermediaries
- Screenshot: The SAAJ object model
WSDL
- Screenshot: WSDL document— a conceptual representation
- Screenshot: Dynamic interaction of a service and its consumer
- Screenshot: A logical class diagram of the key WSDL elements
- Screenshot: BillPayservice service WSDL mapped to the WSDL conceptual model
- Screenshot: The definitions element
- Screenshot: The types element
- Screenshot: The message element
- Screenshot: The schema for the operations element
- Screenshot: A one-way operation
- Screenshot: A request-response operation
- Screenshot: A solicit-response operation
- Screenshot: A notification operation
- Screenshot: The portType element
- Screenshot: The binding element
- Screenshot: The SOAP header
- Screenshot: The multipartRelated element
- Screenshot: (a) RPC and (b) document styles
- Screenshot: The service element
- Screenshot: Vendor tool tasks
- Screenshot: Tasks performed by Hvendor tools for WSDL
- Screenshot: xrpcc can read an XML configuration file to generate client-side code.
UDDI
- Screenshot: UDDI interaction
- Screenshot: Creating a business entity
- Screenshot: Details for the business entity
- Screenshot: Creating a business service
- Screenshot: Creating a binding template
- Screenshot: Creating a tModel
- Screenshot: UDDI core data structures
- Screenshot: businessEntity
- Screenshot: businessService
- Screenshot: bindingTemplate
- Screenshot: tModel
- Screenshot: Binding template activity
- Screenshot: UDDI interoperability
ebXML
- Screenshot: ebXML frameworks (adapted from the ebXML Business Process Specification Schema)
- Screenshot: Design-time and runtime components
- Screenshot: Graphic process modeling and the Business Process Specification Schema
- Screenshot: Use cases map to collaborations grouped as discrete transactions (adapted from the ebXML Business Process Specification Schema)
- Screenshot: The XML elements in a Collaboration-Protocol Profile
- Screenshot: A Collaboration-Protocol Agreement is agreed upon based on the Collaboration-Protocol Profile documents
- Screenshot: The XML elements in a Collaboration-Protocol Agreement
- Screenshot: Design-time and runtime components in detail
- Screenshot: Relationships in the Registry Information Model
- Screenshot: ebXML Registry Information Model (source— ebXML RIM specifications)
- Screenshot: Registry interfaces
- Screenshot: Registry bindings
- Screenshot: The ebXML message (source— ebXML Message Service Specification)
- Screenshot: ebXML messaging system modules
- Screenshot: ebXML messaging
- Screenshot: A business collaboration scenario
Java Web Service Developer Pack
- Screenshot: Java WSDP components
- Screenshot: The Tomcat Web server administration console
- Screenshot: Sample tasks for creating a JAX-RPC server
- Screenshot: The wsdeploy tool
- Screenshot: Sample tasks for creating a JAX-RPC client
- Screenshot: The registry browser
JAXP
- Screenshota: Logical JAXP architecture
- Screenshotb: JAXP architecture
- Screenshot: Schema showing tree structure of DOM
- Screenshot: The org.w3c.dom package
- Screenshot: XML validation with JAXP 1.2
- Screenshot: XSLT transformation process
- Screenshot: XML transformed into HTML
- Screenshota: Transcoding XML into different formats
- Screenshotb: Logical tiering
- Screenshot: JAXP and XSLT
- Screenshot: XSLTc architecture
- Screenshot: Class diagram for JDOM. Note the lack of relationships between classes.
JAX-RPC
- Screenshot: The JAX-RPC model
- Screenshot: JAX-RPC client-server interaction
- Screenshot: (a) RPC style. (b) Document style.
- Screenshot: Service deployment
- Screenshot: xrpcc artifacts
- Screenshot: WSDL elements and dynamic interaction of a service and its consumer.
- Screenshot: Handler architecture
- Screenshot: Fault handling in handlers
- Screenshot: Handler example
- Screenshot: Using XML attachments with JAX-RPC for asynchronous invocation
- Screenshot: Serializers and deserializers
- Screenshot: The type mapping system
- Screenshot: EJB endpoint for JAX-RPC
- Screenshot: EJB invoking other Web services
JAXM
- Screenshot: MOM
- Screenshot: Centralized MOM topology
- Screenshot: Decentralized MOM topology
- Screenshot: Hybrid MOM topology
- Screenshot: Synchronous Web services
- Screenshot: Asynchronous Web services
- Screenshot: Conceptual model for JMS
- Screenshota: Point-to-point messaging
- Screenshotb: Publish-subscribe messaging
- Screenshot: The JMS API
- Screenshot: JMS messaging
- Screenshot: Sending messages with point-to-point messaging
- Screenshot: Conceptual JavaMail model
- Screenshot: The JavaMail API
- Screenshot: Sending mail using JavaMail
- Screenshot: Message structure for (a) simple messages and (b) multipart messages
- Screenshot: Retrieving mail using JavaMail
- Screenshot: Asynchronous B2B messaging using JavaMail
- Screenshot: Conceptual model for JAXM
- Screenshot: Architectural stack for JAXM
- Screenshot: SOAP message structure with a profile
- Screenshot: Point-to-point messaging from a client without a provider
- Screenshot: Synchronous messaging with response
- Screenshot: Synchronous messaging with acknowledgment
- Screenshot: Provider roles in asynchronous messaging
- Screenshot: Asynchronous messaging with response
- Screenshot: Asynchronous messaging with acknowledgment
- Screenshot: Asynchronous one way messaging
- Screenshot: SAAJ model in the javax.xml.soap package
- Screenshot: Synchronous messaging
- Screenshot: Implementing a synchronous service
- Screenshot: Asynchronous messaging
- Screenshot: Sequence diagram of provider-to-provider communication
- Screenshot: Sequence diagram of provider-to-provider communication
- Screenshot: JAXM Provider Administration in the reference implementation
- Screenshot: Realizing an asynchronous JAXM service
- Screenshot: JAXM, JAX-RPC, and relationship to SAAJ
- Screenshot: JAXM interoperability scenarios
- Screenshot: JMS providers using SOAP
JAXR
- Screenshot: Registry usage
- Screenshot: JAXR Architecture
- Screenshot: The core JAXR information model
- Screenshot: Inheritance relationships in the information model
- Screenshot: Classification of registry objects
- Screenshot: The basic subdivisions of matter
- Screenshot: NAICS code assignment
- Screenshot: Classification with an internal taxonomy
- Screenshot: An example of an external taxonomy
- Screenshot: Classification with an internal taxonomy
- Screenshot: An extramural association between two organizations
- Screenshot: JAXR API
- Screenshot: The LifeCycleManager and the BusinessLifeCycleManager
- Screenshot: The QueryManager and the BusinessQueryManager
- Screenshot: The DeclarativeQueryManager for level 1 providers
- Screenshot: Flute Bank as registered in the IBM UDDI registry
- Screenshot: WSDL representation in UDDI
- Screenshot: WSDL information published in UDDI
- Screenshot: ebXML registry browser
JAXB
- Screenshot: JAXB architecture
- Screenshot: The binding compiler
- Screenshot: Declaration scope
Transaction Management
- Screenshot: The two-phase commit protocol
- Screenshot: Nested transactions
- Screenshot: JTS transaction manager components
- Screenshot: Atomicity relaxed, travel agency example
- Screenshot: app and BTP elements overview
- Screenshot: app and BTP elements in an atom/cohesion
- Screenshot: BTP and app elements
- Screenshot: BTP actors and messages overview
- Screenshot: A simple atom example illustrating the BTP two-phase protocol
- Screenshot: Cohesion completion
- Screenshot: BTP element tree
- Screenshot: Roles played by superiors and inferiors
- Screenshot: BTP SOAP message shown pictorially
- Screenshot: Relationship between WS-Coordination and WS-Transaction
Security
- Screenshot: Secure Sockets Layer
- Screenshot: SAML
- Screenshot: SAML assertion
- Screenshot: SAML assertion response
- Screenshot: WS-I specifications
- Screenshot: Married couple interaction
- Screenshot: JAAS pluggable authentication
- Screenshot: Bank wire transfer process
- Screenshot: Mobile access through gateways
- Screenshot: Security federations
- Screenshot: Delegation of trust
- Screenshot: Federated network identity
Practical Considerations
- Screenshot: Accounting service
- Screenshot: XMLPay flow
- Screenshot: Downtime cost as a function of impact
- Screenshot: Redundant infrastructure for high availability
- Screenshot: Typical J2EE architecture
- Screenshot: Cluster architecture
- Screenshot: Web services using grid computing
- Screenshot: Web services summary
Future Standards
- Screenshot: The service description stack
- Screenshot: BPEL process and partner services
- Screenshot: Core elements of a BPEL process document
- Screenshot: Basic structure of a BPEL document
- Screenshot: WS-routing and SOAP intermediaries
- Screenshot A.1: Role of XML Schema and schema validators
- Screenshot A.2: Simple DTD for the employeeList document
- Screenshot A.3: XML Schema for the employeeList document
- Screenshot A.4
- Screenshot A.5
- Screenshot A.6: Extending XML schema using the appinfo element
- Screenshot B.1: The outout from the JSTL example
Comments
