IP Library › Granted Patent US 11,374,833
Granted Patent B2
US 11,374,833 · App. 16/162,689 · Granted Jun 28, 2022

System and method for providing a service management engine for use with a cloud computing environment

Inventors: Rajiv Mordani (Sunnyvale, CA); Abhijit Kumar (Cupertino, CA); Bhavanishankara Sapaliga (Bangalore, IN); Sivakumar Thyagarajan (Bangalore, IN); Nazrul Islam (Santa Clara, CA)
Assignee: ORACLE INTERNATIONAL CORPORATION
H04L41/5058G06F9/5072
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,374,833
App. No.
16/162,689
Granted
Jun 28, 2022
Kind
B2
Abstract

A system and method for providing a service management engine for use with a cloud computing environment. In accordance with an embodiment, enterprise software applications (e.g., Fusion Middleware applications) can be instantiated as services within a cloud platform, where they are then made accessible by other (e.g., customer) applications. In an embodiment, a service management engine (SME), in communication with an orchestration engine, can be used to provision services as one or more different service types, according to a service definition package (SDP). Service types can be instantiated according to the configuration of the cloud platform itself, and the contents of the SDP, including discovering, provisioning, and associating service types with system resources, to address different customer requirements.

Claims (51)

1. A system for providing services in a cloud computing environment, comprising:

one or more computers including a processor, and a cloud environment executing thereon;

a platform component that enables provisioning of services to be provided as enterprise applications within the cloud environment;

a plurality of service management engines that provision the services as a plurality of service types, including lifecycle management and monitoring of the service types,

wherein each particular service type within the plurality of service types maps to a corresponding service management engine within the plurality of service management engines, that handles lifecycle management and monitoring for the particular service type, and

wherein each particular service management engine, of the plurality of service management engines, is usable to provision service instances of its corresponding particular service type; and

wherein, in creating a service runtime, the platform component:

determines one or more of the service types to be provisioned as part of the service runtime, within the cloud environment, and

configures one or more of the service management engines corresponding to the one or more of the service types, to provision the one or more of the service types as part of the service runtime.

2. The system of claim 1 , wherein each service management engine, of the plurality of service management engines, parses a service definition package associated with a service type, and provisions services according to a definition provided by the service definition package.

3. The system of claim 1 , wherein the platform component enables the service types to be instantiated, by one or more service management engines, as provider service management engines.

4. The system of claim 3 , wherein an orchestration engine calls service management engines associated with the service types, and performs pre-provisioning associations between the service management engines and one or more provider service management engines.

5. The system of claim 4 , wherein, for the particular service type, the orchestration engine calls the service management engine associated with the particular service type to determine one or more database or other provider dependencies for the service management engine.

6. The system of claim 1 , wherein a service type to be provided by the platform component, for use in creating service runtimes, is created upon parsing of a service definition package associated with the service type to be provided, wherein one or more service management engines that are bundled in the service definition package are registered with the platform component.

7. The system of claim 1 , wherein the system includes a plurality of service definition packages;

wherein each service definition package, of the plurality of service definition packages, includes a binary component and a metadata component that define one or more service types that are provided by the service definition package and which can be provisioned by the system in response to a request;

wherein a service type is created based on a selection of a particular service definition package and a configuration information specific to an installation of the platform component; and

wherein, in response to a request from a user, the orchestration engine operates to:

determine the particular service type to be used for provisioning a service within the cloud environment; and

invoke the service management engine that maps to the particular service type to parse the particular service definition package from which the service type is created, and provision the service as the service type according to the contents of the particular service definition package.

8. The system of claim 1 , wherein a service management engine is dynamically incorporated into a platform domain by installing an associated service definition package, wherein a service definition package manager handles installation and registration of service management engines bundled in service definition packages, and wherein a set of registered service management engines then provide the service types that are available to create services within the platform domain.

9. The system of claim 1 , further comprising a plurality of provider types that represents use of resources managed by the provider types, wherein when creating a service, the orchestration engine:

matches requirements of a desired service type with capabilities of configured provider types;

