Web Services provider configuration overview

The purpose of a Web Services provider mode configuration is to expose a service to one or more partner consumers. In this mode, the Web Service provider acts as a server, responding to requests from partner clients.

Illustrations and descriptions

The following figures illustrates schematically how Activator processes requests from remote Web Service consumers.

Example 1: Two way service, synchronous response

In the context of a Web Service exposed by Activator, and configured for synchronous response:

1. A partner connects to Activator over HTTP in client mode, and sends a service request.
2. Activator maintains the HTTP connection open while processing the request in a service (through a series of components).
3. Activator generates a service response (or a fault).
4. Activator applies outbound collaboration settings to control how the response is sent to the Web Service consumer partner.
5. Activator sends the response back through the pending HTTP connection.
6. The partner closes the HTTP connection.

Example 2: One way service

1. A partner connects to Activator over HTTP in client mode, and sends a service request.
2. Activator acknowledges (at protocol level) the receipt of the message.
3. The partner closes the HTTP connection.
4. Activator processes the request in a service (through series of components).
5. Activator applies outbound collaboration settings to control how the response is sent to the destination application or partner.
6. Activator delivers the message(s) to the final destination

Configuration overview

To configure a Web Services provider, you complete two principal tasks:

• Define the content of the Web Service - This involves specifying the format of both the request for the service, and the response to the request. The message content of Web Services exchanges is exchanged in XML formatted files. The format of these files is defined by XML schemas.
• Define a communications framework – This involves specifying the transport protocol and access parameters that enable consumers to inject messages into your system, and for you to respond to those messages. Communications with your Web Service Partners is done over HTTP.

Related topics

• Web services
• Web Services consumer configuration
• Web Services collaboration settings
• Web Services message protocol
• Implement MTOM encoding
• Lockout settings for Web Services (HTTP embedded) users
• Troubleshoot Web Services configurations