Cape Clear 7 ESB for SaaS
The simplest case
Let’s consider first the simple case where a SaaS provider exposes a service interface (as a WSDL). This service may be actually implemented as a BPEL script, as a Java service, as a database integration, or any combination of the above. In this case, in the simplest view, the customer is (somehow) able to create their own web service client, which they use to invoke directly on the SaaS provider service. If the client is to handle responses (or errors), they will need to register a suitable callback interface, and be able to handle and react to incoming SOAP messages.
