Managing data center orchestration using service plans and manifests
US-2024385850-A1 · Nov 21, 2024 · US
US9898344B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9898344-B2 |
| Application number | US-201414476583-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 3, 2014 |
| Priority date | Sep 20, 2013 |
| Publication date | Feb 20, 2018 |
| Grant date | Feb 20, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 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. 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. 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 th
Configuring for program initiating, e.g. using registry, configuration files · CPC title
Grid computing · CPC title
wherein the managed service relates to distributed or central networked applications · CPC title
Assignment of logical groups to network elements · CPC title
Software deployment · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.