System and method for behavior injection in cloud computing platforms or applications

Patent metadata

Field	Value
Publication number	US-11880694-B2
Application number	US-202016883717-A
Country	US
Kind code	B2
Filing date	May 26, 2020
Priority date	May 26, 2020
Publication date	Jan 23, 2024
Grant date	Jan 23, 2024

Abstract

In accordance with an embodiment, described herein is a system and method for behavior injection in a cloud computing platform (cloud platform) or software application, including the use of injection points to modify the operation or behavior of a tenant platform environment. An injection service enables a cloud platform provider to configure software code/behaviors to be injected into cloud platform modules or other components associated with tenants, including mapping, for a tenant-specific globally unique identifier (GUID) associated with a lifecycle activity injection point, a behavior including a platform code or process and metadata that can be used to inject and modify operation of a corresponding module. The described approach enables a cloud platform to expose behavioral aspects of the cloud platform or a software application executing therein, so that they can be controlled or modified in a dynamic manner, from outside of the cloud platform.

First claim

What is claimed is:

1. A system for behavior injection in a cloud computing environment having a cloud platform or software application executing therein, comprising:
a computer including one or more processors;
an injection service operating on the computer, that enables configuration of software code or behaviors to be injected into modules at the cloud platform associated with tenants of the cloud computing platform;
wherein the injection service provides a mapping, for each of a plurality of globally unique identifiers (GUID) associated with lifecycle activity injection points, a platform code or process and metadata that can be used to inject and modify operation of a corresponding module, the metadata being maintained by the injection service, each GUID being associated with a tenant and referencing a unique lifecycle injection point associated with a respective tenant; and
wherein at the cloud platform, a received platform code or process and metadata are used to modify the operation of a requesting module within a particular tenant platform environment associated with a tenant of the tenants of the cloud computing platform,
wherein each of the tenants of the cloud computing platform are associated with one or more tenant platform environments provided by the cloud platform, the received platform code or process and metadata being received based on a request comprising a GUID from the requesting module to the injection service, the GUID of the request being associated with the tenant and referencing a unique lifecycle injection point associated with the tenant, the cloud platform utilizing the received metadata to determine a process by which to modify the operation of the requesting module within the particular tenant platform environment.

2. The system of claim 1 , wherein at the requesting module, one or more injection points associated with lifecycle activities for a particular tenant platform are used to check for behaviors to be injected, by communicating one or more requests to the injection service using one or more tenant-specific GUIDs.

3. The system of claim 1 , wherein the injection service determines availability of behaviors matching tenant-specific GUID(s) received in association with requests from the request module, and returns a corresponding platform code or process and metadata for execution by the requesting module.

4. The system of claim 1 , wherein the injection service is provided as a RESTful web service or other service hosted outside of the cloud platform, and a change of behavior of a module and/or activity within the platform can be performed from outside of the cloud platform via calls to the service.

5. The system of claim 1 , wherein the cloud platform exposes behavioral aspects of the cloud platform or a software application executing therein, said exposing of behavior aspects providing for control or modification thereof in a dynamic manner, from outside of the cloud platform.

6. The system of claim 1 , wherein the cloud platform orchestrates use by the tenant platform environment, or by software applications executing therein, of various lifecycle activities provided within cloud platform as modules (components) as part of a tenant lifecycle associated with those modules.

7. The system of claim 1 , wherein a tenant-specific GUID can be used to indicate the association of one or more (or all) tenants, with one or more module injection points, for purposes of requesting and receiving platform codes or processes from the injection service.

8. A method for behavior injection in a cloud computing environment having a cloud platform or software application executing therein, comprising:
providing a computer including one or more processors;
providing an injection service operating on the computer, the injection service enabling configuration of software code or behaviors to be injected into modules at the cloud platform associated with tenants of the cloud computing platform;
providing, by the injection service, a mapping for each of a plurality of globally unique identifiers (GUID) associated with lifecycle activity injection points, a platform code or process, and metadata that can be used to inject and modify operation of a corresponding module, the metadata being maintained by the injection service, each GUID being associated with a tenant and referencing a unique lifecycle injection point associated with a respective tenant; and
wherein at the cloud platform, a received platform code or process and metadata are used to modify the operation of a requesting module within a particular tenant platform environment associated with a tenant of the tenants of the cloud computing platform,
wherein each of the tenants of the cloud computing platform are associated with one or more tenant platform environments provided by the cloud platform, the received platform code or process and metadata being received based on a request comprising a GUID from the requesting module to the injection service, the GUID of the request being associated with the tenant and referencing a unique lifecycle injection point associated with the tenant, the cloud platform utilizing the received metadata to determine a process by which to modify the operation of the requesting module within the particular tenant platform environment.

9. The method of claim 8 , wherein at the requesting module, one or more injection points associated with lifecycle activities for a particular tenant platform are used to check for behaviors to be injected, by communicating one or more requests to the injection service using one or more tenant-specific GUIDs.

10. The method of claim 8 , wherein the injection service determines availability of behaviors matching tenant-specific GUID(s) received in association with requests from the request module, and returns a corresponding platform code or process and metadata for execution by the requesting module.

11. The method of claim 8 , wherein the injection service is provided as a RESTful web service or other service hosted outside of the cloud platform, and the change of behavior of a module and/or activity within the platform can be performed from outside of the cloud platform via calls to the service.

12. The method of claim 8 , wherein the cloud platform exposes behavioral aspects of the cloud platform or a software application executing therein, said exposing of behavior aspects providing for control or modification thereof in a dynamic manner, from outside of the cloud platform.

13. The method of claim 8 , wherein the cloud platform orchestrates use by the tenant platform environment, or by software applications executing therein, of various lifecycle activities provided within cloud platform as modules (components) as part of a tenant lifecycle associated with those modules.

14. The method of claim 8 , wherein a tenant-specific GUID can be used to indicate the association of one or more (or all) tenants, with one or more module injection points, for purposes of requesting and receiving platform codes or processes from the injection service.

15. A non-transitory computer readable storage medium having instructions thereon, which when read and executed by a computer including one or more processors cause the computer to perform a method comprising:
providing the computer including the one or more processors;
providing an injection service operating on the computer, the injection service enabling configuration of software code or behaviors to be injected into modules at the cloud platform associated with tenants of the cloud computing platform;
providing, by the injection service, a mapping

Assignees

• Oracle Int Corp

Inventors

• Devta Prakash Kumar
• Pant Dinesh Chandra
• Misra Srimant

Classifications

• G06F9/44521 Primary

  Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading · CPC title

• G06F9/5072

  Grid computing · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• H04L67/125

  involving control of end-device applications over a network · CPC title

• G06F9/44526 Primary

  Plug-ins; Add-ons · CPC title