System and method for providing configuration modularity in an application server, cloud platform, or other environment

• US 9,898,344 B2
• Filed: 09/03/2014
• Issued: 02/20/2018
• Est. Priority Date: 09/20/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kalali, Masoud
• Primary Examiner(s): Lee, Bryan
• Assistant Examiner(s): GIDADO, OLUWATOSIN M
• Application Number:
  US14/476,583
• Publication Number:
  US 20150089031A1
• Time in Patent Office: 1,266 Days
• Field of Search: 709220
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

In accordance with an embodiment, described herein is a system and method for providing configuration modularity in an application server, cloud platform, or other environment. For example, in a cloud computing environment, application server modules, e.g., WebLogic Server or GlassFish modules, can be embedded within the environment to provide various cloud platform functionalities. In accordance with an embodiment, the system comprises a configuration modularity logic for use in determining, for a particular application or service deployment, a configuration of application, module or service components, including determining if a configuration is provided by a global or domain configuration, determining if annotations are provided by the particular application or service deployment for use in configuring the application, module or service components, and/or determining if a default configuration is provided for use with the particular application or service deployment.

Claims

1. A system for providing configuration modularity in an application server, cloud platform, or other environment, comprising:

one or more computers including an application server or cloud environment executing thereon that supports provisioning of enterprise applications as services; and

a configuration modularity logic for use in determining, upon receiving a request for a particular application or service deployment, a configuration of each application, module or service component of the particular application or service deployment, including

determining whether a configuration is provided by a global or domain configuration,

using, if provided by the global or domain configuration, the configuration to configure a config bean for each of the application, module or service components,

determining, if the configuration for a config bean for one or more of the application, module or service components is not provided by the global or domain configuration, whether annotations are provided by the particular application or service deployment for use in configuring the config bean for the one or more of the application, module or service components,

using, if provided by the particular application or service deployment, the annotations to configure the config bean for use by the one or more of the application, module or service components,

determining, if the configuration for a config bean for one or more of the application, module or service components is not provided by the global or domain configuration and the annotations are not provided by the particular application or service configuration for use in configuring the config bean for the one or more of the application, module or service deployments, whether a default configuration is provided for use with the particular application or service deployment in configuring the config bean for the one or more of the application, module or service components, and

using the default configuration to configure the config bean for the one or more of the application, module or service components.

2. The system of claim 1, wherein the application server or cloud environment includes one or more modules associated with a configuration file that provides configuration data for those modules and that is used by the configuration modularity logic to configure the modules for use within the application server or cloud environment.

3. The system of claim 1, wherein the system includes the application server, and wherein the system uses the configuration modularity logic to configure config beans for use by applications or modules deployed within the application server environment.

4. The system of claim 1, wherein the system includes the cloud environment, and wherein the system uses the configuration modularity logic to configure service definition packages for use by services deployed within the cloud environment.

13. The system of claim 1, wherein the configuration modularity logic is invoked by intercepting a call to access a config bean for each of the application, module or service components.

14. The system of claim 1, wherein determining a configuration of each application, module or service component of the particular application or service deployment includes populating placeholders in an object graph of the config bean for each of the application, module or service components with appropriate configuration information.

15. The system of claim 4, further comprising:

a service management engine for

deploying an instance of the particular application or service deployment using the configured service definition package,

provisioning the instance of the particular application or service deployment, and

managing a lifecycle of the instance of the particular application or service deployment;

wherein, upon receiving an instruction to deploy the instance of the particular application or service, the service management engine determines a config context and applies the configuration modularity logic to the deployed the instance of the particular application or service.

5. A method of providing configuration modularity in an application server, cloud platform, or other environment, comprising:

providing, at one or more computers including an application server or cloud environment executing thereon that supports provisioning of enterprise applications as services, a configuration modularity logic; and

determining, by the configuration modularity logic upon receiving a request for a particular application or service deployment, a configuration of each application, module or service component of the particular application or service deployment, including

determining whether a configuration is provided by a global or domain configuration, using, if provided by the global or domain configuration, the configuration to configure a config bean for each of the application, module or service components,

