Abstract: An update system is provided that generates a service list of services and sorts the services in the service list from least dependent services to most dependent services. Services that are unaffected by updates as determined based on the sorting are removed. An update runbook is generated with steps for updating the services. An order of the steps is based on the sorted service list, and the steps indicate target services, hosting machines and actions to perform on target services.

Abstract: An update system is provided that generates a service list of services and sorts the services in the service list from least dependent services to most dependent services. Services that are unaffected by updates as determined based on the sorting are removed. An update runbook is generated with steps for updating the services. An order of the steps is based on the sorted service list, and the steps indicate target services, hosting machines and actions to perform on target services.

Abstract: An update system is provided that performs a stop of that service at each machine that hosts that service such that a service that is dependent on another service stops before that other service starts performing a stop. After a machine hosting a service stops, the update system performs an update of that service on that machine. The update system then performs a start of that service at each machine that hosts that service such than a service that another service depends on starts before that other service starts performing a start.

Abstract: A computing system comprises, in one example, a difference generation component configured to access a type file representing a type in a base version of a computing system and identify a customization made to the type in the base version of the computing system to obtain a customized version of the computing system, and a type accessing component configured to serialize the customization into a customization file of a given file format, the customization file having a separate element representing each customization made to the type in the base version of the computing system to obtain the customized version of the computing system, the type accessing component storing the customization file as a separate file from the type file.

Abstract: A computing system comprises, in one example, a difference generation component configured to access a type file representing a type in a base version of a computing system and identify a customization made to the type in the base version of the computing system to obtain a customized version of the computing system, and a type accessing component configured to serialize the customization into a customization file of a given file format, the customization file having a separate element representing each customization made to the type in the base version of the computing system to obtain the customized version of the computing system, the type accessing component storing the customization file as a separate file from the type file.

Abstract: A computing system comprises, in one example, a difference generation component configured to access a type file representing a type in a base version of a computing system and identify a customization made to the type in the base version of the computing system to obtain a customized version of the computing system, and a type accessing component configured to serialize the customization into a customization file of a given file format, the customization file having a separate element representing each customization made to the type in the base version of the computing system to obtain the customized version of the computing system, the type accessing component storing the customization file as a separate file from the type file.

Abstract: Multiple instances of a computer system subscribe to a central data storage system. The central data storage system receives a set of entities that the instances wish to synchronize with one another, along with a schema representing those entities, from each instance. The central data storage system receives changes to the identified entities from the various instances, identifies conflicts, and synchronizes changes from a given instance to the other subscribing instances.

Abstract: Multiple instances of a computer system subscribe to a central data storage system. The central data storage system receives a set of entities that the instances wish to synchronize with one another, along with a schema representing those entities, from each instance. The central data storage system receives changes to the identified entities from the various instances, identifies conflicts, and synchronizes changes from a given instance to the other subscribing instances.

Abstract: An update system is provided that performs a stop of that service at each machine that hosts that service such that a service that is dependent on another service stops before that other service starts performing a stop. After a machine hosting a service stops, the update system performs an update of that service on that machine. The update system then performs a start of that service at each machine that hosts that service such than a service that another service depends on starts before that other service starts performing a start.

Abstract: A computer system includes a processor and a data store coupled to the processor. An application component is operably coupled to the processor and the data store and is configured to run one or more applications stored in the data store. A test framework is coupled to the processor and the data store and is configured to perform at least one test relative to a component of the computer system that interacts with a database. A savepoint manager is configured to responsively generate at least one savepoint in the database prior to the at least one test and to roll back the at least one savepoint after the at least one test. Methods of testing the computer system are also provided.

Abstract: A computing system comprises, in one example, a difference generation component configured to access a type file representing a type in a base version of a computing system and identify a customization made to the type in the base version of the computing system to obtain a customized version of the computing system, and a type accessing component configured to serialize the customization into a customization file of a given file format, the customization file having a separate element representing each customization made to the type in the base version of the computing system to obtain the customized version of the computing system, the type accessing component storing the customization file as a separate file from the type file.

