System and method for providing a service management engine for use with a cloud computing environment
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.
1. A system for providing a service management engine for use with a cloud computing environment, comprising:
one or more computers including a cloud environment executing thereon;
a platform component that is provided within the cloud environment, and that supports self-service provisioning for enterprise applications;
a plurality of service management engines, in communication with an orchestration engine, which are used to provision services as service types, including one or more provisioning, lifecycle management, and monitoring of the service types, wherein each particular service type is associated with a particular service management engine that handles lifecycle management and monitoring for the particular service type;
wherein the system determines a plurality of service types to be provisioned for use within the cloud environment, and configures a plurality of corresponding service management engines within the platform component to support the plurality of service types; and
wherein a service management engine is 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 associated with the service definition package, and wherein registered service management engines then provision the service types within the platform domain.
2. The system of claim 1 , wherein each of the one or more service management engines are used to parse a service definition package, and to provision services as one or more different service types, according to contents of the service definition package.
3. The system of claim 1 , wherein the platform component enables service types to be instantiated by the one or more service management engines, as provider service management engines, according to a configuration of the platform component itself.
4. The system of claim 1 , wherein the 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 1 , wherein for each service type, the orchestration engine calls the service management engine associated with the service type to determine one or more database or provider dependencies for the service management engine.
6. The system of claim 1 , further comprising a plurality of provider types that represent resources managed by provider types, wherein when creating a service, the orchestration engine:
matches requirements of a desired service type with capabilities of the provider types;
requests a service type to create an instance of a service;
requests the provider types to create instances of providers; and
associates the service with the providers.
7. A method of providing a service management engine for use with a cloud computing environment, comprising:
providing one or more computers including a cloud environment executing thereon;
providing a platform component within the cloud environment, that supports self-service provisioning for enterprise applications;
providing a plurality of service management engines, in communication with an orchestration engine, which are used to provision services as service types, including one or more provisioning, lifecycle management, and monitoring of the service types, wherein each particular service type is associated with a particular service management engine that handles lifecycle management and monitoring for the particular service type; and
determining a plurality of service types to be provisioned for use within the cloud environment, and configuring corresponding a plurality of service management engines within the platform component to support the plurality of service types;
wherein a service management engine is 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 associated with the service definition package, and wherein registered service management engines then provision the service types within the platform domain.
8. The method of claim 7 , wherein each of the one or more service management engines are used to parse a service definition package, and to provision services as one or more different service types, according to contents of the service definition package.
9. The method of claim 7 , wherein the platform component enables service types to be instantiated by the one or more service management engines, as provider service management engines, according to a configuration of the platform component itself.
10. The method of claim 7 , wherein the 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.
11. The method of claim 7 , wherein for each service type, the orchestration engine calls the service management engine associated with the service type to determine one or more database or provider dependencies for the service management engine.
12. The method of claim 7 , further comprising a plurality of provider types that represent resources managed by provider types, wherein when creating a service, the orchestration engine:
matches requirements of a desired service type with capabilities of the provider types;
requests a service type to create an instance of a service;
requests the provider types to create instances of providers; and
associates the service with the providers.
13. A non-transitory computer readable medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:
providing, at one or more computers including a cloud environment executing thereon, a platform component within the cloud environment, that supports self-service provisioning for enterprise applications;
providing a plurality of service management engines, in communication with an orchestration engine, which are used to provision services as service types, including one or more provisioning, lifecycle management, and monitoring of the service types, wherein each particular service type is associated with a particular service management engine that handles lifecycle management and monitoring for the particular service type; and
determining a plurality of service types to be provisioned for use within the cloud environment, and configuring a plurality of corresponding service management engines within the platform component to support the plurality of service types;
wherein a service management engine is 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 associated with the service definition package, and wherein registered service management engines then provision the service types within the platform domain.
14. The non-transitory computer readable medium of claim 13 , wherein each of the one or more service management engines are used to parse a service definition package, and to provision services as one or more different service types, according to contents of the service definition package.
15. The non-transitory computer readable medium of claim 13 , wherein the platform component enables service types to be instantiated by the one or more service management engines, as provider service management engines, according to a configuration of the platform component itself.
16. The non-transitory computer readable medium of claim 13 , wherein the 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.
17. The non-transitory computer readable medium of claim 13 , wherein for each service type, the orchestration engine calls the service management engine associated with the service type to determine one or more database or provider dependencies for the service management engine.