EOIO or BPM for receiver SOAP messages
In our IDOC - XI - SOAP (R/3 4.7 - XI 3.0 SP17 - WebService) scenario we have a requirement from the receiving WebService that we cannot send two messages to close together (say within one second) in order to allow the WebService time to unpack the message, transform it and forward it to the legacy system. How the WebService is implemented with this restriction I do not know.
How do we solve this?
Will the QoS EOIO solve this issue? In that case, how do we make sure the Idocs is sent with EOIO from SAP and the SOAP calls from XI do the same? I cannot find any QoS for the receiver SOAP adapter.
Or do we have to setup a BPM that implements a wait step for each message? This seems a bit "insecure".
The last option as I see it is implement some logic in SAP to wait for the ALEAUD response message back from the legacy system (the whole interface is async) before it sends the next IDoc.
Can anyone help me find the easiest (and best) solution?
Thanks a lot in advance!