Pluggable framework
US-10866787-B2 · Dec 15, 2020 · US
US11797285B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11797285-B2 |
| Application number | US-202117536784-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 29, 2021 |
| Priority date | Nov 29, 2021 |
| Publication date | Oct 24, 2023 |
| Grant date | Oct 24, 2023 |
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.
Techniques enable an application for execution in a heterogeneous computing environment including an on-premise server and a Software-as-a-Service (SaaS) provider. A scaffold defining assets usable by the application and configuration details therefor is developed. At least one scaffold map is generated. Each specifies target servers where individual assets are located and/or to be located. Different scaffold maps are generated for different user-specifiable environments to which the application is deployable. An application manager helps generate agent manifests based on the scaffold and one or more scaffold maps. The agent manifests are usable to configure respective target servers. A package manager helps provision the target servers based on the agent manifests. The provisioning includes distributing to corresponding target servers, and processing thereon, the agent manifests. The processing includes rolling back the distribution responsive to an occurrence of a defined exception case. The application is enabled following successful provisioning.
Opening claim text (preview).
What is claimed is: 1. A method of enabling an application for execution in a heterogeneous computing environment, the heterogeneous computing environment including different runtime environments distributed across at least one on-premise server and at least one Software-as-a-Service (SaaS) provider such that the at least one on-premise server is configured to provide at least one first service of the application and the at least one SaaS provider is configured to provide at least one second service of the application, the method comprising: developing a scaffold for the application, the scaffold defining a set of assets usable by the application as well as configuration details for the assets; generating at least one scaffold map, each scaffold map specifying target servers in the heterogeneous computing environment where individual assets in the set of assets are located or where individual assets in the set of assets are to be located, wherein different scaffold maps are generated for different user-specifiable environments to which the application is deployable; automatically and programmatically generating, via an application manager, agent manifests based on the scaffold and one or more of the at least one scaffold maps, the agent manifests being usable to configure respective target servers associated with the respective scaffold maps; automatically and programmatically provisioning, via a package manager, the target servers of heterogeneous computing environment based on the agent manifests, the provisioning including distributing to corresponding target servers, and processing thereon, the agent manifests, wherein the processing includes rolling back the distribution responsive to an occurrence of a defined exception case; and enabling the application following successful provisioning. 2. The method of claim 1 , wherein application manager instances and package manager instances are deployable to different runtimes on different target servers. 3. The method of claim 2 , wherein the application manager instances are configured to assist in local scaffold creation. 4. The method of claim 2 , wherein the package manager instances are configured to assist in processing local package deployments for the application. 5. The method of claim 2 , wherein the method is operable in first and second modes, the first mode employing the application manager and the package manger to centrally manage deployment and configuration of the application, the second mode employing the application manager instances and the package manager instances to locally manage deployment and configuration of the application independent of the Software-as-a-Service (SaaS) provider. 6. The method of claim 1 , wherein different packages are deployable to different target servers in the heterogeneous computing environment, each package having one of a plurality of different types, and further comprising enforcing rules defining where different packages can be deployed in the heterogeneous computing environment based on the types of the respective packages. 7. The method of claim 6 , wherein one of the types indicates that the package(s) associated therewith are open source. 8. The method of claim 1 , further comprising enabling sandboxing on a level more granular than an individual runtime. 9. The method of claim 8 , wherein the sandboxing is practiced for individual packages or individual assets. 10. The method of claim 8 , wherein the sandboxing is practiced for a given package based on whether the given package was provided by a public repository. 11. The method of claim 1 , further comprising running the method in one of first and second modes, the first mode enabling hot deployment across platforms at a level more granular than an individual runtime and the second mode enabling cold deployment across platforms at the level more granular than an individual runtime. 12. The method of claim 1 , wherein packages are distributable to multiple different runtimes with respective configurations appropriate for the different respective runtimes, rather than being deployed to a container. 13. The method of claim 1 , wherein the scaffold is developed based on user-specified information received via a user interface. 14. The method of claim 1 , wherein the scaffold includes data specifying a test harness, and further comprising, after the provisioning, automatically testing the application using the test harness. 15. The method of claim 1 , wherein each agent manifest is associated with one target server. 16. The method of claim 1 , wherein for a given target server, multiple agent manifests are generated provided that the given target server includes multiple different runtime platforms. 17. At least one non-transitory computer readable storage medium comprising code that, when executed by at least one processor, perform operations that enable an application to be executed in a heterogeneous computing environment, the heterogeneous computing environment including different runtime environments distributed across at least one on-premise server and at least one Software-as-a-Service (SaaS) provider such that the at least one on-premise server is configured to provide at least one first service of the application and the at least one SaaS provider is configured to provide at least one second service of the application, the operations comprising: developing a scaffold for the application, the scaffold defining a set of assets usable by the application as well as configuration details for the assets; generating at least one scaffold map, each scaffold map specifying target servers in the heterogeneous computing environment where individual assets in the set of assets are located or where individual assets in the set of assets are to be located, wherein different scaffold maps are generated for different user-specifiable environments to which the application is deployable; automatically and programmatically generating, via an application manager, agent manifests based on the scaffold and one or more of the at least one scaffold maps, the agent manifests being usable to configure respective target servers associated with the respective scaffold maps; automatically and programmatically provisioning, via a package manager, the target servers of heterogeneous computing environment based on the agent manifests, the provisioning including distributing to corresponding target servers, and processing thereon, the agent manifests, wherein the processing includes rolling back the distribution responsive to an occurrence of a defined exception case; and enabling the application following successful provisioning. 18. A system configured to enable an application to be executed in a heterogeneous computing environment, the heterogeneous computing environment including different runtime environments distributed across at least one on-premise server and at least one Software-as-a-Service (SaaS) provider such that the at least one on-premise server is configured to provide at least one first service of the application and the at least one SaaS provider is configured to provide at least one second service of the application, the system comprising: at least one processor and a memory coupled thereto, the at least one processor being configured to at least: present a user interface enabling a user to develop a scaffold for the application, the scaffold defining a set of assets usable by the application as well as configuration details for the assets; generate at least one scaffold map, each scaffold map specifying target
Installation · CPC title
for initial configuration or provisioning, e.g. plug-and-play · CPC title
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Software deployment · CPC title
Configuring for program initiating, e.g. using registry, configuration files · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.