Sap Ag

Sap Se

Martin Hartig

Frank Brunswig

Thomas Fiedler

Johannes Viegener

Stefan Rau

Udo Peter Klein

Helmut Prestel

Thomas Gauweiler

Rolf Hammer

Kai Baumgarten

Daniel Wachs

Christiane Kettschau

Ralf Wendelgass

Sigrid K Wortmann

Stefan Werner

Peter Eberlein

Volker Driesen

Bare Said

Timm Falter

Frank Jentsch

Juergen Specht

Martin Mayer

Steffen Tatzel

Steffen Meissner

Heiko Konrad

Achim Braemer

Christoph Luettge

Rau Stefan

Matthias Mittelstein

Stefan A Baeuerle

Uwe Schlarb

Markus Cherdron

Frank Stienhans

Guenter Pecht-Seibert

Andrey Engelko

Markus Viol

Michael Seubert

Baré Said

Daniel Zoch

Wieland Hoprich

Reiner P Hammerich

Wolfgang M Koch

Bjoern Mielenhausen

Abhay A Tiple

Uwe Bloching

Georg Wilhelm

Adam Polly

Frank Seeger

Lars-Eric Biewald

Dirk Stumpf

Maic Wintel

Jens Weiler

Joerg Weller

Andreas F Morsch

Werner Rehm

Oswald Gschnitzer

Ye Jin

Holger Koser

Joerg Lienhardt

Bolivar Santos Perez Pereira

Andre Haferkorn

Gerhard Wenzel

Erwin Burkhardt

Jutta Bindewald

Felix Wente

Christian Lutter

Bernd Krannich

Oliver Klamenz

Björn Friedmann

Florian Föbel

Christian Goldbach

Matthias Rinck

Jochen Müller

Craig Chaplin

Holger Neu

Hai Anh Pham

Disclosed herein are system, method, and computer program product embodiments for transitioning virtual systems from one run-level to a next run-level. In an embodiment, a controller may receive a run-level request to transition a computing cluster (e.g., vSystem) from a first run-level to a second run-level. The controller persists a current run-level of the computing cluster as the second run-level in a configuration file. The controller executes a set of actions corresponding to the second run-level to transition the computing cluster from the first run-level to the second-level. A gateway of the computing cluster receives a request to access the computing cluster. The request includes a user's authentication details. The gateway grants or restricts access to the computing cluster based on the type of user attempting to access the computing cluster and the current run-level of the computing cluster as indicated in the configuration file.

Managing system run-levels

A zero downtime upgrade procedure is initiated that upgrades a first version of software executing on a source system comprising at least one source server to a second version of software executing on a target system comprising at least one target server. The source system initially starts operating in a read-write mode. Thereafter, concurrent with the operation of the source system, operation of the target system is initiated in a read-only mode. Operations of the source system are then ceased by ramping down activities of the source system. Upon cessation of operation of the source system, operation of the target system is initiated in a read-write mode.

Zero downtime software system upgrade

Disclosed herein are systems and methods for embedding database procedures in data-driven software applications written in a language different from the database-procedure language. For example, in some embodiments, the hosting application may be written in ABAP whereas the database procedure may be written in SQLScript. In various embodiments, the database procedures are encapsulated in specially marked methods of the host application, which, when called at runtime, cause the database procedures to be created in a database catalog and executed on a database server.

Embedding database procedures in data-driven applications

Disclosed herein are systems and methods facilitating extensions to software applications that access a database, and in particular to applications with embedded database procedures. In various embodiments, an extension anchor embedded in the application as well as one or more extensions implemented as database procedures are encapsulated in specially marked database-procedure methods.

Extensibility of embedded database procedures

The present disclosure describes methods, systems, and computer program products for providing multi-level user interface theming. One computer-implemented method includes instantiating a shadow system and database schema for a new version software application in a shared database, the shadow system database schema containing aliases pointing to tables instantiated in a production database schema, instantiating a bridge database schema containing aliases pointing to each database table within the production database schema, preparing a bridge sub-system connected to the bridge database schema aliases, replicating database tables within the production database schema, for use by the bridge sub-system and adjusting the original database tables for structure and content consistent with the new version software application, deploying an upgrade sub-system and tools to complete adjustment of structure and content of the original database tables, and connecting an instantiated instance of the new version software application to adjusted database tables.

Zero downtime maintenance with maximum business functionality

Disclosed herein are systems and methods for the hot deployment of database procedures embedded in a host software application. In various example embodiments, the database procedures are encapsulated in specially marked methods of the host application, which, when called at runtime, cause the database procedures, and associated procedure stubs through which the database procedures are called, to be created in a database catalog and executed on the database server. When an embedded database procedure is modified in an application by one user during execution of that application by a second user, compilation of the modified database procedure may result in deletion of the original database procedure and/or associated procedure stub from the database, avoiding inconsistencies between database procedure versions during application execution by the second user.

