Abstract: At an Operational Insights and Development Recommendation (OIDR) system, development artifacts from a central artifacts repository are received. At the OIDR system, statistical data from a central data analysis infrastructure is received. The statistical data is retrieved from application systems running software created from the development artifacts, and the statistical data is correlated with the development artifacts. Data insights and recommendations based on the correlated statistical data and development artifacts are provided by the OIDR system to an enhanced integrated development environment (IDE). Recommendations are derived using an analysis algorithm.

Abstract: A request from a User for a Service is received by an Application. An Open Authorization (OAUTH) Client of the Service is requested from a Service Instance of the Service. A copy OAUTH Client of the Service specific to the User is provided based on a clone OAUTH Client associated with the Service Instance. A Token is obtained to access the Service by providing the copy OAUTH Client to a User Account and Authorization (UAA) entity. Access to the Service is obtained by providing the 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: An application is defined including an application implementation and a deployment application including design-time artifacts. Persistence artifacts are modeled as content for the deployment application. Persistence artifacts needed at runtime are generated using implemented software code for the application implementation and the generated persistence artifacts are added to the modeled persistence artifacts. The defined application is added to a multi-tenancy-enabled multi-target application (MTA) associated with the defined application and comprising a set of modules. The MTA is stored into a versioned artifact repository. An MTA deployment service is triggered to deploy the MTA and the application associated with the MTA is started.

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: According to some embodiments, a system and method are provided to automatically rename database objects. The system receives a rename file comprising (i) a plurality of database object names representing a plurality of database objects associated with an application and (ii) an identity assignment associated with one or more of the plurality of database objects. One or more of the plurality of database objects are automatically renamed based on (i) a currently installed version of the application, (ii) a version of the application associated with the rename file and (iii) the identity assignment associated with the one or more of the plurality of database objects.

Abstract: Registering a Service Broker and an Instance Manager Broker with a Controller. Receiving a request at the Controller from a Deployer associated with an Application to bind a Service Instance of an Instance Manager to an Application. Forwarding the received request from the Controller to the Instance Manager Broker to instantiate the Service Instance of the Instance Manager. Forwarding credentials returned by the Instance Manager Broker from the instantiated Service Instance of the Instance Manager from the Controller to the Deployer.

Abstract: An IoT data packet of IoT data in a first data format is received over a distributed system from an Internet of Things (IoT) device. A determination is made that a second different data format of at least some of the IoT data is being used by at least one application by using an IoT data model of an IoT persistency service storing the IoT data in different data formats supporting different applications. A transformation rule in the IoT data model is used to transform the IoT data packet in the first data format to the second different data format. The IoT data packet in the second different data format is stored in the IoT persistency service.

Abstract: During a first delta time period, monitoring a growth in a number of records and determining a highest-growth partition in the database. The highest-growth partition is divided into subranges. During a second delta time period, a growth is monitored for each subrange. For the subrange with a greatest growth, the subrange is subdivided into sub-subranges and a growth determined for each sub-subrange. The monitoring and the determining is repeated and further subdivisions made of divisions having the highest growths until growths have been recorded for N delta time periods. For each of the N delta time periods, weighted growths are determined for each subdivision. Expected record counts are determined for each of the divisions that are expected for a subsequent time period spanning the N delta time periods. Based on the expected record counts, a partition split point within the highest-growth partition is determined, and the highest-growth partition is split into two partitions.

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: 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: A Tenant request to subscribe to an Application is received. A Service that the Application consumes is determined. The Tenant is determined to be new to the Service. In response to determining the Tenant is new, a subscription of the Tenant is provided in the Service, and the Application is added to the subscription.

Abstract: A first instance of a deployer application is executed in a server mode. The deployer application is configured to deploy service instances for a multi-tenant application. A first onboarding request is received for a first tenant for the multi-tenant application. A first service instance for the first tenant is created, in response to the first onboarding request. A first request to deploy artifacts to the first service instance is received, by the first instance of the deployer application. The artifacts are deployed, by the first instance of the deployer application, to the first service instance.

Abstract: Various examples are directed to systems and methods for configuring an application that uses a plurality of microservices. A distributed configuration deploy service (DCDS) may generate a first set of microservice configuration parameter values for a first microservice of the plurality of microservices based at least in part on a first microservice configuration model for the first microservice and at least in part on a second configuration model for a second microservice of the plurality of microservices. A configuration application programming interface (API) may determine that the first set of microservice configuration parameter values do not conflict with first live data at the first microservice. The configuration API may also lock the first microservice; apply the first set of microservice configuration parameter values to the first microservice; and release the locking of the first microservice.

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 request from a User for a Service is received by an Application. An Open Authorization (OAUTH) Client of the Service is requested from a Service Instance of the Service. A copy OAUTH Client of the Service specific to the User is provided based on a clone OAUTH Client associated with the Service Instance. A Token is obtained to access the Service by providing the copy OAUTH Client to a User Account and Authorization (UAA) entity. Access to the Service is obtained by providing the Token.

Abstract: A request is received at a service manager from a service broker proxy or a service manager aware service registry to create a service instance. Creation of a service instance is requested from a service broker. Details of the created service instance are stored within the service manager. A success or failure status is returned to the service broker proxy.

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: Methods, systems, and computer program products for transferring business objects and business object data are described. A business object from a first networked service may be obtained. The business object may be stored in a cloud business object broker and may be transferred to a second networked service. The business object may be deleted from the cloud business object broker after a transferal from the cloud business object broker to the second networked service.

Abstract: Proxy-based access occurs between a cloud database and analytical client tool, without requiring a separate intervening application server. A client proxy (tool side) communicates exclusively with a server proxy (database side). In response to a connect request in a database protocol (e.g., Structured Query Language—SQL) received from the tool by the client proxy, the server proxy is caused to initiate an authentication process (e.g., using Security Assertion Markup Language—SAML) with an Identity Provider (IdP). The client proxy intercepts and extracts a security token from the IdP in order to establish a tunnel with the server proxy. Upon ultimately receiving the connect command through the tunnel, the server proxy replaces an end-user credential (recognized by the tool but meaningless to the database) with the security token in order to establish a technical user and a query session context that can be recognized by the database.