Transactions

Use the -x option when starting the listener, to run web services transactionally. Select the integrity of messages by setting the persistence option in the service URI.

Web services

Use the -x option when starting the listener, to run web services transactionally. On .NET Framework 1 and 2 the SOAP listener uses Microsoft Transaction Coordinator (MTS). On Axis 1.4, the SOAP listener uses queue manager coordinated transactions.

Web service clients

The SOAP senders are not transactional.

IBM MQ bindings

We can set the binding type for the SOAP sender. It can connect as an IBM MQ server application, or as a client application. We can also bind the SOAP sender as an XA-client on .NET.

Message persistence

Select the level of persistence by setting the Persistence option in the URI.

Web service transactions

We can use web service transactions, because the SOAP sender is not transactional. If you write your own SOAP sender, and intend to use web service transactions, do not create a transactional SOAP sender. We cannot send the request message and receive the reply message in the same transaction. The send and receive must not be coordinated by the web service transaction.