Abstract: Techniques for metadata-driven rapid adapter building (RAB) are disclosed, including: receiving, by an RAB framework, a function call from a third-party application; obtaining, by the RAB framework, a metadata document that defines an adapter between a server-side runtime and the third-party application; determining that the metadata document includes one or more metadata fields that map the function call to one or more software development kit (SDK) functions exposed by the server-side runtime; responsive to receiving the function call and based on the one or more metadata fields, executing the one or more SDK functions exposed by the server-side runtime.

Abstract: In accordance with an embodiment, described herein are systems and methods for (a) determining workflow characteristics for use with an integration cloud service or other computing environment; and (b) providing a marketplace that employs a conversational interface to guide users in selecting and retrieving integration artifacts, for example workflows or other assets, to address particular needs. A collection service can receive an indication of an integration archive that defines a business workflow or integration flow, wherein a characteristics server can then extract and persist the characteristics associated with the workflow, for subsequent use in providing a determination of workflows. In accordance with an embodiment, a digital assistant can be employed to allow discovery of workflows by building a discovery criteria based on a knowledge of characteristics associated with various business workflows or integration flows, and through interactive conversations by a user with the digital assistant.

Abstract: Embodiments described herein are generally related to cloud computing environments, and are particularly directed to systems and methods for dynamic throttling of workflows based on integrated applications. An integration cloud or platform-as-a-service (iPaaS) platform can enforce fixed limits for flows, and evolve the limits behavior based on responses from target applications, for example as sent within documented headers in their responses.

Abstract: In accordance with an embodiment, described herein are systems and methods for (a) determining workflow characteristics for use with an integration cloud service or other computing environment; and (b) providing a marketplace that employs a conversational interface to guide users in selecting and retrieving integration artifacts, for example workflows or other assets, to address particular needs. A collection service can receive an indication of an integration archive that defines a business workflow or integration flow, wherein a characteristics server can then extract and persist the characteristics associated with the workflow, for subsequent use in providing a determination of workflows. In accordance with an embodiment, a digital assistant can be employed to allow discovery of workflows by building a discovery criteria based on a knowledge of characteristics associated with various business workflows or integration flows, and through interactive conversations by a user with the digital assistant.

Abstract: The present embodiments relate to adaptive throttling with tenant-based concurrent rate limits. A first exemplary embodiment provides a method for adaptive throttling with tenant-based concurrent rate limits. The method can include a computing device receiving a request directed to a first tenant of a multi-tenant cloud infrastructure system. The first tenant being granted access to a limited processing capacity to process a limited number of requests. The computing device can further determine whether the multi-tenant cloud infrastructure system is in stress. The computing device can further permit the first tenant access to the additional processing capacity to process a number of requests greater than the limited number of requests.

Abstract: Systems and methods for supporting rollback of changes made to target systems via an integration platform. Systems and methods can support reverting changes made to target applications via an integration platform (e.g., integration platform as a service (iPaaS)) with the help of a rollback activity. In order to aid the development and design of integration orchestrations, the integration platform can provide suggested rollback actions. In case of a failure in integration runtime, this rollback activity will revert changes made to the target applications prior to the point of fault. This helps ensure that systems remain in consistent state.

Abstract: Systems and methods for supporting rollback of changes made to target systems via an integration platform. Systems and methods can support reverting changes made to target applications via an integration platform (e.g., integration platform as a service (iPaaS)) with the help of a rollback activity. In order to aid the development and design of integration orchestrations, the integration platform can provide suggested rollback actions. In case of a failure in integration runtime, this rollback activity will revert changes made to the target applications prior to the point of fault.

Abstract: In accordance with an embodiment, described herein is a system and method for providing a universal security handler for use with a cloud-based integration platform. A universal security configuration interface can be provided to capture custom values, syntaxes, and/or grammars for a common set of security properties for different implementations of a particular authorization flow. The captured information can be used by a plurality of software components to create a custom security provider, which includes information needed for obtaining an access token from a specified cloud service provider. The security provider, which also includes methods for performing each step of the authorization flow, can be provided to a security processor configured to handle exchanges between the universal security configuration interface and the specified cloud service provider. The system enables the cloud-based integration platform to integrate with a plurality of third-party cloud services without writing additional code.

Abstract: According to an aspect of the present disclosure, a query builder sends to a node in a cloud, a request for meta-data related to objects, and in response receives from the node, the meta-data specifying information related to objects exposed by the node. Upon receiving from a user a partial query and a current edit location during building of a corresponding complete query, the query builder determines, based on the received meta-data, the current edit location, and the partial query, a list of identifiers which are potential candidates for insertion at the current edit location. The query builder then displays the list of identifiers to the user, and receives a selection of an identifier from the displayed list. The query builder incorporates the selected identifier in the partial query at the current edit location to form a further developed query.

Abstract: In accordance with an embodiment, described herein is a system and method for providing a universal security handler for use with a cloud-based integration platform. A universal security configuration interface can be provided to capture custom values, syntaxes, and/or grammars for a common set of security properties for different implementations of a particular authorization flow. The captured information can be used by a plurality of software components to create a custom security provider, which includes information needed for obtaining an access token from a specified cloud service provider. The security provider, which also includes methods for performing each step of the authorization flow, can be provided to a security processor configured to handle exchanges between the universal security configuration interface and the specified cloud service provider. The system enables the cloud-based integration platform to integrate with a plurality of third-party cloud services without writing additional code.

Abstract: Provided is a device for securing an essential component, in particular a lock cylinder, a lock cylinder catch or the like, of a handle of a motor vehicle, the device having a carrier, which can be secured on the inside to a movable part, in particular to a lid, tailgate or door. A blocking unit is arranged on the carrier and comprises movable gear elements, by means of which the blocking unit can be moved between a blocking position and a release position, the component being located in a detached manner in the carrier in the release position and the component being held securely on the carrier in the blocking position.

Abstract: According to an aspect of the present disclosure, a query builder sends to a node in a cloud, a request for meta-data related to objects, and in response receives from the node, the meta-data specifying information related to objects exposed by the node. Upon receiving from a user a partial query and a current edit location during building of a corresponding complete query, the query builder determines, based on the received meta-data, the current edit location, and the partial query, a list of identifiers which are potential candidates for insertion at the current edit location. The query builder then displays the list of identifiers to the user, and receives a selection of an identifier from the displayed list. The query builder incorporates the selected identifier in the partial query at the current edit location to form a further developed query.

Abstract: Provided is a device for securing an essential component, in particular a lock cylinder, a lock cylinder catch or the like, of a handle of a motor vehicle, the device having a carrier, which can be secured on the inside to a movable part, in particular to a lid, tailgate or door. A blocking unit is arranged on the carrier and comprises movable gear elements, by means of which the blocking unit can be moved between a blocking position and a release position, the component being located in a detached manner in the carrier in the release position and the component being held securely on the carrier in the blocking position.