Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services >

About One-Way Operations and Web Services

One-Way operations provide a means of sending a request to a Web Service with the expectation that a SOAP response will not be returned. The Siebel application provides the ability to publish and consume Web Services that implement one-way operations.

One-way operations come into play in both inbound and outbound scenarios:

• Inbound. If the Business Service Workflow method does not have any output arguments, it is a one-way operation.
• Outbound. If the service proxy method has no output arguments, it is a one-way operation.

Consider using one-way operations when data loss is tolerable. In cases involving one-way operations, you send a SOAP request and do not receive a SOAP response. The provider receives the SOAP request and processes it.

NOTE:  It is important to note that SOAP faults, if any, are not returned as well.

Defining Support for One-Way Operations

In defining support for one-way operations, the following WS-I Basic Profile specifications are taken into account:

• Specification R2714. For a one-way operation, an instance must not return a HTTP response that contains a SOAP envelope. Specifically, the HTTP response entity-body must be empty.
• Specification R2715. An instance must not consider transmission of one-way operations complete until a HTTP response status code of either 200 OK or 202 Accepted is received by the HTTP client.
• Specification R2727. For one-way operations, an instance must not interpret the HTTP response status code of 200 OK or 202 Accepted to mean the message is valid or that the receiver would process it.