At this point, SOAP IWS only returns HTTP 200 after successful processing, which limits it to synchronous processing. It would be good if it could return HTTP 202 instead, especially when an asynchronous approach is desired.
In many cases, the data bus is not interested in receiving a full response — it only requires confirmation from the CCB in the form of an HTTP 202 status code. Unlike IWS, outgoing messages can operate in both synchronous and asynchronous modes, depending on the configuration of the HTTP transport method:
- In asynchronous “Send” (“Fire-and-forget”) mode, the system sends a message to the HTTP endpoint and does not wait for a response, except for a possible confirmation (HTTP 202 OK).
- In synchronous “SendReceive” mode, the system sends the message and waits for both a response and confirmation (usually HTTP 200).
I propose that CCB should be able to handle message reception asynchronously.