IP Library › Granted Patent US 12,254,020
Granted Patent B2
US 12,254,020 · App. 17/484,704 · Granted Mar 18, 2025

Container plugin for legacy on-premise application

Inventor: Daniel Kirmse (Berlin, DE)
Assignee: SAP SE
G06F16/252G06F9/44526G06F16/18
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 12,254,020
App. No.
17/484,704
Granted
Mar 18, 2025
Kind
B2
Abstract

Various examples are directed to systems and methods for installing a plugin to a cloud-implemented database management application. A shared container file system may be initiated at a cloud environment. A plugin container image may be accessed, where the plugin container image comprises plugin payload data describing a first plugin to the database management application and a copy executable. A plugin container may be started at the cloud environment, where the plugin container is based at least in part on the plugin container image. The plugin container may be mounted to the shared container file system. The copy executable may be executed to copy the plugin payload data to the shared container file system. The first plugin may be installed to a database management application instance executing at the cloud environment.

Claims (60)

1. A system for installing a plugin to an on premise database management application executed in a cloud environment, the system comprising:

at least one processor programmed to perform operations comprising:

executing a container orchestration service;

initiating, by the container orchestration service, a shared container file system at the cloud environment;

accessing, by the container orchestration service, a plugin container image, the plugin container image comprising plugin payload data associated with a first plugin to the database management application and a copy executable, the plugin payload data comprising a first plugin executable;

starting, by the container orchestration service, a plugin container at the cloud environment, the plugin container being based at least in part on the plugin container image;

mounting the plugin container to the shared container file system;

executing the copy executable to copy the plugin payload data to the shared container file system;

starting, by the container orchestration service, a plugin deployer container at the cloud environment;

mounting the plugin deployer container to the shared container file system;

executing an installer executable at the plugin deployer container;

moving, by the installer executable, the plugin payload data from the shared container file system to at least one container implementing an instance of the database management application at the cloud environment; and

executing the first plugin executable in the at least one container implementing the instance of the database management application at the cloud environment.

2. The system of claim 1 , further comprising extracting, by the plugin deployer container, the plugin payload data from the shared container file system.

3. The system of claim 2 , further comprising connecting the plugin deployer container to the at least one container implementing the instance of the database management application.

4. The system of claim 1 , the accessing of the plugin container image comprising accessing the plugin container image from a container image registry.

5. The system of claim 1 , the copy executable being statically-linked.

6. The system of claim 1 , the plugin container image further comprising a statically-linked security executable, the operations further comprising executing the security executable to perform at least one security check on the plugin payload data.

7. The system of claim 1 , the plugin container image further comprising a statically-linked scanning executable, the operations further comprising executing the scanning executable to perform at least one scan of the plugin payload data.

8. The system of claim 1 , further comprising:

receiving, by a frontend service executing at the cloud environment, a plugin request from a first user associated with a first user group, the instance of the database management application being associated with the first user group;

determining, by the frontend service, a version of the instance of the database management application; and

accessing a plugin catalog, by the frontend service, to determine at least one plugin compatible with the database management application, the at least one plugin comprising the first plugin.

9. A method for installing a plugin to an on premise database management application executed in a cloud environment, the method comprising:

executing a container orchestration service;

initiating, by the container orchestration service, a shared container file system at the cloud environment;

accessing, by the container orchestration service, a plugin container image, the plugin container image comprising plugin payload data associated with a first plugin to the database management application and a copy executable, the plugin payload data comprising a first plugin executable;

starting, by the container orchestration service, a plugin container at the cloud environment, the plugin container being based at least in part on the plugin container image;

mounting the plugin container to the shared container file system;

executing the copy executable to copy the plugin payload data to the shared container file system;

starting, by the container orchestration service, a plugin deployer container at the cloud environment;

mounting the plugin deployer container to the shared container file system;

executing an installer executable at the plugin deployer container;

moving, by the installer executable, the plugin payload data from the shared container file system to at least one container implementing an instance of the database management application at the cloud environment; and

executing the first plugin executable in the at least one container implementing the instance of the database management application at the cloud environment.

10. The method of claim 9 , further comprising extracting, by the plugin deployer container, the plugin payload data from the shared container file system.

11. The method of claim 10 , further comprising further comprising connecting the plugin deployer container to the at least one container implementing the instance of the database management application.

12. The method of claim 9 , the accessing of the plugin container image comprising accessing the plugin container image from a container image registry.

13. The method of claim 9 , the copy executable being statically-linked.

14. The method of claim 9 , the plugin container image further comprising a statically-linked security executable, the method further comprising executing the security executable to perform at least one security check on the plugin payload data.

15. The method of claim 9 , the plugin container image further comprising a statically-linked scanning executable, the method further comprising executing the scanning executable to perform at least one scan of the plugin payload data.

16. The method of claim 9 , further comprising:

receiving, by a frontend service executing at the cloud environment, a plugin request from a first user associated with a first user group, the instance of the database management application being associated with the first user group;

determining, by the frontend service, a version of the instance of the database management application; and

accessing a plugin catalog, by the frontend service, to determine at least one plugin compatible with the database management application, the at least one plugin comprising the first plugin.