determining, if the configuration for a config bean for one or more of the application, module or service components is not provided by the global or domain configuration, whether annotations are provided by the particular application or service deployment for use in configuring the config bean for the one or more of the application, module or service components,

using, if provided by the particular application or service deployment, the annotations to configure the config bean for the one or more of the application, module or service components,

determining, if the configuration for a config bean for one or more of the application, module or service components is not provided by the global or domain configuration and the annotations are not provided by the particular application or service configuration for use in configuring the config bean for the one or more of the application, module or service deployments, whether a default configuration is provided for use with the particular application or service deployment in configuring the config bean for the one or more of the application, module or service components, and

using the default configuration to configure the config bean for the one or more of the application, module or service components.

6. The method of claim 5, wherein the application server or cloud environment includes one or more modules associated with a configuration file that provides configuration data for those modules and that is used by the configuration modularity logic to configure the modules for use within the application server or cloud environment.

7. The method of claim 5, wherein the method is performed with the application server, including using the configuration modularity logic to configure config beans for use by applications or modules deployed within the application server environment.

8. The method of claim 5, wherein the method is performed with the cloud environment, including using the configuration modularity logic to configure service definition packages for use by services deployed within the cloud environment.

16. The method of claim 5, wherein the configuration modularity logic is invoked by intercepting a call to access a config bean for each of the application, module or service components.

17. The method of claim 5, wherein determining a configuration of each application, module or service component of the particular application or service deployment includes populating placeholders in an object graph of the config bean for each of the application, module or service components with appropriate configuration information.

18. The method of claim 8, further comprising:

providing a service management engine for

deploying an instance of the particular application or service deployment using the configured service definition package,

provisioning the instance of the particular application or service deployment, and

managing a lifecycle of the instance of the particular application or service deployment;

wherein, upon receiving an instruction to deploy the instance of the particular application or service, the service management engine determines a config context and applies the configuration modularity logic to the deployed the instance of the particular application or service.

9. 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 the method comprising:

providing, at one or more computers including an application server or cloud environment executing thereon that supports provisioning of enterprise applications as services, a configuration modularity logic; and

determining, by the configuration modularity logic upon receiving a request for a particular application or service deployment, a configuration of each application, module or service component of the particular application or service deployment, including

determining whether a configuration is provided by a global or domain configuration,

using, if provided by the global or domain configuration, the configuration to configure a config bean for each of the application, module or service components,

determining, if the configuration for a config bean for one or more of the application, module or service components is not provided by the global or domain configuration, whether annotations are provided by the particular application or service deployment for use in configuring the config bean for the one or more of the application, module or service components,

using, if provided by the particular application or service deployment, the annotations to configure the config bean for the one or more of the application, module or service components,

determining, if the configuration for a config bean for one or more of the application, module or service components is not provided by the global or domain configuration and the annotations are not provided by the particular application or service configuration for use in configuring the config bean for the one or more of the application, module or service deployments, whether a default configuration is provided for use with the particular application or service deployment in configuring the config bean for the one or more of the application, module or service components, and

using the default configuration to configure the config bean for the one or more of the application, module or service components.

10. The non-transitory computer readable storage medium of claim 9, wherein the application server or cloud environment includes one or more modules associated with a configuration file that provides configuration data for those modules and that is used by the configuration modularity logic to configure the modules for use within the application server or cloud environment.

11. The non-transitory computer readable storage medium of claim 9, wherein the method is performed with the application server, including using the configuration modularity logic to configure config beans for use by applications or modules deployed within the application server environment.

12. The non-transitory computer readable storage medium of claim 9, wherein the method is performed with the cloud environment, including using the configuration modularity logic to configure service definition packages for use by services deployed within the cloud environment.

19. The non-transitory computer readable storage medium of claim 9, wherein the configuration modularity logic is invoked by intercepting a call to access a config bean for each of the application, module or service components.

20. The non-transitory computer readable storage medium of claim 9, wherein determining a configuration of each application, module or service component of the particular application or service deployment includes populating placeholders in an object graph of the config bean for each of the application, module or service components with appropriate configuration information.