Hot deployment of embedded database procedures

According to one general aspect, a method for managing a plurality of different tenants on a shared computing infrastructure including at least one application server apparatus may include associating a tenant with a plurality of services, wherein each service provides a set of actions that the service is configured to perform. In some embodiments, the method may include associating at least one tenant runlevel for each associated service with the tenant. In various embodiments, the method may include, when the application server apparatus executes a service for the tenant, determining the tenant runlevel associated with the tenant, and managing the set of actions configured to be performed by the service based at least in part upon the tenant runlevel associated with the tenant and the service.

Application server runlevel framework

A system is provided in which at least one first server comprises at least one data processor executing a business application platform providing various business applications for access by at least one remote client. In addition, at least one second server comprises at least one data processor executing an embedded business intelligence server (EBIS). The EBIS provides an interface to the platform to at least one business intelligence applications providing business intelligence functionality. With such a system, a unified interface can be rendered on the at least one remote client concurrently provides functionality from the platform and the at least one business intelligence client. Related apparatus, systems, techniques and articles are also described.

Business application platform with embedded business intelligence server

The subject matter described herein relates to software routines called application exits that are provided at well defined phases of a tenant copy process. The tenant copy process enables copying of separated tenant data associated with a source tenant at multi-computing tenant system to a new created tenant at a destination location either at multi-computing tenant computing system or second multi-computing tenant computing system. The application exits perform predefined functions at the well defined phases such that the predefined functions enable operations including detachment of tenant data from the source tenant that needs to be copied or moved such that the detached tenant data is separated tenant data. When the source tenant is just being moved, instead of being copied, from a source location to a destination location, the source tenant is deleted once all the data associated with the source tenant has been moved to the destination location.

Application exits for consistent tenant lifecycle management procedures

A plurality of domain-specific service adaptation languages can be supported by a back-end service adaptation system to provide runtime access to a runtime instance of a data object comprising data stored in a repository. By defining a language-specific data access service and parser for each domain-specific service adaptation language, a single, service adaptation language-independent compiler and interpreter can prepare and execute a runtime load that includes an execution plan for retrieving and converting data from the repository for delivery in a data object according to a query request from a consumer runtime environment. A consumer using the consumer runtime environment can define the service adaptation language to be used and provide a parser and source code to enable access to business object data using the back-end service adaptation system.

Multi-language support for service adaptation

A plurality of partitions can be defined in a database for a multi-tenant computing system provided on one or more processors such that each partition of the plurality of partitions is associated with only one business tenant of a set of business tenants supported by the multi-tenant system. The database can stored shared content that is shared among and accessible to all tenants of the multi-tenant computing system while tenant content for each business tenant can be stored in the database in one partition of the plurality of partitions. The one partition can be assigned to an associated business tenant. At least a portion of the tenant content can be unique to and associated with the associated business tenant. One or more errors can be generated to prevent tenant content associated with a first business tenant of the set of business tenants from being accessed by a second business tenant of the set of business tenants when an application code executed within the multi-tenant computing system comprises a construct that would otherwise enable cross-tenant access by the second business tenant to tenant content associated with the first business tenant. Related systems, methods, and computer program products are described.

Strict tenant isolation in multi-tenant enabled systems

An indication of a start of an execution of a process can be received, and a time counter associated with measuring a time elapsed can be initiated by the execution of the process. The time elapsed by the execution of the process can be compared with a predetermined threshold timeout value, and a report indicating the time elapsed by the execution of the process and whether the elapsed time exceeded the predetermined threshold timeout value can be automatically generated.

Optimizing performance of an application

A call for an application programming interface can be received from an application component at a context checking module, and a current application context of the application component within which the call for the application programming interface was generated can be determined. A context token of the application programming interface can be compared with the current application context, and if the context token does not match the context token, a remedial action can be executed. Related methods, systems, and articles of manufacture are disclosed.

Application level contexts

Systems and methods are provided for adapting a procedure call from a service manager to a service provider in a computer framework. An inbound procedure call is received, requesting an inbound procedure to operate on an object. Then, the inbound procedure is transformed to an outbound procedure based on a stored mapping of input procedures to output procedures. The outbound procedure is called from the service provider to operate on the object.

Systems and methods for adapting procedure calls to service providers

A system may include generation of extension metadata defining a functional extension associated with a business object, and generation of a runtime metadata buffer comprising enhanced metadata, the enhanced metadata based on core metadata of the business object and the extension metadata. In some aspects, a service request associated with the business object is received, it is determined whether the service request is associated with the functional extension, an extension service associated with the functional extension is provided if it is determined that the service request is associated with the functional extension, and a core service associated with core data of the business object is provided if it is determined that the service request is not associated with the functional extension.

Functional extensions for business objects

Growing community of inventors

Speyer, Germany

Martin Hartig