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:
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:
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.
Abstract:
The present disclosure involves systems, software, and computer implemented methods for generating an example database, including sample code, to provide custom code migration suggestion. In one example, a method may include identifying a set of modified objects at a platform system with which code in a first development system is associated, determining at least one development artifact in the code of the first development system dependent upon at least one of the modified objects, monitoring changes to the code of the first development system for changes to development artifacts dependent upon the at least one modified object, and in response to determining that a change to a particular development artifact dependent upon the at least one modified object, automatically storing information associated with the change to the particular development artifact into the example database which stores examples of changes to code associated with the set of modified objects.
Abstract:
A business software customer deploying both on-premises and cloud-based applications can be provided with an automatically-generated, customer-tailored release master plan for a hybrid networked business solution that can include specific information and instructions tailored to the business software customer's customer-specific system landscape.
Abstract:
The disclosure generally describes methods, software, and systems for re-architecting an existing software product provided as a service. A user input specifying current databases used for an old software product version is received. The user input includes a definition of a target persistency layout including databases assigned for storing a new software product version, the old software product version including one or more database tables and the new software product version including an adjustment to the one or more database tables to generate one or more target database tables. Sizes of the one or more database tables are read from a catalog of a database. A migration assessment of the new software product version is generated based on the sizes of the one or more database tables. A migration test of the one or more database tables is executed using the migration assessment to generate migration test results. An updated adjustment to the one or more database tables is provided based on the migration test results.
Abstract:
In an implementation of a computer-implemented method: to create extracted data records, an extract filter is instructed to extract relevant data records from log messages of two runs of a software pipeline. To create diff records using the extracted data records, a diff filter is instructed to compare and identify differences in messages between the two runs, where the diff records are amended with labeled data status information of a software pipeline run the extracted data records have been taken from. A recommendation engine is instructed to execute a machine-learning model training with the diff records. The recommendation engine is called to analyze the diff records for a failure-indicator. A determination is made that a failure causing the failure-indicator has been corrected in a later run of the software pipeline. A change is identified in a configuration or version of a software application associated with a correction. A failure-indicator-solution combination is generated.
Abstract:
Implementations include a schema stack management system that enables zero-downtime during execution of maintenance procedures on application systems having schema stacks including one or more customer-provided schema extensions.
Abstract:
Systems and methods include reception of a first service call from a first service at a second service, generation, at the second service, of a response to the first service call, determination, at the second service, of an amount of hardware resources consumed by the second service during generation of the response to the first service call, generation, at the second service, of a first resource consumption token identifying the amount of hardware resources consumed by the second service during generation of the response to the first service call, determination of a first identifier of a type of hardware on which the second service is executing, and return of the response, the first resource consumption token and the first identifier of the type of hardware to the first service.
Abstract:
In an implementation, a shutdown coordinator sends an instruction to a router to no longer assign new sessions to an application instance, where the application instance is to be shut down. The shutdown coordinator sends a request to the application instance to export associated sessions for handover to a new application instance. The shutdown coordinator receives an indication from the application instance that no further requests can be processed by the application instance since all associated sessions have been exported to an external session storage. The shutdown coordinator instructs the router to redirect requests to the application instance to the new application instance. The shutdown coordinator shuts down the application instance. The shutdown coordinator deletes remaining sessions of all associated sessions from the external session storage after a defined timeout period.