Sap Se

Christopher Schildt

Cornelia Kinder

Alexander Bunte

Volker Sauermann

Arne Harren

Michael Wintergerst

Simon Lueders

Jonathan Bregler

Andreas Kellner

Michael Schnaubelt

Daniel Kuntze

Le-Huan Stefan Tran

Vladislav Leonkev

Ralph Debusmann

Andreas Thumfart

Andre Hildebrandt

Stefan A Baeuerle

Anil Kumar Goel

Meinolf Block

Klaus Kopecz

Roger Killian-Kehr

A system, a method, and a computer program product for deployment of objects are disclosed. At least one configuration for deploying of at least one artifact during runtime of an application is defined. The configuration includes at least one dependency for the artifact. The configuration is applied to the artifact. The artifact is deployed based on the applied configuration during runtime of the application. The configuration can include at least one of the following: a default configuration for the artifact and an explicit configuration for the artifact.

User-configurable database artifacts

Key values can be defined at design time (e.g. in a DTTI object) using character strings that include wildcard characters that define multi-dimensional key ranges. Wildcard characters can designate that a single variable character is to be inserted or that a range from zero to multiple characters can be inserted. The use of wildcards can make checks for key intersection non-trivial. During run time, the key values to be accessed from one or more tables are evaluated, and the operation proceeds. An error can occur if the presence of one or more wildcards in two key value strings used in an aggregation operation result in an overlap such that a same record is included more than once.

Determining an intersection between keys defining multi-dimensional value ranges

The current subject matter relates to an approach for splitting and rewriting database object bundles into database entities or subunits. For example, cyclical dependencies between a first parameter file and a second parameter file can be identified. The first parameter file can be partitioned into a plurality of subunits comprising a first subunit and a second subunit. The second parameter file, the first subunit, and the second subunit can be reordered to a call order that ensures there are no cyclical dependencies.

Transparently splitting and rewriting data-base object bundles to database entities

A system, a method, and a computer program product for deployment of objects are disclosed. Using a deployment infrastructure of a database system, a deployment container for deployment of at least one object at runtime of an application is generated. The container includes at least one artifact for the object and a container schema indicative of at least one dependency associated with the object. At least one deployment privilege is associated based on the container schema with the artifact for the object. The artifact of the deployment container is deployed based on the associated deployment schema during runtime of the application. The container can be an isolated container and an access privilege to an object can be requested based on a synonym for deployment purposes.

Database level containers

A system, a method, and a computer program product for deploying objects are disclosed. A file containing a plurality of artifacts for deploying during runtime of an application is defined. At least one dependency for at least one artifact in the plurality of artifacts is determined based on the defined file. A database object for implementation during runtime of the application is created based on the determined dependency. At least one change to the database object during runtime of the application is implemented. The artifact is deployed during runtime of the application based on the implemented change to the database object.

Deployment process plugin architecture

A system, a method, and a computer program product for deploying of objects are disclosed. At least one file containing a plurality of artifacts for deploying during runtime of an application is defined. Each artifact in the plurality of artifacts includes at least one object in the plurality of objects required to be deployed during runtime of the application. At least one dependency for at least one artifact in the plurality of artifacts is determined. An execution order for deployment of the plurality of artifacts is generated. The plurality of artifacts is deployed in accordance with the generated execution order.

Deployment of database objects

Design time artifacts ordered in a dependency tree according to a call order defined by a database application accessing data in a database can be classified as source and/or sink artifacts. The dependency tree can be traversed in a direction reverse of the call order to determine, for each sink artifact, one or more required source artifacts upon which the sink artifact depends and that is needed to provide correct data inputs for operation of the sink artifact. Based on the traversing, implicitly dependent sink artifacts positioned earlier in the call order that their required source artifacts can be identified, and a new call order can be defined in which all of the required source artifacts for the implicitly dependent sink artifact are called before the implicitly dependent sink artifact.

Sorting runtime calls of design time artifacts via data dependencies

Growing community of inventors

Walldorf, Germany

Christopher Schildt