US 12,135,964 B2
Software updates without downtime via an integration content mapper for integration services
Gopalkrishna Kulkarni, Bangalore (IN)
Assigned to SAP SE, Walldorf (DE)
Filed by SAP SE, Walldorf (DE)
Filed on Jun. 10, 2022, as Appl. No. 17/837,252.
Prior Publication US 2023/0401053 A1, Dec. 14, 2023
Int. Cl. G06F 8/656 (2018.01); G06F 8/61 (2018.01); G06F 11/36 (2006.01)
CPC G06F 8/656 (2018.02) [G06F 8/61 (2013.01); G06F 11/3688 (2013.01); G06F 11/3692 (2013.01)] 9 Claims
OG exemplary drawing
 
1. A system associated with a cloud computing environment, comprising:
a tenant data store containing information associated with tenants of the cloud computing environment, including an indication that a first customer has subscribed to an exclusive tenant that receives an upcoming version of runtime software associated with an Enterprise Service Bus (“ESB”);
a notification system that pushes a notification about the upcoming version of runtime software to an integration service for the first customer;
a tenant preview service, for the exclusive tenant, containing the upcoming version of runtime software;
a software update store containing new integration scenario content, created and tested by the first customer, in connection with the upcoming version of runtime software; and
an integration content mapper, including:
a computer processor, and
computer memory, coupled to the computer processor and storing instructions that, when executed by the computer processor, cause the integration content mapper to:
(i) determine, based on old and new integration scenario content metadata, if an automatic port of the new integration scenario content in the software update store should be automatically provided to a runtime node,
(ii) if the new integration scenario content should be automatically provided, use a software update tool to automatically deploy the new integration scenario content, via an Application Programming Interface (“API”), for a plurality of customers and tenants, and
(iii) if the new integration scenario content should not be automatically provided, automatically deploy old integration scenario content to the runtime node.