Abstract: Methods, systems, and computer-readable storage media for executing, by a target system deploy tool, a first portion of a target-side maintenance procedure on the target system, halting execution of the first portion of the target-side maintenance procedure, executing, by a source system deploy tool, a source-side maintenance procedure on the source system, wherein, during execution of the source-side maintenance procedure, table structure change events are recorded in a source-side orchestration table, reading, by a replicator, the table structure change events recorded in the source-side orchestration table, writing, by the replicator, the table structure change events to a target-side orchestration table, and executing, by the target system deploy tool, a second portion of the target-side maintenance procedure on the target system, at least in part, by performing the table structure change events of the target-side orchestration table on one or more tables of the target system.

Abstract: A request is received from a deployer associated with an application to create an instance broker service instance. A request is received from the deployer to bind the instance broker service instance to the application. Instance broker credentials associated with the instance broker service instance are received and provided to the application. The application uses the instance broker credentials to access the instance broker service instance and determines whether to create a new service instance using the instance broker service instance.

Abstract: A platform's central instance manager (IM) receives microservice requests issued to a common application shared between various tenants. Embodiments function to co-locate within a same database, the persistence containers of different microservice instances of a specific tenant. The central IM associates a corresponding tenant identifier with microservice request instances created. Referencing this assigned tenant identifier, the central IM maintains an external configuration file comprising a mapping of services (m) and tenants (n), to relevant persistence container service instances. Such mapping permits the allocation of tenant-specific microservice data for storage within persistence containers of a particular database. This co-location of data promotes flexibility, allowing tenants to furnish database structures tailored to their individual needs.

Abstract: A system includes determination, at a first computing system, of the creation of a first user account, the first user account associated with a first username, a first identity store and a first person, determination, at the first computing system, of a first identifier uniquely identifying the first person, storage, at the first computing system, of a first association between the first username, the first identity store and the first identifier, reception, at a second computing system, of an indication of activity, the indication including the first username and the first identity store, determination, at the second computing system, the first identifier based on the first username, the first identity store and the stored first association, and creation, at the second computing system, of a log entry associating the activity with the first identifier.

Abstract: Methods, systems, and computer-readable storage media for providing a set of key-range-ranges associated with an application, the set of key-range-ranges defining a plurality of key ranges, each key-range-range being assigned to a respective role, determining that a key range is to be defined for the application by a user having a role, determining whether the key range conforms with the set of key-range-ranges and respective roles, accepting the key range at least partially in response to determining that the key range conforms with the set of key-range-ranges and respective roles, and initiating deployment of the application including the key range to a production system.

Abstract: A system may include a shared storage data store containing a first version of entities with original content and a local tenant storage data store to contain information associated with a tenant's application server. A database interface agent may enter a copy-on-access mode and maintain materialization and modification flags. The agent may then initiate an upgrade process during which the first version of the entities are utilized by the application server. The agent may then enter a copy-on-write mode and delete, from the local tenant storage data store, entities having flags that indicate the table was migrated but did not receive customer data. The structure of the remaining entities may then be updated in view of the structure of the second version of the entities. Finally, the content of the entities may be updated in view of the content of the second version of entitles and previously received customer data.

Abstract: A credential change management platform may, from a time period T1 to T2: deny access by remote client devices that submit credentials other than the prior or new credentials and, as a result of the denial, increment a lock-out counter, and allow access by devices that submit either the prior or new credential. From T2 to T3, the platform may: deny access by devices that submit credentials other than the prior or new credential and, as a result of the denial, increment the lock-out counter, deny access by devices that submit the prior credential without incrementing the lock-out counter, and allow access by devices that submit the new credential. After T3, the platform may: deny access by devices that submit credentials other than the new credential and, as a result of the denial, increment the lock-out counter, and allow access by devices that submit the new credential.

Abstract: Methods, systems, and computer program products for managing software changes and upgrades are described. Software change information of a plurality of changed objects of a software package is obtained, the software change information comprising a name of an object being changed and a type of the object being changed. An object dependency graph for the object is generated, the object dependency graph providing a data structure for identifying dependency relationships of the object being changed, and usage statistics for the object and the object type are retrieved. An identity of a module impacted by a software change is determined based on the data structure and an overall rating of the software change is generated.

Abstract: Methods, systems, and computer-readable storage media for executing, by a target system deploy tool, a first portion of a target-side maintenance procedure on the target system, halting execution of the first portion of the target-side maintenance procedure, executing, by a source system deploy tool, a source-side maintenance procedure on the source system, wherein, during execution of the source-side maintenance procedure, table structure change events are recorded in a source-side orchestration table, reading, by a replicator, the table structure change events recorded in the source-side orchestration table, writing, by the replicator, the table structure change events to a target-side orchestration table, and executing, by the target system deploy tool, a second portion of the target-side maintenance procedure on the target system, at least in part, by performing the table structure change events of the target-side orchestration table on one or more tables of the target system.

Abstract: Methods, systems, and computer program products for accessing a database element are described. A local schema comprising a table link is created and the table link is used to access a database table via a persistency interface.

