The A2X request/response web services are standard SOAP web services. The asynchronous services communicate typically via SAP's integration solution, Process Integration or SAP PI. This reliable communication between the A2A web services and SAP PI is based on a SAP specific protocol (XMB, based on SOAP with Attachments and a number of custom SAP header fields).

But more interesting is the support of SAP's A2A web services for WS-ReliableMessaging. WS-RM is one of those many WS-* standards. WS-RM is a protocol for reliably delivering messages over SOAP. SAP supports versions 1.0 and 1.1 of WS-RM.

We recently connected WebSphere ESB 7.5 with SAP using WS-RM. The communication from SAP over WS-RM to the IBM ESB was rather trivial. WS-RM was well supported. One attention point was the configuration of a WS-Addressing action for each operation.

SAP is also coming up with an alternative for WS-RM, called "SAP-RM" or "plain SOAP". It simply boils down to a HTTP POST with filtering of duplicate messages. This mechanism has been available in SAP's integration solution PI but is now also being supported in modern SAP back-end applications. We only tested this with soapUI, not yet from IBM WESB.

1 comment:

I am trying to access an enterprise service delivered by SAP from SOAP UI.

I have enabled the all the settings that you have mentioned SRT_ADMIN_CHECK is greenI have not enabled WSRM in SOAP UI,I keep getting this error "Only the anonymous value for wsrm:AcksTo is supported"Any clues ?

Also when i enable WSRM and WSA in SOAP UI and try the same i can see that first SOAP UI tries to createsequence then 2nd and 3rd step mentioned here.There i get a "HTTP 401 Unauthorized."