Abstract: A computer system includes a processor and a data store coupled to the processor. An application component is operably coupled to the processor and the data store and is configured to run one or more applications stored in the data store. A test framework is coupled to the processor and the data store and is configured to perform at least one test relative to a component of the computer system that interacts with a database. A savepoint manager is configured to responsively generate at least one savepoint in the database prior to the at least one test and to roll back the at least one savepoint after the at least one test. Methods of testing the computer system are also provided.

Abstract: Techniques to prioritize and optimize the execution of upgrade operations are described. A technique may include determining the size of data blocks that are to be copied from one storage medium to another, and the dependencies of upgrade tasks on the data blocks and on other tasks. A task may be prioritized according to a weight that includes the cumulative sizes of the data blocks that it and its dependent tasks depend on. A data block copying may be prioritized according to the cumulative weights of the tasks that depend on that data block. Some embodiments may perform several data copying and/or tasks in parallel, rather than sequentially. Other embodiments are described and claimed.

Abstract: Multiple instances of a computer system subscribe to a central data storage system. The central data storage system receives a set of entities that the instances wish to synchronize with one another, along with a schema representing those entities, from each instance. The central data storage system receives changes to the identified entities from the various instances, identifies conflicts, and synchronizes changes from a given instance to the other subscribing instances.

Abstract: A base assembly generated from a model in a computer system and a customization assembly generated from a customization model that models customization to the computer system are run separately. The customizations are applied to extend the base system, without overwriting any of the code for the base system.

Abstract: A customization environment uses a customization system that models customizations to a base computer system. Each set of customizations is stored as a separate extension package, which is stored separately from the code for the base system. During runtime, the extension packages are discovered in a runtime environment and applied to extend the base system, without overwriting any of the code for the base system.

Abstract: Enterprise systems, methods and computer program products are disclosed for providing caching of data retrieved from joined tables and an inheritance table hierarchy of a database in an enterprise. The computer implemented method comprises creating a queue of cursors of a statement associated with a database; evaluating a cursor of the queue and marking as one of a unique record and an object of an inheritance table; and, if a cursor of the queue is marked as one of a unique record and a unique object, then, storing data associated with one of the unique record and object in a data cache for subsequent retrieval, thus avoiding costly network calls. If the process leaves a cursor unevaluated, the method retrieves data from an enterprise database associated with the statement. The process is implemented on an application object server including a data access layer and a kernel instance.

Abstract: Enterprise systems, methods and computer program products are disclosed for providing bulk create (insert), update and delete operations for table inheritance in an enterprise resource system using an object-oriented language supporting polymorphism. The computer implemented method comprises receiving a request for one of a create, update and delete operation with respect to data of first and second tables of an inheritance table hierarchy; creating a temporary table comprising a surrogate key and a record identifier; establishing a filter condition with fields from different tables in table inheritance; and one of creating, updating and deleting data from the different tables in table inheritance according to the filter condition. The process is implemented on an application object server including a compiler for the object-oriented language, a kernel instance and a data access layer.

Abstract: Enterprise systems, methods and computer program products are disclosed for providing caching of data retrieved from joined tables and an inheritance table hierarchy of a database in an enterprise. The computer implemented method comprises creating a queue of cursors of a statement associated with a database; evaluating a cursor of the queue and marking as one of a unique record and an object of an inheritance table; and, if a cursor of the queue is marked as one of a unique record and a unique object, then, storing data associated with one of the unique record and object in a data cache for subsequent retrieval, thus avoiding costly network calls. If the process leaves a cursor unevaluated, the method retrieves data from an enterprise database associated with the statement. The process is implemented on an application object server including a data access layer and a kernel instance.

Abstract: Techniques to prioritize and optimize the execution of upgrade operations are described. A technique may include determining the size of data blocks that are to be copied from one storage medium to another, and the dependencies of upgrade tasks on the data blocks and on other tasks. A task may be prioritized according to a weight that includes the cumulative sizes of the data blocks that it and its dependent tasks depend on. A data block copying may be prioritized according to the cumulative weights of the tasks that depend on that data block. Some embodiments may perform several data copying and/or tasks in parallel, rather than sequentially. Other embodiments are described and claimed.