Abstract: Methods, systems, and computer-readable storage media for determining a sub-set of services, each service in the sub-set of services being in an overload status and having a SSF associated therewith, providing statistics associated with each service in the sub-set of services and relating service call statistics to each API group of a set of API groups, determining a set of sessions based on the service call statistics, each session in the set of sessions associated with at least one service in the sub-set of services having a service call statistic that exceeds a threshold service call statistic, defining an execution group and a waiting group, determining that a session is in the waiting group, and in response, blocking a request of the session from being processed by a service in the sub-set of services, and providing a wait indication to a user associated with the session.

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: Implementations include receiving, by a migration delta analyzer of a software system, an object list including objects accessed by the on-premise application, determining, by the migration delta analyzer, at least one migration option for each object in the object list using a mapping table, receiving, through a user interface, input from a user representing a selection of migration option for each object in the object list, and providing a cloud application based on the selected migration option for each object in the object list.

Abstract: Implementations include receiving, by a migration delta analyzer of a software system, an object list including objects accessed by the on-premise application, determining, by the migration delta analyzer, at least one migration option for each object in the object list using a mapping table, receiving, through a user interface, input from a user representing a selection of migration option for each object in the object list, and providing a cloud application based on the selected migration option for each object in the object list.

Abstract: Methods, systems, and computer-readable storage media for receiving, by a customer cockpit, a toggle notification indicating that an edge feature of an edge component of a hybrid software deployment is to be activated, the toggle notification being received during execution of a process by the edge component, determining, by the customer cockpit, that the process has ended and, in response, triggering an edge controller to toggle the edge feature to an activated state within the edge component, receiving, by a vendor cockpit, an edge confirmation of the edge component that confirms that the edge feature is in the activated state, and at least partially in response to receiving the edge confirmation, triggering, by the vendor cockpit, a tenant controller to toggle a tenant feature to an activated state within a tenant component of the hybrid software deployment.

Abstract: Various examples are directed to cloud platform systems that implement a plurality of cloud components. A first cloud component may receive a zone token. The zone token may comprise a first user identifier indicating a first user and a first zone identifier (ID) indicating a first zone. The first cloud component may receive from a user computing system associated with the zone token a task request indicating a first task. The first cloud component may execute the first task. Executing the first task may include determining a first data unit at the first cloud component associated with the first zone ID, accessing the first data unit, and sending a request message to a second cloud component, the request message comprising the first zone ID, wherein the second cloud component comprises at least one second data unit associated with the first zone ID.

Abstract: A request is received to create a graph database from one or more relational databases. For each relational database, data objects in the relational database are identified. For each data object, a graph data object corresponding to the data object is created. The graph data object is linked to the data object. A set of associated data objects in the relational database are determined, and for each associated data object, an associated graph data object is created if a graph data object corresponding to the data object does not exist. For each created graph data object, a graph data relation object is created that represents a relationship between the graph data object and the associated graph data object. Created graph data objects, associated graph data objects, and graph data relation objects are stored in the graph database. The graph database is provided to one or more applications.

Abstract: Various examples are directed to a cloud platform system that comprises a plurality of cloud platform deployments including a first cloud platform deployment implemented at a first geographic region and a second cloud platform deployment implemented at a second geographic region. An access manager system receives from a user computing device, a user logon request identifying a user. The access manager system also receives, from an identity provider system, group data associated with the user logon request, the group data indicating a first group to which the user belongs. The access manager system determines that a subaccount access map correlates the first group to a first subaccount that is implemented at the first cloud platform deployment. The access manager system also provides the user computing device an indication that the user is authorized to access the first subaccount.

Abstract: Methods and systems are used for providing a generic command line interface to an extensible list of cloud platform services. As an example, a generic command request including a command and command input data is received from a client. A platform service for the command is determined based on command metadata associated with the command. The command input data is mapped to a platform service application programming interface (API) associated with the platform service based on the command metadata associated with the command. The platform service API is called based on the mapping. Response data from the platform service API is mapped to command output data in a generic command response based on the command metadata associated with the command. The generic command response is transmitted to the client.

Abstract: In an example embodiment, a solution is provided that allows a user to submit a document. Information can be obtained from the document using optical character recognition (OCR) or other techniques. This information can then be used to identify one or more workflows that pertain to the document. The one or more workflows may be ranked using machine learning techniques and presented to the user. Once the user selects a desired workflow, the information obtained from the document can then be used to automatically complete at least a portion of the workflow, for example by prefilling one or more fields in a form.

