Cape Clear ESB Platform for On-Demand Integration
Go to selected chapter 1 2 3 4 5 6 7 8 9 10 11 12 13 14
 

Cape Clear 7 ESB for SaaS

Handling non-SOAP and non-XML payloads

Of course, this still presumes that the client is emitting SOAP messages, which may be an onerous assumption. It is, in our experience, very common that when someone wants to email or ftp information to an address, that information is much more likely to be formatted as an Excel spreadsheet or a CSV than it is to be a SOAP message. In order to handle this, the ESB needs to not only pick the message up from the relevant transport, but it needs to know how to create a suitable SOAP message envelope, populate it with endpoint details, and also populate the message body (or attachment) with appropriate information from the message so that the service can process it correctly.

Next: Moving towards mediations…

footer