Transcript 0131858580_c06

Copyright © Pearson Education, Inc.
Figure 6.1: Specifications and concepts
covered in this chapter.
Copyright © Pearson Education, Inc.
Figure 6.2: Not all message exchanges require both requests and
responses.
Copyright © Pearson Education, Inc.
Figure 6.3: The request-response MEP.
Copyright © Pearson Education, Inc.
Figure 6.4: A sample request-response exchange between the TLS
Accounts Payable and Vendor Profile Services.
Copyright © Pearson Education, Inc.
Figure 6.5: The fire-and-forget MEP.
Copyright © Pearson Education, Inc.
Figure 6.6: The TLS Accounts Payable Service sending off a one-way
notification message.
Copyright © Pearson Education, Inc.
Figure 6.7: The publish-and-subscribe messaging model is a
composite of two primitive MEPs.
Copyright © Pearson Education, Inc.
Figure 6.8: The TLS Notification Service notifying
subscribers about a problem condition via a notification
broadcast.
Copyright © Pearson Education, Inc.
Figure 6.9: The four basic patterns supported by WSDL 1.1.
Copyright © Pearson Education, Inc.
Figure 6.10: In an activity, multiple Web services collaborate to do a
specific piece of work.
Copyright © Pearson Education, Inc.
Figure 6.11: A primitive service activity consisting of a simple MEP.
Copyright © Pearson Education, Inc.
Figure 6.12: A complex activity involving four services.
Copyright © Pearson Education, Inc.
Figure 6.13: A sample complex activity spanning RailCo and TLS
boundaries.
Copyright © Pearson Education, Inc.
Figure 6.14: Coordination provides services
that introduce controlled structure into
activities.
Copyright © Pearson Education, Inc.
Figure 6.15: The coordinator service composition.
Copyright © Pearson Education, Inc.
Figure 6.16: The WS-Coordination
registration process.
Copyright © Pearson Education, Inc.
Figure 6.17: The WS-Coordination
completion process.
Copyright © Pearson Education, Inc.
Figure 6.18: Coordination as it relates to other parts of SOA.
Copyright © Pearson Education, Inc.
Figure 6.19: The TLS Accounts Payable, Vendor Profile, and Ledger
Services being managed by a coordination.
Copyright © Pearson Education, Inc.
Figure 6.20: Atomic transactions apply an all-or-nothing requirement to
work performed as part of an activity.
Copyright © Pearson Education, Inc.
Figure 6.21: The atomic transaction coordinator service model.
Copyright © Pearson Education, Inc.
Figure 6.22: The coordinator requesting that transaction participants
prepare to vote.
Copyright © Pearson Education, Inc.
Figure 6.23: The transaction participants voting on the outcome of the
atomic transaction.
Copyright © Pearson Education, Inc.
Figure 6.24: The coordinator aborting the transaction and notifying
participants to rollback all changes.
Copyright © Pearson Education, Inc.
Figure 6.25: Atomic transaction relating to other parts of SOA.
Copyright © Pearson Education, Inc.
Figure 6.26: All changes made by the TLS Accounts Payable, Vendor
Profile, and Ledger Services are under the control of an atomic
transaction.
Copyright © Pearson Education, Inc.
Figure 6.27: A business activity controls the integrity of a service activity
by providing participants with a “plan B” (a compensation).
Copyright © Pearson Education, Inc.
Figure 6.28: The business activity coordinator service model.
Copyright © Pearson Education, Inc.
Figure 6.29: Two atomic transactions residing
within the scope of a business activity.
Copyright © Pearson Education, Inc.
Figure 6.30: A business activity relating to other parts of SOA.
Copyright © Pearson Education, Inc.
Figure 6.31: The TLS Purchase Order Submission Process wrapped in
a long-running business activity and spanning two organizations (two
participants).
Copyright © Pearson Education, Inc.
Figure 6.32: An orchestration controls almost
every facet of a complex activity.
Copyright © Pearson Education, Inc.
Figure 6.33: A process service coordinating and exposing functionality
from three partner services.
Copyright © Pearson Education, Inc.
Figure 6.34: The process service, after first being invoked by a partner
service, then invokes another partner service.
Copyright © Pearson Education, Inc.
Figure 6.35: Orchestration relating to other parts of SOA.
Copyright © Pearson Education, Inc.
Figure 6.36: The extended TLS
Purchase Order Submission Process
managed by an orchestration and
involving numerous potential partner
organizations.
Copyright © Pearson Education, Inc.
Figure 6.37: A choreography enables collaboration between its
participants.
Copyright © Pearson Education, Inc.
Figure 6.38: A choreography composed of two
smaller choreographies.
Copyright © Pearson Education, Inc.
Figure 6.39: A choreography enabling collaboration between two different
orchestrations.
Copyright © Pearson Education, Inc.
Figure 6.40: Choreography relating to other parts of SOA.