Abstract: In some implementations, there is provided a method including receiving, by a centralized controller, data from a plurality of database tables at a plurality of database instances at a cloud service, wherein the data is received via a plurality of database views on the plurality of database tables; in response to receiving the data, performing, by the centralized controller, a union view of the data obtained from the plurality of database views; storing, by the centralized controller, the union view of the data as configuration metadata; and performing, by the centralized controller, at least one calculation view to update a value of the configuration metadata and to provide the updated value to at least one of the plurality of database tables at the cloud service. Related systems and articles of manufacture are also disclosed.

Abstract: In some implementations, there is provided a method including receiving, by a centralized controller, data from a plurality of database tables at a plurality of database instances at a cloud service, wherein the data is received via a plurality of database views on the plurality of database tables; in response to receiving the data, performing, by the centralized controller, a union view of the data obtained from the plurality of database views; storing, by the centralized controller, the union view of the data as configuration metadata; and performing, by the centralized controller, at least one calculation view to update a value of the configuration metadata and to provide the updated value to at least one of the plurality of database tables at the cloud service. Related systems and articles of manufacture are also disclosed.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for receiving the configuration model from a configuration definition repository, the configuration model providing one or more configuration definitions for configuring a software product within a landscape, receiving a landscape plan, the landscape plan defining one or more components of a landscape, on which the software product is to be configured, determining that at least one configuration task of a plurality of configuration tasks is to be executed automatically, the plurality of configuration tasks being included in a workflow that is provided based on the one or more configuration definitions, and the landscape plan, and, in response, automatically executing the at least one configuration task using at least a portion of the automation content.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for receiving the configuration model from a configuration definition repository, the configuration model providing one or more configuration definitions for configuring a software product within a landscape, receiving a landscape plan, the landscape plan defining one or more components of a landscape, on which the software product is to be configured, determining that at least one configuration task of a plurality of configuration tasks is to be executed automatically, the plurality of configuration tasks being included in a workflow that is provided based on the one or more configuration definitions, and the landscape plan, and, in response, automatically executing the at least one configuration task using at least a portion of the automation content.

Abstract: Techniques for using a software logistics protocol include initiating, using the software logistics protocol, a software logistics process, the software logistics protocol being a common application programming interface (API) for controlling and managing the life cycle and operation of a plurality of different software logistics processes; monitoring, using the software logistics protocol, the progress of execution of the software logistics process; and gathering, using the software logistics protocol, output information from the software logistics process after the software logistics process finishes executing.

Abstract: Techniques for using a software logistics protocol include initiating, using the software logistics protocol, a software logistics process, the software logistics protocol being a common application programming interface (API) for controlling and managing the life cycle and operation of a plurality of different software logistics processes; monitoring, using the software logistics protocol, the progress of execution of the software logistics process; and gathering, using the software logistics protocol, output information from the software logistics process after the software logistics process finishes executing.