requests a service type to create an instance of a service;

requests provider types to create instances of providers for use by the instance of the service; and

associates the service with the providers.

10. A method of providing a services in a cloud computing environment, comprising:

providing, at one or more computers including a processor, and a cloud environment executing thereon, a platform component that enables provisioning of services to be provided as enterprise applications within the cloud environment;

providing a plurality of service management engines that provision the services as a plurality of service types, including lifecycle management and monitoring of the service types,

wherein each particular service type within the plurality of service types maps to a corresponding service management engine within the plurality of service management engines, that handles lifecycle management and monitoring for the particular service type, and

wherein each particular service management engine, of the plurality of service management engines, is usable to provision service instances of its corresponding particular service type; and

wherein, in creating a service runtime, the platform component:

determines one or more of the service types to be provisioned as part of the service runtime, within the cloud environment, and

configures one or more of the service management engines corresponding to the one or more of the service types, to provision the one or more of the service types as part of the service runtime.

11. The method of claim 10 , wherein each service management engine, of the plurality of service management engines, parses a service definition package associated with a service type, and provisions services according to a definition provided by the service definition package.

12. The method of claim 10 , wherein the platform component enables the service types to be instantiated, by one or more service management engines, as provider service management engines.

13. The method of claim 12 , wherein an orchestration engine calls service management engines associated with the service types, and performs pre-provisioning associations between the service management engines and one or more provider service management engines.

14. The method of claim 13 , wherein, for the particular service type, the orchestration engine calls the service management engine associated with the particular service type to determine one or more database or other provider dependencies for the service management engine.

15. The method of claim 10 , wherein a service type to be provided by the platform component, for use in creating service runtimes, is created upon parsing of a service definition package associated with the service type to be provided, wherein one or more service management engines that are bundled in the service definition package are registered with the platform component.

16. A non-transitory computer readable storage medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform a method comprising:

providing, at one or more computers including a processor, and a cloud environment executing thereon, a platform component that enables provisioning of services to be provided as enterprise applications within the cloud environment;

providing a plurality of service management engines that provision the services as a plurality of service types, including lifecycle management and monitoring of the service types,

wherein each particular service type within the plurality of service types maps to a corresponding service management engine within the plurality of service management engines, that handles lifecycle management and monitoring for the particular service type, and

wherein each particular service management engine, of the plurality of service management engines, is usable to provision service instances of its corresponding particular service type; and

wherein, in creating a service runtime, the platform component:

determines one or more of the service types to be provisioned as part of the service runtime, within the cloud environment, and

configures one or more of the service management engines corresponding to the one or more of the service types, to provision the one or more of the service types as part of the service runtime.

17. The non-transitory computer readable storage medium of claim 16 , wherein each service management engine, of the plurality of service management engines, parses a service definition package associated with a service type, and provisions services according to a definition provided by the service definition package.

18. The non-transitory computer readable storage medium of claim 16 , wherein the platform component enables the service types to be instantiated, by one or more service management engines, as provider service management engines.

19. The non-transitory computer readable storage medium of claim 18 , wherein an orchestration engine calls service management engines associated with the service types, and performs pre-provisioning associations between the service management engines and one or more provider service management engines.

20. The non-transitory computer readable storage medium of claim 19 , wherein, for the particular service type, the orchestration engine calls the service management engine associated with the particular service type to determine one or more database or other provider dependencies for the service management engine.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2018
From: MORDANI, RAJIV; KUMAR, ABHIJIT; SAPALIGA, BHAVANISHANKARA; THYAGARAJAN, SIVAKUMAR; ISLAM, NAZRUL
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 047310/0027 →
Continuity (6)
Continuation 13970403 · Aug 19, 2013
Provisional Application 61799126 · Mar 15, 2013
Provisional Application 61698467 · Sep 7, 2012
Provisional Application 61748658 · Jan 3, 2013
Provisional Application 61766819 · Feb 20, 2013
Related Publication 20190052550A1 · Feb 14, 2019
Cited By (1)
US 12,452,147