WS-ReliableMessaging
Contents
- Overview
- WS-Addressing
- WS-AtomicTransactions
- WS-MakeConnection
- WS-Notification
- WS-Policy
- WS-SecureConversation
- WS-Security
Overview
WAS provides support for two levels of the WS-ReliableMessaging spec.
WS-Addressing
WS-ReliableMessaging supports the asynchronous request and reply model in WS-Addressing.
If we use a policy set that includes WS-ReliableMessaging and WS-Addressing policies, and the WS-Addressing policy is configured as optional, WAS overrides the WS-Addressing setting and automatically enables WS-Addressing.
WS-AtomicTransactions
WS-ReliableMessaging transactions do not use the WS-AtomicTransactions protocol.
WS-AtomicTransactions and WS-ReliableMessaging are mutually exclusive when WS-ReliableMessaging is being used, with a managed store, to provide transactional recoverable messaging.
If WS-ReliableMessaging is configured to use an in-memory store, then there are cases where a WS-AtomicTransaction can be flowed between the reliable messaging source and the reliable messaging destination for two-way invocations. In this situation, WS-ReliableMessaging only protects against network failures, not against server failure.
See: using WS-ReliableMessaging
WS-MakeConnection
WS-ReliableMessaging V1.1 uses WS-MakeConnection to enable synchronous message exchange.
WS-MakeConnection uses information contained in WS-Addressing message headers, so for any application that uses reliable synchronous message exchange include both WS-ReliableMessaging and WS-Addressing policy in the policy set.
WS-Notification
If we create JAX-WS based WS-Notification services, we can apply WS-ReliableMessaging policies make the WS-Notification services reliable.
New feature: In WAS ND v7.0, there are two types of WS-Notification service:
- Version 7.0
You configure a V7.0 WS-Notification service and service points to compose a JAX-WS WS-Notification service with WS-ReliableMessaging, or to apply JAX-WS handlers to the WS-Notification service. This is the recommended type of service for new deployments.
- Version 6.1
You configure a V6.1 WS-Notification service and service points to expose a JAX-RPC WS-Notification service using the same technology provided in WAS V6.1, including the ability to apply JAX-RPC handlers to the service.
WS-Policy
The WS-Policy implementation in WAS supports Web Services Reliable Messaging Policy Assertion V1.0 and Web Services Reliable Messaging Policy Assertion V1.1.
Use the WS-Policy protocol to exchange policies in standard format. We can communicate the policy configuration to any other client, service registry or service that supports WS-Policy, including non-WAS products in a heterogeneous environment.
WSDL. For a client, the client can obtain the policy of the service provider in the standard WS-PolicyAttachments format and use this information to establish a configuration that is acceptable to both the client and the service provider. In other words, the client can be configured dynamically, based on the policies supported by its service provider. At any stage - that is, before or after we have built the reliable Web service application, or configured the policy sets - we can set a property that configures endpoints to only support clients that use reliable messaging. This setting is reflected by WS-Policy if engaged.
WS-SecureConversation
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, either of the WS-I RSP default policy sets.
WS-Security
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.
If possible, use WS-SecureConversation rather than WS-Security because the WS-SecureConversation protocol is less susceptible to security attacks.
Related tasks
Set endpoints to only support clients that use WS-ReliableMessaging
Building a reliable Web service application
Detecting and fixing problems with WS-ReliableMessaging
Learn about WS-ReliableMessaging