Cape Clear 7 ESB for SaaS
Non-http transports
Now let’s consider a more realistic case where the client does not want (or is not able to) to create a client to invoke directly on a WSDL service. Let’s say that the client can ftp or email the relevant data to a specified address. In this case, the ESB will need to provide a non-http transport (ftp or POP, in this case), to receive the message, and then forward it to the actual WSDL interface so that it can be processed as before. Cape Clear 7 supports multiple unreliable and reliable transports.
