29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Workflow-oriented<br />

A workflow message exchange pattern can be used to implement a business<br />

process where multiple service producers exist. In this scenario, the message<br />

that is passed from Web service to Web service maintains the state for the<br />

workflow. Each Web service plays a specific role in the workflow (Figure 11-6).<br />

Service<br />

Consumer<br />

Service 3<br />

Producer<br />

Service 1<br />

Producer<br />

Service 2<br />

Producer<br />

Figure 11-6 Workflow-oriented message exchange pattern<br />

This message exchange pattern is inflexible and does not facilitate reuse. The<br />

workflow, or choreography, has been built into each of the Web services, and the<br />

individual Web services can no longer be self-contained.<br />

Publish-subscribe<br />

The publish-subscribe message exchange pattern, also known as the<br />

event-based or notification-based pattern, is generally used in situations where<br />

information is being pushed out to one or more parties (Figure 11-7 on<br />

page 369).<br />

Implementation of this pattern at the application level is one possible<br />

architecture. Alternatively, the Service 1 Producer component can publish SOAP<br />

messages to a messaging infrastructure that supports the publish-subscribe<br />

paradigm.<br />

368 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!