• Save
Building Enterprise-Ready SaaS Products Open for Integration
Upcoming SlideShare
Loading in...5
×
 

Building Enterprise-Ready SaaS Products Open for Integration

on

  • 2,018 views

http://www.impetus.com/webinar_registration?event=archived&eid=41...

http://www.impetus.com/webinar_registration?event=archived&eid=41

The webcast discusses:

• Architecture and design approaches to build integration-ready enterprise SaaS application
• Integration challenges in enterprise grade SaaS solutions
• Best practices in developing ‘open for integration’ SaaS solutions

Statistics

Views

Total Views
2,018
Slideshare-icon Views on SlideShare
2,018
Embed Views
0

Actions

Likes
9
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Here we see some of the main characteristics of a SaaS application. These include, but does not limit to, Multi-tenancy being the major driving and influential factor, followed by monetization, configurability, scalability, integration and security.
  • There are various factors which effect SaaS adoption in enterprises and integration is among top of the list.For a ready adoption of any saas solution the most important factor is provisioning a new tenant and its users seamlessly. Any obstructive experience of provisioning a new tenant adversely impacts consumer acceptability of saas solution in their ecosystem. Enterprises uses various systems in their ecosystem and require easier adoption of any product in their family of products. The complexity in providing flexible end points in the SaaS product to be able to easily integrate with any external systems is a major challenge for any SaaS provider.
  • The most important entity in any application is its users and every enterprise has its own set of user who would also be using the application. A SaaS based Solution would be able to provide integration end points so that it can connect with the user base of the target tenant. Loosely couple design would enable easy integration. As seen in this diagram that a SaaS product would require an integration so that it can communicate the user base of different tenants.
  • One of the way of integrating the tenant user base with SaaS product is through Federated Identity Manager. The user identification, authentication and authorization is federated to tenant user base and based on the mapping between user roles and permissions the SaaS products behaves.As seen in this diagram that when tenant user tries to access the application the Access Control module directs the authentication request to the Application’s Server and it tries to authenticate the user based on the tenant configurations. If the server is configured to communicate the tenant user base where a treaty is already in place, it gets the user authentication response and allows or dis-allow the application usage based on the response received. The LDAP sever in the given scenario can be replaced with set of services for user authentication, authorization and user management.
  • Many a times business user requires usage of multiple systems to answer a specific query and since two or more applications are required in the process it is very annoying to log in different application to access the required data. The ability of the SaaS product to integrate with the tenants authentication and authorization module and be able to provide Single signOn will solve such issues.As you can see in the diagram that when user accesses the application the access control module communicates with the configured tenant’s SSO application and allows the access to the application without requiring to access the user base directly.
  • In an enterprise world on business process or business entity is spread across various boundaries and to complete a task business users interact with multiple systems to process one client request. These integrated system in the process requires similar data.For example consider the following scenario where the order management application requires the customer information to make the shipment and the customer details can either be managed by the same application itself or it can be integrated with another application where they both share the same data and the data is managed by the second application which in this case is customer management application. The integration configurations module(ICM) provides mechanism to enable tenant specific integration configurations.
  • As we have seen in the earlier slide that how two system share same data for completing the process. Similarly the processing of on a complex business process be distributed over multiple systems.Consider the following scenario where the automated bill management system makes the bill payments automatically on the payment date. The systems makes use of external payment system passes it the required information and the payment system then makes the payment. The payment system returns the response token back to the bill management system which finally generates the receipt for the user.The complete bill payment processing is distributed over two different system which are integrated to complete the task based on the required business flow.
  • As seen in the earlier slide that the shared business data and services along with distributed processing is desirable feature for Integration and well designed system which works on the loosely coupled services makes the work easier.A service is a well-defined function that is universally available and responds to requests from “service consumers”. Once an enterprise assembles a collection of useful services, managing the services becomes an important function.First of all, applications need some form of service directory, a centralized list of all available services.Second, each service needs to describe its interface in such a way that an application can “negotiate” a communications contract with the service.These two functions, service discovery and negotiation, are the key elements that make up a service-oriented architecture.Service-oriented architectures (SOAs) blur the line between integration and distributed applications. A new application can be developed using existing, remote services that may be provided by other applications. Therefore, calling a service may be considered integration between the two applications. On the other hand a service-oriented architecture usually provides tools that make calling an external service almost as simple as calling a local method (performance considerations aside). Because all services are available in a consistent manner, SOAs are sometimes referred to as “service bus architectures”.The different connectors enables the mapping of services of an application with external services or applications.
  • Internal integration points for a SaaS application translates to those integration points that the SaaS application natively/internally consumes. These integration points need to be designed for meeting the required performance, scalability and SLA requirements.External integration points for a SaaS application translates to integration of SaaS application with external on-premise/tenant’s system. In order to enable such integrations, the SaaS application should be built to dynamically provision various endpoints for integrating with such systems. This integration may be via an ESB or via Integration servers as part of the complete SaaS solution.Any enterprise would have standards driven business processes and messaging. In order to enable integration with such diverse systems the usage of standard techniques and processes is very critical.
  • I would now like to share with our audience about our Saas Maturity Model.Typically ISVs are increasingly keen to adopt the SaaS business model and delivery platform. There are various motivation factors like; lower cost of application delivery, recurring revenue model etc. behind it.We at Impetus, have developed a SaaS Maturity Model which provides a framework for quickly assessing the current level of maturity of a product offering. This model also presents a roadmap for working towards more mature, and feature-rich SaaS offering.
  • In terms of the levels of our proposed maturity model – there are four levels that mark the increasing levels of sophistication of SaaSproduct offering. At the lowest rung, you are essentially not a SaaS application provider because you are not implementing multi-tenancy and are being reactive to each new customer you acquire. This is the base level. The next level is managed – in which you start seeing elements of multi-tenancy at least at an infrastructural level. As you move towards the Adaptive and Optimizing levels, you will see more sophisticated implementations of multi-tenancy as well as the other elements associated with SaaS applications. We have further mapped out various challenges across various maturity levels and have come up with a comprehensive maturity model for SaaS applications and Taruna that probably require another webinar to cover all the details.
  • I would now like to share with you the Impetus approach to SaaS Enablement.iSaaS is impetus capability to provide SaaS enabled solution not only for new application, but also for modifying existing application to a SaaS model. As seen here, iSaaS platform provides various capabilities out of the box. The main driving factor being multi-tenancy, the other capabilities revolve around other much required features from building and managing SaaS application. This platform provides SaaS enablement for Java based application with support on all major application servers and database servers.