Abstract: Methods, systems, and computer-readable storage media for determining at least one constraint that is to be changed as a result of a maintenance procedure that is to be performed on an application that interacts with a database system, identifying a data value of a table stored in the database as violating the at least one constraint, the table having a start release structure, moving a data object including the data value to a quarantine table that include the start release structure, editing the data value within the quarantine table to provide an edited data value that does not violate the at least one constraint, and moving the data object including the edited data value to the table, after the maintenance procedure has been performed.

Abstract: Embodiments allow identifying unique locations, proximity, and constraints of various individualization resource units in a data center. A plurality of processes may compete for available resources (e.g., CPU, network bandwidth, memory) in a shared environment, which may be virtualized (e.g., comprising host, VM, container, application server instance resource units). A scheduling infrastructure determines individualization unit locations according to an identifier reflecting resource hierarchies. For each process, the data sending infrastructure sends location data as an ID stack to a central monitoring instance for analysis. That central monitoring instance can reference the resource location information to identify process proximity and competition for resources constraining process performance. Resource location information in the form of coordinates provided by the ID stack, offer valuable information regarding resource consumption and other information relevant for process monitoring.

Abstract: Methods, systems, and computer-readable storage media for providing a set of key-range-ranges associated with an application, the set of key-range-ranges defining a plurality of key ranges, each key-range-range being assigned to a respective role, determining that a key range is to be defined for the application by a user having a role, determining whether the key range conforms with the set of key-range-ranges and respective roles, accepting the key range at least partially in response to determining that the key range conforms with the set of key-range-ranges and respective roles, and initiating deployment of the application including the key range to a production system.

Abstract: A first component originally has a persistency decoupled from a persistency of a second component. The second component requires a table from the persistency of the first component. The first component is assigned a first database schema and the second component is assigned a second database schema. A table link is created in the second database schema of the second component, wherein the table link refers to the required table from the first database schema of the first component.

Abstract: A Proxy Service Broker on a Hoster Platform as a Service (PaaS) receives a request for a Service Catalog including PaaS services available from a Partner PaaS. Using the Proxy Service Broker, creation of an instance of a Partner PaaS service selected from the Service Catalog is initiated. Using the Proxy Service Broker, a call is transmitted to a Partner Service Broker on the Partner PaaS to create the instance of the Partner PaaS service executing on the Partner PaaS. An Application is deployed on the Hoster PaaS to consume the instance of the Partner PaaS service. The deployed Application is bound with the instance of the Partner PaaS service and directly consumes the bound Partner PaaS service.

Abstract: An Open Authorization (OAuth) Client Secret of an application associated with a Multi-Tenant Application (MTA) deployed in a cloud-computing environment if read with a Fiori Launchpad (FLP) Deployer. The FLP Deployer writes, as content to a FLP Repository, the OAuth Client Secret and FLP Config data for the application read from a FLP Config data store. An App Router/shared FLP (App Router/FLP) accesses the FLP Repository to read content and OAuth Client Secrets for the application that has deployed to the App Router/FLP. A User Account and Authentication (UAA) service associated with the App Router/FLP is accessed to fetch an authorization token for a user after receiving a user connection to the App Router/FLP. An original user authorization token obtained for the user is exchanged with an application-specific authorization token. User interface elements displayed in the FLP are filtered based on scopes read from the exchanged application-specific authorization token.

Abstract: A big data database may store information to be used to generate results of aggregation queries. An aggregation query platform may include an aggregation query broker that receives an aggregation query from a remote user interface associated with a user and evaluates the aggregation query to determine if the aggregation query qualifies to be designated as a live query. The aggregation query platform may also include a dynamic aggregation engine to, if the aggregation query is designated as a live query by the aggregation query broker, store an indication of the aggregation query and automatically update a local dynamic result of the aggregation query when information in the big data database associated with the live query is changed.

Abstract: A process owner platform may be associated with a cloud embedded big data application and may exchange information with a tenant service executor platform. The process owner platform may establish a process using a process tenant template, the process being associated with public and private data and transmit, to the remote tenant service executor platform, information including the public data (without including the private data). The process owner platform may then receive result data and a process state identifier and establish a virtual process such that it is associated with the public data, the private data, and the result data. The process owner platform may also execute control logic in accordance with the process state identifier to materialize the virtual process into a process or a process tenant template, and the materialized process or process tenant template may associated with the public data, the private data, and the result data.

Abstract: Systems and methods are disclosed for processing data in an application platform. The method may include receiving at runtime a request for data about contributors to at least one document. Data may be determined for a set of contributors to the at least one document. The data for the set of contributors may be transformed based on at least one transformation rule. The transformed data for the set of contributors may be communicated in response to the request. The request may include context data indicating one or more of a user of a computing device, a user session of the computing device, a currently active application on the computing device, and an active screen of the computing device. The determining the data may include identifying, using at least some of the context data, a document associated with the currently active application.

Abstract: A set of features is received. A feature from the set of features includes a feature setting. The feature setting is adjusted based on a user input. A source code portion that corresponds to the adjusted feature setting is transported to a test system. The source code portion is implemented at the test system and evaluated based on the adjusted feature setting. Log data from the test system is analyzed in a feature evaluation UI. The evaluated feature with the implemented source code portion is submitted for deployment from the test system to a production system.