Patent application number | Description | Published |
20100162221 | SHIPMENT INFRASTRUCTURE FOR ADD-ON CONTENT - A system including a software maintenance tool of a business process platform to manage software changes related to a main software product including a software enhancement supplement of the main software product; and a control unit interfaced with the software maintenance tool and provided by a software product provider to create, assemble, and provision the software enhancement supplement to the software maintenance tool based on a type of content comprising the software enhancement supplement. | 06-24-2010 |
20100169873 | BUSINESS SCOPE DEPENDENT ADD-ON CONTENT PROVISIONING - A system and method to install a software enhancement supplement of a main software product, the method including receiving an installation recommendation for the supplement having content including a business configuration (BC) object on a customer/service provider side of a business process platform from a product provider; displaying an indication of the receipt of the installation recommendation; processing the installation of the supplement into the business process platform of the customer; and providing a notification of the supplement's status upon completion of the supplement installation. | 07-01-2010 |
20120030502 | TENANT RESCUE FOR SOFTWARE CHANGE PROCESSES IN MULTI-TENANT ARCHITECTURES - A multi-tenant system can be switched to a downtime state to implement a transition from a current state to a target state of a core software platform. During a second phase of the transition an error associated with tenant-specific content of a first customer tenant of the plurality of customer tenants of the multi-tenant system can be identified. The second phase can be suspended for the first customer tenant while continuing the second phase for a remainder of the plurality of customer tenants for which an error has not been identified. After a scheduled duration of the downtime state, the multi-tenant system can be reactivated such that the multi-tenant system includes the remainder of the plurality of customer tenants with the transition implemented and the first customer tenant either with the transition implemented if the error has been corrected or without the transition implemented if the error has not been corrected. | 02-02-2012 |
20120030663 | MULTIPLEXER FOR MULTI-TENANT ARCHITECTURES - A tenant multiplexer in an administrative tenant of a multi-tenant software architecture can call an administrative agent in the administrative tenant and receive, from the administrative agent, an action framework and a trusted connection protocol for accessing each of the plurality of client tenants. The trusted connection protocol can establish, without tenant-specific authentication information, a trusted system connection to an update agent in each of the plurality of client tenants. An action framework can be simultaneously implemented using the update agent of each of at least a subset of the plurality of client tenants under control of the multiplexer via the trusted system connection to begin execution of the software process for the at least the subset of client tenants. | 02-02-2012 |
20120030666 | STANDARDIZED PROCEDURES FOR IMPLEMENTING SOFTWARE CHANGES - A change to a tenant-independent content item identified as a target for changes as part of an update process of a core software platform provided by a multi-tenant system can be registered, and one or more customer tenants of the multi-tenant system can be analyzed to identify tenant-specific content items to which the registered change are relevant. A sequence can be established for processing a modification to the tenant-specific content item resulting from the registered change. The sequence can be based on at least one dependency of the tenant-specific content item on the tenant-independent content item affected by the registered change. Related articles and systems are also disclosed. | 02-02-2012 |
20130262689 | MULTIPLEXER FOR MULTI-TENANT ARCHITECTURES - A tenant multiplexer in an administrative tenant of a multi-tenant software architecture can call an administrative agent in the administrative tenant and receive, from the administrative agent, an action framework and a trusted connection protocol for accessing each of the plurality of client tenants. The trusted connection protocol can establish, without tenant-specific authentication information, a trusted system connection to an update agent in each of the plurality of client tenants. An action framework can be simultaneously implemented using the update agent of each of at least a subset of the plurality of client tenants under control of the multiplexer via the trusted system connection to begin execution of the software process for the at least the subset of client tenants. | 10-03-2013 |
20130346787 | Tenant Rescue for Software Change Processes in Multi-Tenant Architectures - A multi-tenant system can be switched to a downtime state to implement a transition from a current state to a target state of a core software platform. During a second phase of the transition an error associated with tenant-specific content of a first customer tenant of the plurality of customer tenants of the multi-tenant system can be identified. The second phase can be suspended for the first customer tenant while continuing the second phase for a remainder of the plurality of customer tenants for which an error has not been identified. After a scheduled duration of the downtime state, the multi-tenant system can be reactivated such that the multi-tenant system incldues the remainder of the plurality of customer tenants with the transition implemented and the first customer tenant either with the transition implemented if the error has been corrected or without the transition implemented if the error has not been corrected. | 12-26-2013 |