Building Enterprise-Ready SaaS Products Open for Integration Building Enterprise-Ready SaaS Products Open for Integration Presentation Transcript

  • Building Enterprise-Ready, Open for Integration SaaS Products
    May 13th, 2011
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Outline
    SaaS Characteristics
    Integration Challenges
    Factors that Impact Integration
    Architecture & Design Approach
    User Integration
    Application Integration
    Best Practices
    SaaS Maturity Model
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • SaaS Characteristics
    Key
    Elements
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Integration
    User Integration with SaaS Products
    Application Integration with SaaS Products
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Factors that Impact Integration
    What affects Integration approaches & strategies
    Multi-tenancy approach
    Configuration support
    Security considerations
    Customization requirements
    Impact of Integration
    Scalability & Performance
    Subscription Model
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Integration Challenges
    Seamless integration with tenants’ user base
    Integration of SaaS product with external customer systems (on-premise)
    Provisioning flexible end-points for enterprise applications in SaaS products
    How to ensure secure and consistent integration in a SaaS model?
    Integration with disparate systems
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • User Integration
    • User Integration with SaaS Products
    Tenant 1: Users
    SaaS
    Products
    Integration Engine
    Tenant 2: Users
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • User Integration
    • Federated Identity Management (IDM)
    Configure
    ACL
    Tenant 1
    Tenant 2
    Tenant 1
    Tenant 2
    Retrieves ACL
    Tenant 1
    LDAP Server
    SaaS Application
    Retrieves ACL
    Access Control
    Configure
    ACL
    LDAP Server
    Tenant 2
    LDAP Server
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • User Integration
    • Single Sign On Integration (SSO)
    Configure
    ACL
    Tenant 1
    Tenant 2
    Tenant 1
    Tenant 2
    Authenticates User
    Tenant 1
    Authentication
    Server
    SaaS Application
    AuthenticatesUser
    Access Control
    Authentication
    Server
    Configure
    ACL
    Tenant 2
    Authentication
    Server
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Application Integration
    Requires generation of events
    Push Mechanism-
    Synchronous means of publishing the event
    Real-time generation of events
    Pull Mechanism-
    Offline event integration
    How event generation helps?
    Facilitates easier integration of processes
    Enables application to create audit logs
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Application Integration
    Loose Coupling within processes and modules facilitate flexible integration
    Interaction of configurable parameters and adapters provide flexibility and easy integration.
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Application Integration
    Loose Coupling within processes and modules facilitate flexible integration
    Interaction of configurable parameters and adapters provide flexibility and easy integration.
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Data Sharing
    Order Management System
    Complete
    Shipment
    Check Order
    From Inventory
    Retrieve
    Customer Details
    Integration Configuration Module (ICM)
    Customer Management System for Tenant 1
    Customer Management System for Tenant 2
    Retrieve
    Customer Details
    Retrieve
    Customer Details
    Database
    Database
  • Business Process Integration
    Bill Management System
    Check Bill Payment
    Due Date
    Make
    Payment
    Generate
    Receipt
    Payment System
    Third Party Payment Gateway
    Make Payment
    Make Payment
  • Service Oriented Architectures
    SaaS Product
    Application
    Service 1
    Service 1
    Connector A
    Service 1
    Connector B
    Service 1
    Connector C
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Summing up..
    Preferring configuration over assumption during designing application phase
    Optimize internal integration points for resource sharing, performance and SLAs
    Driving external integration points by standard specifications and flexible end-points
    Implementing SaaS applications with standard messaging and business process integration
    Loose Coupling within processes and modules is the key to flexible integration
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • SaaS Maturity Model
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • SaaS Maturity Model
  • iSaaS – Simplifying SaaS
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Impetus Technologies
    We offer innovative product engineering
    and technology R&D services
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Questions
    Please send in your questions using the chat panel
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41
  • Thank you
    Mail us at inquiry@impetus.com
    or visit www.impetus.com
    Meet us at
    Recorded version available at
    http://www.impetus.com/webinar_registration?event=archived&eid=41