Show TOC

SAP Reliable Messaging (SAP RM)Locate this document in the navigation structure

Definition

Web service bindings can consist of one-way and/or request-response operations. Web service messages with one-way operations are sent asynchronously, which means that they are non-blocking for the sending application. Usually, the WSRM standard is used for asynchronous operations, but one-way messages can also be sent using SAP Reliable Messaging (SAP RM) instead.

Advantages:

  • Enables communication via one-way messages with partner software that does not support WS-RM.

  • Less messaging traffic because technical WSRM messages (for example, wsrm:CreateSequence, wsrm:TerminateSequence) are avoided

  • SAP-proprietary extensions for Qualities of Service ( ExactlyOnce, ExactlyOnceInOrder) are aligned with the plain soap adapter of SAP NetWeaver Process Integration.

Disadvantage:

  • No standardized way for Qualities of Service (ExactlyOnce, ExactlyOnceInOrder). WS-RM allows SOAP messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures. With SAP-RM, this is only possible in a proprietary way. In communication with non-SAP software, duplicate message delivery, lost messages or out-of-order processing may happen.

At design time, the operation of a stateless Web service provider and consumer must be defined as Asynchronous or Asynchronous reliable , which is documented in the WSDL of the Web service. At configuration time, you do not have to configure the Web service provider for WSRM or SAP RM, but it reacts according to the inbound message. So a WSDL does not include information that SAP RM is to be used. On consumer side, you select the appropriate quality of service for a Web service consumer.

The programming model for Web service consumers is not affected. Web service calls and all Web service protocols can be used the same way as with WSRM services. In-order processing is also executed with logical sequences and through bgRFC queues. In case an operation of a Web service provider is defined as Asynchronous reliable , an incoming message must have a message ID. Otherwise, the recognition of duplicates is not possible. For communication within a closed ABAP system landscape, this is automatically fulfilled if the operation of the assigned Web service consumer has the same operation profile assigned.

Messages that are sent via SAP RM are displayed in the Web service message monitor under the adapter type Plain SOAP .

More Information

Web Services Reliable Messaging

Programming with Sequences

Configuring a Consumer Proxy

Monitoring ABAP Web Service Messages

For more information about the interoperability with SAP NetWeaver Process Integration and third party products, see the SAP Community Network under Plain Soap in the ABAP Connectivity - ABAP Web Services wiki at http://wiki.sdn.sap.comInformation published on SAP site.