Abstract: In an example embodiment, an instance of a first database and an instance of a first application in a first data center of a managed cloud are replicated to a second data center of the managed cloud. Then state information regarding the first application is stored in a network file system in the first data center. Interactions between a user and the first application are directed to the instance of the first application in the first data center. The state information is then updated based on the interactions, and any changes to the instance of the first database based on the interactions are replicated to the second data center. Then a disaster is detected in the first data center, and all interactions between the user and the first application are redirected to a second instance of the first application in the second data center caused by the replication of the instance of the first application in the first data center.

Abstract: In an example embodiment, an instance of a first database and an instance of a first application in a first data center of a managed cloud are replicated to a second data center of the managed cloud. Then state information regarding the first application is stored in a network file system in the first data center. Interactions between a user and the first application are directed to the instance of the first application in the first data center. The state information is then updated based on the interactions, and any changes to the instance of the first database based on the interactions are replicated to the second data center. Then a disaster is detected in the first data center, and all interactions between the user and the first application are redirected to a second instance of the first application in the second data center caused by the replication of the instance of the first application in the first data center.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A method of collecting data used in assessing total cost of owning enterprise computing systems is provided. The method includes distributing, to an enterprise computing system, an electronic data file that identifies, for use by a data extraction tool, predefined data source fields within the enterprising computing system and that relate to costs included in a predefined cost model that defines costs to be included in an analysis of a total cost of owning an enterprise computing system. The method also includes receiving, from the enterprise computing system, cost information aggregated using data extracted using the distributed data file, wherein the cost information is structured in conformity with the predefined cost model. The method further includes using the received cost information to formulate benchmark total cost of ownership cost information that is structured in conformity with the predefined cost model.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: The disclosure provides integrated software for supporting a distributed business application comprising computer readable instructions embodied on media. The integrated support software is operable to automatically monitor the distributed business application for potential incidents. It also facilitates continuous data exchange between the distributed business application and a remote support module based on the automatic monitoring, with the communications in a protocol associated with a plurality of services in the distributed business application and with a plurality of incidents for these services. Upon identification of a potential incident, the software provides integrated incident management in the distributed business application and provides software maintenance management to the distributed business application for one or more identified incidents.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: The disclosure provides integrated software for supporting a distributed business application comprising computer readable instructions embodied on media. The integrated support software is operable to automatically monitor the distributed business application for potential incidents. It also facilitates continuous data exchange between the distributed business application and a remote support module based on the automatic monitoring, with the communications in a protocol associated with a plurality of services in the distributed business application and with a plurality of incidents for these services. Upon identification of a potential incident, the software provides integrated incident management in the distributed business application and provides software maintenance management to the distributed business application for one or more identified incidents.

Abstract: A method of evaluating development of an enterprise computing system includes receiving, in a computer system, a definition of a target characteristic configured to be used in performing a return on investment analysis of an enterprise computing system. During development of the enterprise computing system, at least a predefined portion of the enterprise computing system is evaluated using the target characteristic. The method further includes outputting from the computer system feedback information on the development including a result of the evaluation.