Im our szenario we want to process an incoming Web Service
on our SAP XI Backend ABAP Stack. Since the WebService doesn't
care about the status of the request we decided to implement
the process asynchronous: we configured an async/outbound Interface
for the WebService and an async/inbound Interface for our
ABAP-Server-Proxy with mappings and so on.
Basically it works fine: we can send thousands of WebServices
to XI and can se them beeing processed in the backend system.
From the WebService point of view the overall processing
time is rather short simply because it has not to wait for
the completion of the relatively complex process.
And here is the question:
even though the process itself works fine, all inbound and
outbound XI messages belonging to this service are in the
'internal error' status (red icon). The reason could be
that an SOAP-Service is actually designed for sychronous processes
and our XI will not send the HTTP OK back to the calling WebService
client:
<i>Error message on the client:
com.sap.aii.af.ra.ms.api.DeliveryException:
XIServer:HTTP_RESP_STATUS_CODE_NOT_OK
error message in XI:
Error code: ICF-IE-http -c: 110 -u: ESSENBERG GU -l: E -s: XD1
-i: sxixd1db_XD1_02 -w: 1 -d: 20070214 -t: 141620 -v: RABAX_STATE
-e: OBJECTS_OBJREF_NOT_ASSIGNED_NO </p> <br/> <p>
HTTP 500 - Internal Server Error <br/> <p>
Your SAP Internet Communication Framework Team
</p> </td> </tr> </table> </body> </html>
</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>In der HTTP-Antwort liegt der Status-Code 500 mit der
Beschreibung Internal Server Error vor Fehler beim Senden per
HTTP (Fehlercode: 500, Fehlertext: Internal Server Error)</SAP:Stack>
<SAP:Retry>N</SAP:Retry></i>
No dump in st22.
A sync/async bridge in this case makes no sense since there is actually
no need for any ccBPM function. Not to mention the perfomance.
Anybody any idea?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.