Sap Se

Sap Ag

Andreas Jahr

Volker Driesen

Andrey Engelko

Steffen Koenig

Oleg Koutyrine

Nicolai Jordt

Dennis Koerner

Christoph Luettge

Fabrizio Muscarella

Michael Decker

Manikandan Rajasekar

Stefan Vormbrock

Georg Storz

Wolfgang Degenhardt

Ralf Kurt Mueller

Markus Gebhard

Methods, systems, and computer-readable storage media for defining a metadata model representative of the software solution, the metadata model including a global model, a to-be model, and an as-is model, updating, by a first model updater, the global model to include metadata generated during execution of a release pipeline associated with the software solution, updating, by a second model updater, the to-be model to include metadata generated during execution of a deployment pipeline associated with the software solution, populating the as-is model with metadata generated as a result of deployment of the software solution to the one or more cloud platforms, the as-is model identifying versions of components of the software solution and respective deploy targets, to which the components are deployed to, and executing at least one management operation on the software solution at least partially based on the metadata model.

Metadata model and use thereof for cloud native software systems

Methods, systems, and computer-readable storage media for receiving, by a content transfer service of a content management system and from a source system, a first content file comprising first content and first content metadata, the first content metadata being stored in a first format, processing the first content file using a set of metadata retrieval definitions to extract file-type-specific metadata from the first content metadata and map at least a portion of the file-type-specific metadata to a first uniform content metadata file having a second format that is different from the first format, each metadata retrieval definition comprising a computer-executable, declarative procedure, and transferring, by the content transfer service, the first content file and the first uniform content metadata file to a target system, the target system consuming the content at least partially based on the first uniform content metadata file.

Content metadata service for lifecycle management of digital content

Methods, systems, and computer-readable storage media for receiving a first identifier associated with an incident arising in a first software system, transmitting a first query to an architecture metadata repository, receiving, from the architecture metadata repository, first architecture metadata at least partially including a first architecture graph that is a computer-readable data representation of the first software system and cross-link data representative of one or more dependencies between the first software system and a second software system, transmitting a second query to the architecture metadata repository, the second query including a second identifier assigned to the second software system, receiving second architecture metadata representative of the second software system, and displaying at least a portion of the first architecture metadata and at least a portion of the second architecture metadata in a display.

Architecture-based root cause analysis

Methods, systems, and computer-readable storage media for central management of multiple landscapes using a central management platform that is absent user management functionality.

Central management platform without user management

Methods, systems, and computer-readable storage media for providing a transition service broker, the transition service broker including a service registry proxy, and a service registry, the service proxy registry registering service proxies, each service proxy enabling interaction between at least one core component of a legacy core, and one or more external services, the service registry registering services available for consumption by core components of the legacy core, each external service of the external services including a service facade that maps between a legacy architecture, and the service, during a transition period between the legacy architecture, and the microservices-based architecture: establishing a connection between the at least one core component, and an external service through a service proxy, and receiving input from the external service through the connection, the input being processed by the at least one core component during execution of the software product in the legacy architecture.

Transition architecture from monolithic systems to microservice-based systems

Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for receiving a request for at least one software artifact stored within a software repository of one or more software repositories of an enterprise, the request being received from a continuous delivery (CD) pipeline associated with an on-premise landscape of a customer, and including a user identifier, and at least one uniform resource locator (URL) indicating a location of a respective software artifact within the software repositories, providing, the request to a repository proxy of the enterprise, the repository proxy including a transparent, terminating network proxy, providing, by the repository proxy, an audit log entry associated with the request, the audit log entry being recorded in an audit log, and transmitting, by the repository proxy, a response to the request, the response including the software artifact retrieved from the software repositories based on the at least one URL.

Repository-based shipment channel for cloud and on-premise software

Systems and methods to manage software change process orchestration are provided. In example embodiments, an indication to initiate a software change process is received. A process required to be performed for the software change process is identified in response to receiving the indication. Using a uniform software logistic protocol capable of accessing tools across different platforms and environments, a tool mapped to the process required to be performed for the software change process is triggered to be executed.

Software change process orchestration in a runtime environment

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

Systems and methods to provide integrated incident management for hybrid landscapes are provided. In example embodiments, an incident ticket is received, at a communication hub, from a first component of a first landscape indicating an incident. A second component in a second landscape is determined to which to route incident information including the incident ticket. The determination of the second component is based on an attribute extracted from the incident ticket. The incident information is transmitted to the second component by the communication hub. A solution for the incident ticket is received from the second component based on the second component having the solution or is received from a component of a service backbone based on the component of the service backbone having the solution by the communication hub, and the solution is forwarded to at least one of the first component or the second component.

Integrated incident management for hybrid landscapes

An upgrade procedure for an application system without downtime is presented. The upgrade procedure includes a mix of a rolling upgrade of application servers, shadow systems, and record and replay mechanisms that employ transformation and locking, for the upgrade of the applications on the application system. Application servers are upgraded one after another. A target version of the system is simultaneously added to the original system and a shadow, or target, system. Data changes are not only carried out in the original system, but are also carried out in the target system, so that a customer realizes no downtime for their data requests to the applications.

Multi-version systems for zero downtime upgrades

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

Example systems and methods of database migration optimized by feedback are presented. In one example, a migration of database data from a first to a second database by multiple concurrent processes may be initiated on a computing system. Processing time of at least some of the processes may be monitored during the migration. Based on this monitoring, at least one portion of the database data being migrated by one of the concurrent processes may be segmented into multiple segments, wherein each of the multiple segments may be migrated by a separate one of the concurrent processes. Also, a load on the computing system may be monitored during the migration. Based on this monitoring, a number of the concurrent processes may be adjusted. In other examples, consistency checking for subsequent database migrations may be based on consistency checking results for the current migration.

Feedback optimized checks for database migration

Techniques for integrating software applications include identifying an enterprise application executable in a first computing environment, where the enterprise application is compatible with a first version of a network application executable in a second computing environment so that a first set of functionality of the first version of the network application is exposed through the enterprise application. The features include identifying a second version of the network application executable in the second computing environment. The second version of the network application includes a second set of functionality at least partially distinct from the first set of functionality. The features include delivering an integration component from the second computing system to the first computing system. The integration component includes a non-modifying add-on component to the enterprise application that exposes at least a portion of the second set of functionality of the second version of the network application through the enterprise application.

Growing community of inventors

Karlsruhe, Germany

Andreas Jahr