CloudStreams Integration Framework for On-Premises and SaaS Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integration of on-premises applications with cloud applications is challenging due to security concerns, latency, limited customization options, data governance issues, and compatibility problems, necessitating a generic framework for seamless integration with SaaS providers.

Innovation Solution

The CloudStreams framework provides a service bus-like integration server with a CloudStreams engine for connection management, native service invocation, custom security policy enforcement, and real-time monitoring, using metadata handlers and connection factory instances to create connector services that interact with cloud applications, enabling transparent access and customization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a generic integration framework is used to integrate on-premises applications with SaaS applications, then integration time and complexity are reduced, but security concerns and data governance issues arise

Engineering Contradiction:
Improveintegration speedVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces an integration framework that acts as an intermediary layer between on-premises applications and SaaS applications. This framework includes connection factory instances, metadata handlers, and connector services that mediate all interactions, ensuring security policies are enforced while enabling rapid integration. The framework provides WS-Security support and custom security policy enforcement capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration framework is segmented into distinct modular components including connection factory instances, metadata handlers, connector descriptors, and virtual services. Each component has a specific function and can be independently configured and managed. This segmentation allows for granular security control and easier maintenance while accelerating integration processes.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If cloud applications are integrated with on-premises applications, then access to cloud services is enabled, but latency and compatibility problems occur

Engineering Contradiction:
Improvecloud service accessVSAvoidlatency
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The framework performs preliminary actions by pre-configuring connection factory instances with transport layer details and pre-defining metadata handlers for different cloud providers. Connector descriptors are generated in advance to define service operations. This preliminary setup reduces runtime latency and ensures compatibility before actual cloud service interactions occur.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If a service bus-like integration server is used with connection management capabilities, then connection efficiency is improved, but system complexity increases

Engineering Contradiction:
Improveconnection efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The integration framework implements a universal connection management system that can handle multiple cloud providers and service types through a single unified interface. The connection factory instances and metadata handlers are designed to be provider-agnostic, supporting various transport protocols and data models. This universality improves connection efficiency across different cloud services while maintaining manageable system complexity through standardization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9100345B2Systems and/or methods for supporting a generic framework for integration of on-premises and SaaS applications with security, service mediation, administrative, and/or monitoring capabilities
Publication Date: 2015.08.04 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9100345B2 patent drawing
  • US9100345B2 patent drawing
  • US9100345B2 patent drawing

AI summary

Certain example embodiments provide a generic integration framework for connecting on-premises applications with software as a service (SaaS) applications, and/or for integrating the same. The framework of certain example embodiments involves a layered approach (including a Connector Development Kit, connection factory, metadata handlers, and connector services) that helps to, among other things, allow customization of applications in multi-tenant architectures. Design-time wizards help create runtime artifacts and, during runtime, the connector service helps serve as an intermediary between the on-premises application and the cloud service, thereby hiding the complexity of the specific cloud providers. Certain example embodiments advantageously provide a generic and well-integrated solution for connecting an on-premises application to a cloud service in connection with existing containers.