Middleware Must Support Bulk SOAP Operations

In order to reduce the number of SOAP requests between the OFSC platform and Middleware, all methods in the Outbound API support bulk data. That is, each SOAP request can contain the data related to several messages. Also, a response record provides a separate execution result on a per message basis.

It is important when implementing SOAP Service to interpret the <messages> element as array. This may not be noticeable in the initial test with a single message, but the SOAP Service that does not have this feature will fail eventually.

The same applies for Middleware SOAP Client for advanced workflow. It should send 'set_message_status' requests periodically with all messages for a given period (e.g. every few seconds). It should not send each message status individually as it arrives to Middleware.

Example of 'send_message' bulk request (details omitted for clarity)

<env:Envelope> 
	<env:Body> 
		<send_message xmlns="urn:toatech:agent"> 
			<user>...</user> 	
			<messages> 
				<message> <!-- message payload --> 
				</message> <message> <!-- message payload --> 
				</message> <message> <!-- message payload --> </message> 
				... <!-- more messages --> 
			</messages> 
		</send_message> 
	</env:Body> 
</env:Envelope>