FIORANO FOR SAAS

 Fiorano addresses the need for integration technology that bridge the gap between SaaS providers and Consumers.  Fiorano enables the creation of ‘mediations’ to facilitate ‘bi-directional’ integration between hosted and on-premise applications.

 A simple case could be where a SaaS provider exposes a service interface (as a WSDL).  The service could be implemented in as an Event-Process, as a Java Service, a DB integration, or a combination of all.  Client creates its own WS client to invoke the SaaS provider service directly. THE SIMPLEST CASE

NON-HTTP TRANSPORTS  Most real life scenarios revolve around cases where a client would not invoke a WSDL service directly.  Fiorano provides for multiple non-Http transports including FTP, POP, SMTP and others.

HANDLING NON-SOAP AND NON-XML PAYLOADS  In most cases, the information to be processed resides in an Excel spread sheet or a.csv file rather than a SOAP message.  In order to handle this the ESB needs to not only pick the messages from the relevant transport, but need to transform the data for the service to process correctly.

MOVING TOWARDS MEDIATIONS…  There are additional pre-processing steps involved between the client and the end point service implementation, like security, identity processing, transformations, application of reliability and error handling.  These steps when coupled with transports and both the endpoints is collectively referred as ‘Mediation’

WHAT KIND OF STEPS CAN BE IN A MEDIATION?  Transports (http, , ftp, jms, database. All transports are schedulable)  Transforms (into and out of XML, within XML)  Validation (syntax and semantic)  Security (WS-I basic profile, SSL)  Logging (Log4j)  Custom code (Java, C, C++, C#, other scripting languages etc.)  Error handling

MULTIPLE TENANCY, MULTIPLE MEDIATIONS A SINGLE SERVICE  Different clients may have different mediations for the same service, reflecting different and unique ways in which they wish to interact with the service. For example: ▫ Accessing the service over ▫ Using SSL instead of WS-Security ▫ Transforming from a different kind of spreadsheet.

THE SAAS HOSTING MODEL  Where do these mediations actually operate? ▫ The network boundary can actually be drawn at different places depending on the requirement. ▫ Most common use cases are where Mediations are hosted by the SaaS provider.

CLIENT-HOSTED INTEGRATIONS  Not all client integrations are hosted by a SaaS provider on a customer’s behalf.  Once developed, it may be preferable for the customer to assume ownership and operation of mediation.  This is a very common model for many customers since they can control, modify and maintain the mediation more easily this way

THIRD PARTY HOSTED MEDIATIONS…  In this case, the integrations are not hosted by either the client or the SaaS provider, but rather by some trusted third party.  Only some sub set of integrations which are ‘strategic’ in the sense of offering a path between common end points, is likely to warrant a business in and of itself.

SAAS PROVIDER ACTING AS A MEDIATION CLIENT…  The same set of approaches that have been outlined apply equally to SaaS vendor who may fulfill part of their service contract by outsourcing or delegating to third party providers.  These 3 rd parties may or may not expose SOAP / WSDL interfaces, hence requiring a set of mediations to interact with them.

FIORANO PLATFORM COMPONENTS FOR SAAS  Fiorano Studio allows business analysts to compose, deploy, monitory and modify mediations in the form of Event Processes, from a single location  FES (Fiorano Enterprise Server) serves as the repository of all Event Processes and as a central point of monitoring and management  FPS (Fiorano Peer Server) runs individual services within the event- flows that implement the mediations; provides a robust, secure and scalable peer-to-peer platform for deploying the actual mediations.

FIORANO FOR SAAS - PLATFORM ARCHITECTURE

WHY FIORANO FOR SAAS?  Powerful, Easy to Use Platform  Quick time to market  Easy on-boarding of new clients  Direct mapping of SaaS mediations to Fiorano Event-flows  Lower total costs for implementation  Re-useable services/mediations  Full multi-channel support  Scalable and standards-based  Easy to manage and monitor  Enterprise-class High availability

THANK YOU! VISIT