17. A non-transitory machine-readable medium comprising instructions thereon that, when executed by at least one processor, cause the at least one processor to perform operations comprising:

executing a container orchestration service;

initiating, by the container orchestration service, a shared container file system at a cloud environment;

accessing, by the container orchestration service, a plugin container image, the plugin container image comprising plugin payload data associated with a first plugin to a database management application and a copy executable, the plugin payload data comprising a first plugin executable;

starting, by the container orchestration service, a plugin container at the cloud environment, the plugin container being based at least in part on the plugin container image;

mounting the plugin container to the shared container file system;

executing the copy executable to copy the plugin payload data to the shared container file system;

starting, by the container orchestration service, a plugin deployer container at the cloud environment;

mounting the plugin deployer container to the shared container file system;

executing an installer executable at the plugin deployer container;

moving, by the installer executable, the plugin payload data from the shared container file system to at least one container implementing an instance of a database management application at the cloud environment; and

executing the first plugin executable in the at least one container implementing the instance of the database management application at the cloud environment.

18. The medium of claim 17 , the operations further comprising extracting, by the plugin deployer container, the plugin payload data from the shared container file system.

19. The medium of claim 18 , the operations further comprising connecting the plugin deployer container to the at least one container implementing the instance of the database management application.

20. The medium of claim 17 , the accessing of the plugin container image comprising accessing the plugin container image from a container image registry.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 8, 2021
From: KIRMSE, DANIEL
To: SAP SE
Reel/Frame 057738/0414 →
Continuity (1)
Related Publication 20230102514A1 · Mar 30, 2023
References Cited (99)
US 9817653B2 · Sreedharan et al. · 2017 [cited by applicant]
US 10320625B1 · Cherumbath · 2019 [cited by applicant]
US 10338964B1 · Kancharla et al. · 2019 [cited by applicant]
US 10387385B1 · Mart · 2019 [cited by applicant]
US 10496392B2 · Shuvali et al. · 2019 [cited by applicant]
US 10732951B2 · Jayanthi et al. · 2020 [cited by applicant]
US 10853146B1 · Talayco · 2020 [cited by applicant]
US 11113090B1 · Wilkinson et al. · 2021 [cited by applicant]
US 11372820B1 · Harjono et al. · 2022 [cited by applicant]
US 11704408B1 · Ciubotariu · 2023 [cited by examiner]
US 11841731B2 · Kirmse · 2023 [cited by applicant]
US 11922163B2 · Kirmse · 2024 [cited by applicant]
US 12013866B2 · Kirmse · 2024 [cited by applicant]
US 12026496B2 · Kirmse · 2024 [cited by applicant]
US 20060167947A1 · Dunkle · 2006 [cited by applicant]
US 20070067361A1 · Bailey et al. · 2007 [cited by applicant]
US 20090177646A1 · Pham et al. · 2009 [cited by applicant]
US 20110083138A1 · Sivasubramanian et al. · 2011 [cited by applicant]
US 20130190080A1 · Bibbey et al. · 2013 [cited by applicant]
US 20130263088A1 · Hoff et al. · 2013 [cited by applicant]
US 20160188415A1 · Karinta et al. · 2016 [cited by applicant]
US 20160275019A1 · Nam · 2016 [cited by examiner]
US 20160294614A1 · Searle et al. · 2016 [cited by applicant]
US 20170046181A1 · Williams et al. · 2017 [cited by applicant]
US 20170115978A1 · Modi et al. · 2017 [cited by applicant]
US 20170161053A1 · Hayakawa et al. · 2017 [cited by applicant]
US 20170192873A1 · Ozdemir et al. · 2017 [cited by applicant]
US 20170300311A1 · Vasquez Lopez et al. · 2017 [cited by applicant]
US 20170330195A1 · Lange et al. · 2017 [cited by applicant]
US 20180004792A1 · Desai et al. · 2018 [cited by applicant]
US 20180011699A1 · Manthiramoorthy et al. · 2018 [cited by applicant]
US 20180267796A1 · Kennedy · 2018 [cited by examiner]
US 20190102280A1 · Caldato et al. · 2019 [cited by applicant]
US 20190146772A1 · Griffin et al. · 2019 [cited by applicant]
US 20190317887A1 · Wiener et al. · 2019 [cited by applicant]
US 20190370471A1 · Petratos et al. · 2019 [cited by applicant]
US 20200019414A1 · Byard et al. · 2020 [cited by applicant]
US 20200145337A1 · Keating et al. · 2020 [cited by applicant]
US 20200228602A1 · Spoczynski et al. · 2020 [cited by applicant]
US 20210049267A1 · Wu et al. · 2021 [cited by applicant]
US 20220050674A1 · Liljeback et al. · 2022 [cited by applicant]
US 20220107802A1 · Rao et al. · 2022 [cited by applicant]
US 20220292106A1 · Umay et al. · 2022 [cited by applicant]
US 20220294788A1 · Pattar et al. · 2022 [cited by applicant]
US 20220350642A1 · Poddar et al. · 2022 [cited by applicant]
US 20220365801A1 · Kasso et al. · 2022 [cited by applicant]
US 20230070209A1 · Srinivasan et al. · 2023 [cited by applicant]
US 20230096143A1 · Kirmse · 2023 [cited by applicant]
US 20230098023A1 · Kirmse · 2023 [cited by applicant]
US 20230102769A1 · Kirmse · 2023 [cited by applicant]
US 20230103087A1 · Kirmse · 2023 [cited by applicant]
US 20230103223A1 · Kirmse · 2023 [cited by applicant]
US 20240126540A1 · Kirmse · 2024 [cited by applicant]
CN 103268319A · 2013 [cited by applicant]
CN 110347440A · 2019 [cited by applicant]
CN 108595221B · 2021 [cited by applicant]
EP 3451341A1 · 2019 [cited by applicant]
EP 3557408A1 · 2019 [cited by applicant]
WO WO2013148144A1 · 2013 [cited by applicant]
WO WO2016028973A1 · 2016 [cited by applicant]
“European Application Serial No. 22196329.1, Extended European Search Report mailed Mar. 1, 2023”, 14 pgs. [cited by applicant]
Pahl, Claus, “Containerization and the PaaS Cloud”, IEEE Cloud Computing, vol. 1, No. 3, (May 1, 2015), 24-31. [cited by applicant]
Shah, Jay, et al., “Building Modern Clouds: Using Docker, Kubernetes & Google Cloud Platform”, IEEE 9th Annual Computing and Communication Workshop and Conference, (Jan. 7, 2019), 0184-0189. [cited by applicant]
“U.S. Appl. No. 17/484,637, Final Office Action mailed Mar. 23, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Non Final Office Action mailed Aug. 2, 2023”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Non Final Office Action mailed Nov. 10, 2022”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Notice of Allowance mailed Feb. 15, 2024”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Notice of Allowance mailed May 26, 2023”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Preliminary Amendment filed Jun. 20, 2023”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Response filed Feb. 10, 2023 to Non Final Office Action mailed Nov. 10, 2022”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Response filed May 4, 2023 to Final Office Action mailed Mar. 23, 2023”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,637, Response filed Nov. 2, 2023 to Non Final Office Action mailed Aug. 2, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,667, Corrected Notice of Allowability mailed Jan. 29, 2024”, 13 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,667, Notice of Allowance mailed Apr. 12, 2023”, 22 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,667, Notice of Allowance mailed Jul. 10, 2023”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,667, Notice of Allowance mailed Nov. 7, 2023”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,667, Preliminary Amendment filed Jun. 20, 2023”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,688, Non Final Office Action mailed Nov. 25, 2022”, 20 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,688, Notice of Allowance mailed May 3, 2023”, 15 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,688, Notice of Allowance mailed Jul. 31, 2023”, 18 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,688, Response filed Feb. 27, 2023 to Non Final Office Action mailed Nov. 25, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,732, Non Final Office Action mailed Oct. 26, 2023”, 27 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,732, Notice of Allowance mailed Feb. 22, 2024”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,732, Response filed Jan. 17, 2024 to Non Final Office Action mailed Oct. 26, 2023”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, 312 Amendment filed Oct. 8, 2024”, 6 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Corrected Notice of Allowability mailed Aug. 12, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Examiner Interview Summary mailed May 23, 2024”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Final Office Action mailed Sep. 21, 2023”, 34 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Non Final Office Action mailed Mar. 7, 2024”, 35 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Non Final Office Action mailed Apr. 13, 2023”, 30 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Notice of Allowance mailed Jul. 31, 2024”, 19 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, PTO Response to Rule 312 Communication mailed Oct. 10, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Response filed Jun. 7, 2024 to Non Final Office Action mailed Mar. 7, 2024”, 14 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Response filed Jul. 6, 2023 to Non Final Office Action mailed Apr. 13, 2023”, 14 pgs. [cited by applicant]
“U.S. Appl. No. 17/484,754, Response filed Dec. 21, 2023 to Final Office Action mailed Sep. 21, 2023”, 12 pgs. [cited by applicant]
Afgan, Enis, et al., “CloudLaunch: Discover and Deploy Cloud Applications”, arXiv:1805.04005, [Online]. Retrieved from the Internet: < URL: https://arxiv.Org/ftp/arxiv/papers/1805/1805.04005.pdf>, (2018), 9 pgs. [cited by applicant]
Lyublena, Antova, “Rapid Adoption of Cloud Data Warehouse Technology using Datometry Hyper-Q (Technical White Paper)”, Datometry Inc., [Online]. Retrieved from the Internet: <https://dl.acm.org/doi/pdf/10.1145/3183713.3… [cited by applicant]
Sharma, Prateek, “Containers and Virtual Machines at Scale: A Comparative Study”, Proceedings of the 17th International Middleware Conference, Article No. 1, [Online]. Retrieved from the Internet: <https://dl.acm.org/do… [cited by applicant]
Zurkowski, Bartosz, “Towards Self-organizing Cloud Polyglot Database Systems”, IEEE 13th International Conference on Self-Adaptive and Self-Organizing Systems, [Online] Retrieved from the internet: <https://ieeexplore.i… [cited by applicant]