Cape Clear 7 ESB for SaaS
What features of Cape Clear’s ESB facilitate what has been described?
- Studio—build the services, mediation steps, BPELs, policies
- Mediation builder—chain these together and make them specific for a given set of endpoints, transports, mediation steps and policies.
- Server—host the mediations and services in a robust, secure and scalable fashion.
Some other products, and some other open source components can be used to address parts of this overall problem. However, none that we’re aware of address the problem in total in a unified way, and offer end-to-end tool and server support which takes this from the domain of rocket science into the domain of something that is achievable by mere mortals.
Our tools and server enable mere mortals to rapidly create rich, reliable, asynchronous, per-client-per-service mediations.
What kind of steps can be in a mediation?
- Transports (http, email, ftp, jms, database. All transports are schedulable)
- Transforms (into and out of XML, within XML)
- Validation (syntax and semantic—schematron)
- Security (WS-I basic profile, SSL)
- Logging (Log4j)
- Policy (WS-Policy)
- Custom code (BPEL, Java, ruby etc.)
- Error handling
How does it work?
- Single, spring-based mediation configuration.
- Shared flow runtime with our proven BPEL engine
- Support for multiple transports (JAX-WS engine…)
- Unified tool support.
