Abstract: Representative implementations provide devices and techniques for automatically generating a skeleton of at least a portion of a web service application. The skeleton comprises a framework that may be modified as needed for a desired use, such as for a relational database backed application, for example. In one aspect, the framework includes a versatile model to support different validation methods and varied customization. Filter support allows a user to perform actions on and/or define rules for inputs. In another aspect, the skeleton is automatically activated in an in-memory database repository.

Abstract: A table selector may receive a selection of a replicated table storing data replicated from an original table of a first system, the replicated table being stored using a second system and currently executing a process of receiving the replicated data. A suspension manager may suspend the process of receiving the replicated data, and a table attribute manager may change a replicated table attribute of the replicated table, while the process of receiving the replicated data is suspended. The suspension manager may then resume the process of receiving the replicated data.

Abstract: Described herein is a technology for facilitating delta data load. In some implementations, history tables corresponding to physical tables in a data source are provided in a database layer. The database layer includes change list tables corresponding to the history tables and a physical data model based on one or more physical tables. Delta data is determined by analyzing the change list table to create delta data summary tables. Key lists are generated for summary tables corresponding to physical tables which physical data is based. The delta data is applied to the physical data model.

Abstract: Representative implementations provide devices and techniques for automatically generating a skeleton of at least a portion of a web service application. The skeleton comprises a framework that may be modified as needed for a desired use, such as for a relational database backed application, for example. In one aspect, the framework includes a versatile model to support different validation methods and varied customization. Filter support allows a user to perform actions on and/or define rules for inputs. In another aspect, the skeleton is automatically activated in an in-memory database repository.

Abstract: A framework for handling a wrapper procedure is provided herein. In accordance with one aspect, a user definition of a wrapper procedure encapsulating a stored procedure is received. The framework retrieves metadata associated with the stored procedure. The framework may prepare at least one query statement to invoke the stored procedure using an input parameter identified from the metadata. The framework may further set at least one value of at least one identified input parameter based on the metadata, and execute the prepared query statement using the set value of the input parameter to generate at least one value for an output parameter.

Abstract: A table selector may receive a selection of a replicated table storing data replicated from an original table of a first system, the replicated table being stored using a second system and currently executing a process of receiving the replicated data. A suspension manager may suspend the process of receiving the replicated data, and a table attribute manager may change a replicated table attribute of the replicated table, while the process of receiving the replicated data is suspended. The suspension manager may then resume the process of receiving the replicated data.

Abstract: Described herein is a technology for facilitating delta data load. In some implementations, history tables corresponding to physical tables in a data source are provided in a database layer. The database layer includes change list tables corresponding to the history tables and a physical data model based on one or more physical tables. Delta data is determined by analyzing the change list table to create delta data summary tables. Key lists are generated for summary tables corresponding to physical tables which physical data is based. The delta data is applied to the physical data model.