Sap Se

Sap Ag

Andrey Engelko

Volker Driesen

Wieland Hoprich

Martin Mayer

Steffen Meissner

Nicolai Jordt

Levke Bentzien

Peter Schreiber

Andreas Jahr

Christiane Valentin

Andre Haferkorn

Klaus Daschakowsky

Peter Eberlein

Martin Hartig

Juergen Specht

Thomas Vogt

Lars-Eric Biewald

Heiko Konrad

Dirk Debertin

Christoph Luettge

Joerg Schmidt

Tobias Wenner

Fabrizio Muscarella

Florian Mueller

Joerg Schoen

Florian Thomas

Manikandan Rajasekar

Georg Storz

Lars Spielberg

Matthias Mittelstein

Christian Fiderer

Abdullah Amer

The disclosure generally describes methods, software, and systems, including a method for generating suggestions for extensions to data sets. Using metadata for a plurality of documents, data relationships are determined between sets of documents of the plurality of documents. Each set of documents originates from different data sources and does not share common ontologies. The metadata includes terms and labels for documents in the plurality of documents. Using the determined data relationships, enhancement suggestions are determined. Each enhancement suggestion identifies pieces of information from at least one first document in the set of documents that can serve as an extension to information contained in a second document in the set of documents. The identified enhancement suggestions are ranked based on enhancement usability ranking factors. The ranked enhancement suggestions are provided.

Generating suggestions for extending documents

Methods, systems, and computer-readable storage media for minimizing downtime during maintenance procedures to an application. In some implementations, actions include executing a first application, executing a second application, and providing an access schema layer that facilitates communication between applications and a data schema layer, the data schema layer including one or more tables of a database, wherein, during a maintenance procedure, the access schema layer includes: a first access schema, the first access schema facilitating exclusive communication between the first application and at least one table of the data schema layer, and a second access schema, the second access schema facilitating exclusive communication between the second application and one or more tables of the data schema layer.

Zero downtime maintenance for applications and databases

Continuous access to an application and associated data is provided during a modification (for example, an upgrade) of the application. Shared tables are used to perform parallel changes in databases associated with an original database schema, a temporary database schema, and an upgraded database schema. Aliases are used to access shared tables from some database schemas. The use of shared tables obviates a separate merging of data written by different tools and/or systems during an upgrade of the application. Related methods, apparatuses, systems, techniques and articles are also described.

Aliases for accessing shared tables during provision of continuous access during application upgrade

A system, a method, and a computer program product for providing a generic user interface client. At least one common process in a plurality of processes performed by a plurality of software programs is determined. A user interface client for managing the common process is executed. The common process is managed using the user interface client.

Generic user interface client for software logistics processes

An upgrade of a first version of a database application to a second version of a database application that both have a same data schema is initiated. The first database application has a first access schema such that at least one table in the data schema is linked to the first access schema. The second version of the database application has a second access schema such that at least one table in the data schema is linked to the second access schema. The first access schema differs from the second access schema. Subsequently, concurrent access is provided for each access schema to at least one database table in the data schema to both the first version of the database application and the second version of the database application. The concurrent access is enabled by using separate read and write channels. Related apparatus, systems, techniques and articles are also described.

Simultaneous operation of multiple versions of an application using bidirectional synchronization and separated read write channels

A system and method for database migration is provided. In an example embodiment, the database migration technique may include a first connection to a relational database, a second connection to an in-memory database, and a migration framework to analyze the data structures of the relational database so as to identify first and second subsets of data structures. The first subset of data structures is migrated to the in-memory database during an uptime period of the relational database, and the second subset of data structures is migrated to the in-memory database during a downtime period of the relational database.

Systems and methods for in-place migration with downtime minimization

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

A temporary system is described to provide, during an upgrade of an application implemented using an original system, a continuous access to the application. A copy of a first data-set characterizing a first version of the application is generated on the temporary system when the upgrade becomes available. A selective access to the copy on the temporary system is enabled while preventing access to the first data-set on an original system. The first data-set on the original system is upgraded to form a second data-set characterizing a second version of the application, and a testing of the second data-set is performed. When a result of the testing indicates that the second data-set should be implemented, an access to the second data-set on the original system is enabled while preventing access to the copy on the temporary system. Related methods, apparatus, systems, techniques and articles are also described.

Using temporary system to provide continuous access during application upgrade

Techniques for upgrading and migrating software systems include configuring a target database on a computing appliance that is communicably coupled with a distributed computing environment that includes a source database, the source database including a plurality of productive database tables and a plurality of non-productive database tables; determining a distribution of database tables to migrate to the target database, the distribution including at least a portion of the plurality of productive and non-productive database tables from the source database and at least one new database table of a database upgrade; migrating the distribution of database tables to the target database; and pointing a productive system of the distributed computing environment to the target database.

Upgrading and migrating a database by a migration tool

The subject matter described herein relates to providing a continuous access to a database at times, including when the database is being modified or upgraded. Initially, access to an old version of a table is enabled and provided to a user. A copy of the old version is generated. Access is asynchronously redirected from the old version to the copy of the old version. A new version of the table is generated by modifying the structure of the first version of the table. The copy of the old version is accessible when the database is being modified or upgraded. When the structure is being modified, access is asynchronously redirected from the copy of the old version to the new version.

Providing continuous database access during database modification

In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a logging table generator configured to generate a logging table corresponding with an original table targeted for an upgrade, and a control table generator configured to generate a control table configured to store a version identifier for changes logged in the logging table. The computer system can include a change recorder configured to receive an indicator of a change to a record of the original table during execution of at least a portion of the upgrade of the original table, and a key recorder configured to store in the logging table a primary key identifying the record of the original table and the version identifier stored in the control table.

Change data capturing during an upgrade

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.

Software logistics protocols

A computer system includes a shadow system including a shadow program database having a structure defining an upgrade to a structure of an original program database on an original system, and having data defining an upgrade to data of the original program database on the original system. The computer system includes a database replicator configured to perform at least one transfer of data from a portion of the original user database into the structure of the shadow user database during an uptime of the original system and configured to perform a final transfer of data from the portion of the original user database into the structure of the shadow user database during a downtime of the original system, and an upgrade transfer module configured to replace the portion of the original user database with the shadow user database after the final transfer of data has been performed.

Shadow system mirroring of an original system during uptime of an upgrade process

The current subject matter provides a method to upgrade an individual tenant by moving the individual tenant from a source computing system that implements an older software version to a target computing system that implements a newer software version. The movement of the individual tenant incorporates a movement of customer-specific data associated with the moved tenant. Instead of just upgrading a same multi-tenancy computing system implementing the tenant that needs to be upgraded, a new (target) multi-tenancy computing system implementing a newer software version is installed such that this tenant can be moved from the (source) multi-tenancy computing system to the new (target) multi-tenancy computing system. The data associated with the moved tenant is adjusted to new structures associated with the newer software version.

Tenant move upgrade

Example systems and methods of upgrading a single-database, multiple-tenant software system are presented. In one example, a target database schema for a target version of the software system is created. For each tenant of a current database schema for a current version of the software system, a current state of the data corresponding to the tenant in the current database schema is captured. The data corresponding to the tenant is transitioned from the current database schema to the target database schema. The tenant in the target database schema is tested to verify the tenant. If the tenant in the target database schema is verified, the tenant in the target database schema is opened for users. If not verified, the tenant in the current database schema is restored using the captured state.

Growing community of inventors

Karlsruhe, Germany

Andrey Engelko