Web services scenarios

These common web services scenarios are organized according to the role that is played by the integration node.

You can also create web services in the new Services editor by defining the service interface, and implement the operations as separate message flows. For more information, see Developing integration solutions by using integration services.

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

In scenario A, the WSDL description exists and is imported and used by the message flow.

In scenario B, the WSDL description is generated in an existing message set. The WSDL is used by the message flow and might also be exported for use by an external client.

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

Scenario A: You want the integration node to invoke an existing web service:

See Integration node calls existing web service

Scenario B: You want the integration node to expose an application as a previously defined web service:

See Integration node implements existing web service interface

Scenario C: You want the integration node to expose an application as a new web service:

See Integration node implements new web service interface

Scenario D: You want the integration node to expose a web service to a non-web service client:

See Integration node implements non-Web-service interface to new web service