Software defined SaaS platform

• US 9,836,332 B2
• Filed: 07/31/2015
• Issued: 12/05/2017
• Est. Priority Date: 07/31/2014
• Status: Active Grant

• Current Assignee: Corent Technology, Inc.
• Original Assignee: Corent Technology, Inc.
• Inventors: Syed, Shafiullah, Fatehi, Feyzi, Venkataraman, Sethuraman, Prabhu, Jeya Anantha
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Nguyen, Mongbao
• Application Number:
  US14/815,323
• Publication Number:
  US 20160034277A1
• Time in Patent Office: 858 Days
• CPC Class Codes: G06F 2209/542 Intercept
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A system that transforms non-SaaS (non Software as a Service) applications into tenant-aware SaaS (Software as a Service) applications is disclosed, which analyzes the non SaaS applications to determine which intercepts to external libraries need to be translated into SaaS intercepts that utilize SaaS tenancy services, SaaS operations services, and/or SaaS business services. The system transforms the non-SaaS applications into SaaS applications by providing intercept handlers that call SaaS services on demand when the transformed SaaS application throws a transformed SaaS interrupt.

Claims

1. A SaaS (Software as a Service) system for transforming software applications, comprising a non-transitory computer-readable medium storing instructions that, when executed by a computer processor, cause the computer processor to perform the steps of:

identifying non-SaaS application intercepts of a non-SaaS application capable of being transformed into SaaS intercepts by locating non-SaaS application intercepts within a SaaS transformation database containing transformable non-SaaS application intercepts;

transforming a portion of the non-SaaS application intercepts into SaaS intercepts by;

(a) adding, to the non-SaaS application, API (Application Program Interface) calls to tenancy services to generate a transformed SaaS application linked to a tenancy and user identity manager via the added API calls to tenancy services, wherein the added API calls to tenancy services comprise SaaS intercepts from the SaaS transformation database, and

(b) installing an interception pattern handler functionally connected to the generated transformed SaaS application, wherein the interception pattern handler is configured to;

(1) catch calls initiated from a call site,

(2) determine whether a caught call is a non-SaaS application intercept, or a SaaS application intercept, and

(3) route SaaS application intercepts to a SaaS runtime engine and non-SaaS application intercepts to an external system;

determining a tenancy identity associated with an instance of the transformed SaaS application, wherein each instance is dedicated towards a separate tenant identified by the tenancy identity; and

triggering at least one SaaS service associated with the tenancy identity when the instance of the transformed SaaS application triggers at least one of the SaaS intercepts from the SaaS transformation database.

2. The SaaS system of claim 1 wherein the at least one SaaS service comprises a cloud environment service.

3. The SaaS system of claim 1 wherein the at least one service is selected from the group consisting of a tenancy service, an operations service, and a business service.

4. The SaaS system of claim 1 wherein the step of transforming the portion of the non-SaaS application intercepts into SaaS intercepts adds a SaaS intercept to the transformed SaaS application for each identified non-SaaS application intercept.

5. The SaaS system of claim 1, wherein the interception pattern handler routes SaaS application intercepts to the runtime engine by utilizing an interception API handler.

6. The SaaS system of claim 1, wherein the non-transitory computer-readable medium further stores instructions that, when executed by the computer processor, cause the computer processor to track a tenancy identity of an application instance using a user identity manager.

7. The SaaS system of claim 6, wherein the tenancy and the user identity manager provide the tenancy identity to a tenancy services engine to trigger the at least one SaaS service as a function of the tenancy identity.