Abstract: In an example embodiment, first a system is provided that enables tests created by a second entity to run with first entity data and configurations. A test module is able to assess test results with dynamic input (e.g., rule-based assessments). Second, a system is provided to run and test these test modules on the first entity system with first entity configuration and let the first entity define the test input and interpret the test results. This is not performed on all available tests, but only on the tests that are related to the change to be implemented.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for issue resolution based on actual use of configuration parameters. Actions include receiving, from a monitoring system, an incident report including a description of an issue of a process and a context of the issue, retrieving features associated with the issue based on the context of the issue, processing the features to extract a set of solutions that were executed to resolve associated issues, processing the set of solutions to generate a solution for the issue, comparing an accuracy of the solution with a solution implementation threshold, and implementing the solution to resolve the issue.

Abstract: Methods, systems, and computer-readable storage media for determining, by an application instance, that first data is to be requested, transmitting, by a total outage compensator of the application instance, one or more requests for the first data to one or more peer application instances, receiving, by the total outage compensator, a response to a request for the first data, the response including the data, and executing, by the instance of the application instance, at least one function based on the first data.

Abstract: Methods, systems, and computer-readable storage media for determining an initial distribution based on a set of survey boundaries and historical O-data, the historical O-data being generated through execution of a computer-implemented service, the historical distribution including a first set of parameter ranges and a second set of parameter ranges defining a set of range cells, adjusting one or more parameters ranges of at least one of the first set of parameter ranges and the second set of parameter ranges, determining an adjusted distribution defining a range space for a computer-based survey, receiving X-data from a set of users participating in the computer-based survey, the X-data including responses of users in the set of users provided to the computer-based survey, providing a set of X-data to O-data range vector correlations, and executing analytics of the computer-implemented service based on the set of X-data to O-data range vector correlations.

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: Methods, systems, and computer-readable storage media for monitoring, by a LML plug-in to a first service executed within a first datacenter, accesses to provide access data representative of the accesses to a data record stored in the first datacenter, the accesses including local accesses executed by the first service and remote accesses executed by a second service executed within a second datacenter, receiving, by a LML instance executed within the first datacenter, the access data from the LML plug-in to the first service, determining, by the LML instance, a set of metrics for the data record based on the local accesses and the remote accesses in a first time period, and selectively executing a transfer process based on the set of metrics to copy the data record to the second datacenter.

Abstract: A request is received to create a graph database from one or more relational databases. For each relational database, data objects in the relational database are identified. For each data object, a graph data object corresponding to the data object is created. The graph data object is linked to the data object. A set of associated data objects in the relational database are determined, and for each associated data object, an associated graph data object is created if a graph data object corresponding to the data object does not exist. For each created graph data object, a graph data relation object is created that represents a relationship between the graph data object and the associated graph data object. Created graph data objects, associated graph data objects, and graph data relation objects are stored in the graph database. The graph database is provided to one or more applications.

Abstract: Methods, systems, and computer-readable storage media for receiving, from a first component and by a second component in a cloud platform, a call, a token, and a first client certificate, determining, by the second component, a first client identifier associated with the first component, and determining, by the second component, that the first client identifier is included in a manifest of the token, the manifest defining at least a portion of a communication path between components within the cloud platform, and in response: executing functionality responsive to the call.

Abstract: Implementations include receiving, by a migration delta analyzer of a software system, an object list including objects accessed by the on-premise application, determining, by the migration delta analyzer, at least one migration option for each object in the object list using a mapping table, receiving, through a user interface, input from a user representing a selection of migration option for each object in the object list, and providing a cloud application based on the selected migration option for each object in the object list.

Abstract: A mesh-type scaler is selected for performing overall mesh-wide scaling of a microservices mesh. The microservices mesh is scaled with the mesh-type scaler and one or more mesh scaling rules to generate a predicted value for a monitoring parameter of one or more monitoring parameters. A single-service-type scaler is selected. The monitoring parameter is measured with the single-service-type-scaler to generate a measured value. For an individual service associated with the microservices mesh, a target value is calculated for the monitoring parameter using the predicted value and the measured value. The target value is compared against a defined threshold to generate a scaling value used to determine if scaling is needed with respect to the individual service.