SYSTEMS AND METHODS FOR DEPLOYING LEGACY SOFTWARE IN THE CLOUD

• US 20150215376A1
• Filed: 01/24/2014
• Published: 07/30/2015
• Est. Priority Date: 01/24/2014
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Kranz, Kenneth James, Curran, George
• Granted Patent: US 9,661,064 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04N 21/4431 characterized by the use of Application Program Interface [API] libraries

Abstract

A system, method, apparatus and computer program product is described to provide a plurality of connectors, the connectors configured to support one or more applications in at least one configuration selected from a group of configurations including: i) a non-tenant, and non-tenant aware, application, ii) a non-tenant, but tenant aware, application, iii) a many tenant application, iv) a multi-tenant application, and v) a native multi-tenant application. Also provided are one or more application programming interfaces (APIs) to the connectors, the one or more APIs providing a substantially uniform interface to applications supported by the connectors. In one embodiment, a governance layer provides the APIs, and the governance layer communicates with the connectors, so that an application'"'"'s tenancy support is obfuscated.

Claims

1. A system comprising:

a) one or more computer systems executing two or more applications that each support one or more tenants on the computer systems, wherein at least two different ones of applications are selected from the group;

i) a non-tenant, and non-tenant aware, application, ii) a non-tenant, but tenant aware, application, iii) a many tenant application, and iv) a multi-tenant application;

a) at least two connectors configured to support respective ones of the at least two applications, wherein the respective connectors provide application programming interfaces (APIs) for each respective one of the at least two applications, and further wherein the APIs are substantially uniform with respect to one another; and

b) wherein the connectors comprise one or more computer programs executing on the computer systems.

2. A system according to claim 1 further including one or more computer programs executing on the computer systems to provide a governance layer to communicate with the connectors through the APIs.

3. A system according to claim 2 wherein the tenancy support of the two or more applications is obfuscated.

4. A system according to claim 1 further wherein at least one of the at least two applications is a native multi-tenant application, and wherein at least one other of the at least two applications is not a native multi-tenant application.

5. A system according to claim 1 further wherein the APIs for the at least two applications include a notification service and create, retrieve, update and delete database functions.

6. A system according to claim 1 further wherein each of the tenants supported by the two or more applications has a tenant ID.

7. A system according to claim 1 further including a tenancy broker map that is accessible by the one or more computer systems and stores the tenant ID for the tenants.

8. A system comprising:

a) one or more computer systems executing two or more applications that each support one or more tenants on the computer systems, wherein at least one of the applications is a non-native single tenant application and the other one of the applications is a non-native multi-tenant application;

b) at least two connectors configured to support respective ones of the at least two applications, wherein the respective connectors provide application programming interfaces (APIs) for each respective one of the at least two applications, and further wherein the APIs are substantially uniform with respect to one another; and

c) wherein the connectors comprise one or more computer programs executing on the computer systems.

9. A system according to claim 8 further including one or more computer programs executing on the computer systems to provide a governance layer to communicate with the connectors through the APIs.

10. A system according to claim 8 wherein the tenancy support of the two or more applications is obfuscated.

11. A system according to claim 8 further including a native multi-tenant application that operates on the one or more computer systems using its native API.

12. A system according to claim 8 further wherein the APIs for the at least two non-native tenant applications include a notification service and create, retrieve, update and delete database functions.

13. A system according to claim 8 further wherein each of the tenants has a tenant ID.

14. A system according to claim 13 further including a tenancy broker map that is accessible by the one or more computer systems and stores the tenant ID for the tenants.

15. A computer program product comprising one or more computer programs stored on a non-transitory storage medium, the one or more computer programs operable when executed on one or more computer systems to provide one or more instances of any of the following:

i) first API to a first type of connector, the first type of connector configured to deploy a first type of non-native application in a cloud environment, wherein the first type of application is a single tenant, tenant-aware application;

ii) a second API to a second type of connector, the second type of connector configured to deploy a second type of non-native application in a cloud environment, wherein the second type of application is a many-tenant, tenant-aware application;

iii) a third API to a third type of connector, the third type of connector configured to deploy a third type of non-native application in a cloud environment, wherein the third type of application is a multi-tenant, tenant-aware application; and

the first, second and third APIs all substantially uniform with respect to one another.

16. A computer-implemented method comprising:

a) storing one or more computer programs on a non-transitory storage medium, the one or more computer programs operable when executed on one or more computing systems to provide;

i) a first connector configured to deploy a first type of non-native application in a cloud environment, wherein the first type of application is a single tenant, tenant-aware application;

ii) a second connector configured to deploy a second type of non-native application in a cloud environment, wherein the second type of application is a many-tenant, tenant-aware application;

iii) a third connector configured to deploy a third type of non-native application in a cloud environment, wherein the third type of application is a multi-tenant, tenant-aware application;

iv) the first, second and third connectors each having a substantially uniform application programming interface (API) with respect to one another;

b) installing a non-native application on a computer system in a cloud environment including;

i) determining the type of the non-native application to be deployed;

ii) based on the type, choosing a connector selected from the group of the first, second and third connectors;

iii) installing an instance of the chosen connector on the computer system; and

iv) installing the non-native application on the computer system so that it is accessed through the substantially uniform API for the instance of the chosen connector.

17. A computer-implemented method according to claim 16 further wherein the first, second and third API'"'"'s are substantially uniform so that substantially the same interface is used across a variety of non-native applications deployed in a cloud environment.

18. A computer-implemented method according to claim 17 further including installing one or more computer programs to provide a governance layer to interact with the API.

19. A computer-implemented method according to claim 18 wherein the governance layer communicates with the connectors, and wherein an application'"'"'s tenancy support is obfuscated.

20. A computer-implemented method according to claim 16 wherein for a particular one of the substantially uniform API'"'"'s there is provided two or more different connectors, each different connector providing an interface between the substantially uniform API and a particular different application of the type supported by the respective type of API.