WebSphere Application Server provides support for two levels of the WS-ReliableMessaging specification. This enables backward compatibility with vendors that provide WS-ReliableMessaging support at the February 2005 level, as well as meeting the requirements of the current OASIS specification. This implementation of WS-ReliableMessaging also composes with many other Web services standards.
The Reliable Asynchronous Messaging Profile (RAMP) Version 1.0 uses WS-ReliableMessaging to ensure the reliable delivery of messages.
Following on from the RAMP Version 1.0 specification, the Web Services Interoperability organisation (WS-I) has established a working group to standardize the Reliable Secure Profile. This profile is similar to RAMP Version 1.0, except that it is updated to use WS-ReliableMessaging Version 1.1 with the OASIS WS-SecureConversation specification Version 1.3.
The extent to which WS-ReliableMessaging composes with other Web services standards is described in the following sections:
The WS-ReliableMessaging specification uses WS-Addressing and the implementation fully supports the asynchronous request and reply model proposed in the WS-Addressing specification.
WS-ReliableMessaging composes with WS-Security. The WS-ReliableMessaging headers appended to application messages are signed if required. The WS-ReliableMessaging protocol messages are signed and encrypted if required.
Security processing is done close to the transport: after WS-ReliableMessaging processing at the Web service requester and before WS-ReliableMessaging processing at the Web service provider. This means the messages held in the WS-ReliableMessaging store are not signed and encrypted, so the emphasis is on the administrator to secure the store, if the store being used is the messaging engine in a service integration bus.
WS-ReliableMessaging is designed to work with WS-SecureConversation. A secure conversation context is established and this is used to secure the application messages and the WS-ReliableMessaging protocol messages.
To use WS-SecureConversation, create or apply a policy set that includes both WS-ReliableMessaging and WS-SecureConversation. For example, the RAMP policy set.
The WS-Notification support in WebSphere Application Server is not integrated with the Feature Pack for Web Services, so WS-Notification cannot take advantage of WS-ReliableMessaging in this release.
For more information about WS-AtomicTransactions, see Transaction support in WebSphere Application Server. For more information about using WS-ReliableMessaging transactions, see Providing transactional recoverable messaging through WS-ReliableMessaging.