Web services scenarios

This topic describes some common Web services scenarios. It is organized according to the role played by the broker.

A key consideration is whether a WSDL description for the Web service already exists.

In the first two scenarios below, the WSDL description exists and is imported and used by the message flow.

In the remaining two scenarios, the WSDL description is generated in an existing message set. Again, the WSDL is used by the message flow and may also be exported for use by an external client.

These are generic scenarios and can be implemented using the SOAP domain, or by using an appropriate non-SOAP domain (XMLNSC, MRM, MIME) and basic transport nodes. If you need to use WS-Addressing or WS-Security for a particular implementation, you must use the SOAP domain.

You want the broker to invoke an existing Web service:
See Broker calls existing Web service
You want the broker to expose an application as a previously defined Web service:
See Broker implements existing Web service interface
You want the broker to expose an application as a new Web service:
See Broker implements new Web service interface
You want the broker to expose a Web service to a non-Web service client:
See Broker implements non-Web-service interface to new Web service
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:40

ac34740_