Integration Server 10.3 | Web Services Developer’s Guide | Web Services Reliable Messaging (WS-ReliableMessaging) | Using Reliable Messaging in Integration Server
 
Using Reliable Messaging in Integration Server
 
Persistent Storage Support for Reliable Messaging Data
Limitations When Using Reliable Messaging in Integration Server
To ensure that the SOAP messages are reliably delivered and to track the messages, the reliable messaging source and destination use reliable messaging sequence keys. A sequence key is a user-defined identifier to indicate the sequence to which a message belongs. A reliable messaging client associates a sequence key to a message sequence based on the endpoint URL to which the message sequence is directed.
Integration Server also uses sequence Ids that are unique identifiers used by the reliable messaging servers and clients to identify a particular reliable messaging sequence.
The following steps describe what happens during exchange of SOAP messages where reliable messaging is used:
1. The reliable messaging source sends a message or a series of messages that are transmitted across a communication link to a reliable messaging destination. Along with the messages, the reliable messaging source also sends a request to the recipient asking the recipient to acknowledge the messages.
2. When the reliable messaging destination receives the messages, it sends an acknowledgement back to the reliable messaging source either individually for each message or as a single acknowledgement for a series of messages.
3. If the messages are not delivered in the first attempt, the reliable messaging source retransmits the messages based on the reliable messaging configuration until the message is delivered and the acknowledgement is received or the sequence has timed out or is terminated.
Keep the following points in mind when you configure Integration Server to use reliable messaging:
*Integration Server supports WS-ReliableMessaging Version 1.1 only.
*The namespace prefix wsrm represents the URI http://docs.oasis-open.org/ws-rx/wsrm/200702.
*The namespace prefix wsrmp represents the URI http://docs.oasis-open.org/ws-rx/wsrmp/200702.
*To use WS-ReliableMessaging, you attach a standard WS-Policy, which includes reliable messaging assertions, to a web service descriptor. For more information about defining your own policies, see WS-Policy Files and Guidelines for Creating WS-Policy Files. For instructions about attaching a WS-Policy to a web service descriptor, see webMethods Service Development Help.
*To use WS-ReliableMessaging, you can attach a pre-defined WS-Policy named ReliableMessaging that Integration Server provides. This policy is available in the following directory:
Integration Server_directory \instances\instance_name\config\wss\policies
*Integration Server uses a unique reliable messaging sequence key to track the progress of a set of messages that are exchanged reliably between a web service consumer and provider.
*Integration Server supports only the In Order delivery assurance for reliable messaging.
*You use the Integration Server Administrator to configure reliable messaging for web services. By default, Integration Server applies the reliable messaging configuration defined on the Settings > Web Services > Reliable Messaging > Edit Configuration page to all web service providers and consumers. If you want to override the server-level reliable messaging configuration for a specific web service provider or consumer, define reliable messaging properties for the associated web service endpoint alias. For more information about configuring reliable messaging properties for web services and for managing reliable messaging sequences, see Configuring Reliable Messaging in Integration Server .
*Integration Server provides pub.soap.wsrm built-in services to create and manage reliable messaging sequences. For more information about these built-in services, see webMethods Integration Server Built-In Services Reference.