WS-ReliableMessaging - requirements for interaction with other implementations

The information and configuration that is needed for another vendor's reliable messaging source to send messages to a WebSphere® Application Server reliable messaging destination, or for a WebSphere Application Server reliable messaging source to send messages to another vendor's reliable messaging destination.

Using another vendor's reliable messaging source to send messages to a WebSphere Application Server reliable messaging destination

For another vendor's WS-ReliableMessaging implementation to interact with a WebSphere Application Server WS-ReliableMessaging endpoint, the other vendor's reliable messaging source needs to know the target endpoint address and port for the WebSphere Application Server application that is enabled for reliable messaging. The WS-ReliableMessaging protocol messages are sent to the same endpoint address as the application messages. You can get this address from the WSDL published by the WebSphere Application Server endpoint.

The reliable messaging source controls the endpoint reference used for acknowledgement messages, so the other vendor's product might have to use the WS-Addressing anonymous URI. For more information, see WS-ReliableMessaging - How it works. Whether or not the reliable messaging source uses the WS-Addressing anonymous URI, the WebSphere Application Server reliable messaging destination can work with the reliable messaging source without further configuration.

A WebSphere Application Server reliable messaging destination cannot tell whether the reliable messaging source is durable and transactional. If you want durable transactional web services, check that the other vendor's reliable messaging source supports that mode of operation, as well as configuring the WebSphere Application Server end of the link.

Using a WebSphere Application Server reliable messaging source to send messages to another vendor's reliable messaging destination

For an application in WebSphere Application Server to invoke a web service that uses WS-ReliableMessaging, the information required is the target endpoint address and port for the web service being invoked. The WS-ReliableMessaging protocol messages are sent to the same endpoint address as the application messages. You can usually get this address from the WSDL published by the target Web service.

The WebSphere Application Server Source is provided with additional WS-ReliableMessaging configuration, modeled as part of the policy set associated with the web service client. The policy set might configure the reliable messaging source to use the WS-Addressing anonymous URI as the address within the endpoint reference used for acknowledgement messages. For more information, see WS-ReliableMessaging - How it works

WebSphere Application Server cannot tell whether the reliable messaging destination is durable and transactional. If you want durable transactional web services, check that the other vendor's reliable messaging destination supports that mode of operation, as well as configuring the WebSphere Application Server end of the link.




Related concepts
WS-ReliableMessaging - How it works
Interoperation with other WS-ReliableMessaging providers: use pattern
Related tasks
Detecting and fixing problems with WS-ReliableMessaging
Adding assured delivery to web services through WS-ReliableMessaging
WS-ReliableMessaging
Reference topic Reference topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 7:16:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-iseries&topic=rwbs_wsrm_3p
File name: rwbs_wsrm_3p.html