+

Search Tips   |   Advanced Search

Invoking Web service requests transactionally using SOAP over JMS transport


Use the enableTransactionalOneWay property to ensure that one-way and two-way asynchronous Web service requests using the industry standard SOAP over JMS transport will be sent to the destination queue or topic transactionally.

When using JMS to transport JAX-WS or JAX-RPC Web service requests, the default behavior is for the SOAP message to be added to the destination queue or topic non-transactionally or outside of the client application's transaction. Adding the SOAP message to the destination queue or topic is done outside of the transaction to avoid synchronization problems that can occur with two-way synchronous Web service requests. However, we can choose to enable one-way and two-way asynchronous requests to be processed as part of a transaction. Use the enableTransactionalOneWay property to ensure that one-way and two-way asynchronous Web service requests that use the JMS transport are sent to the destination queue or topic transactionally. When the client application invokes the Web service request, the resulting SOAP request message is added to the destination queue or topic as part of the client application's transaction.

Use one of the following ways to enable the enableTransactionalOneWay property.

 

 

Results

we have a Web services client application configured to invoke one-way and two-way asynchronous requests transactionally when using the JMS transport.

 

Next steps

After we have enabled the enableTransactionalOneWay property, run the client application.

 

Related tasks


Use SOAP over Java Message Service to transport Web services
Task overview: Implement Web services applications

 

Related


Options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands

 

Related information


SOAP over JMS protocol