Abstract: Techniques for webhook registration are disclosed, including: receiving, by an integration platform, a metadata document associated with a producer, wherein the metadata document describes (a) a set of conditions for identifying webhook validation requests and (b) a set of one or more operations for validating webhook validation requests; instantiating, by the integration platform, an adapter based on the metadata document; determining, by the integration platform using the adapter, that a request from a producer satisfies the set of conditions for identifying webhook validation requests; responsive to determining that the validation request satisfies the set of conditions for identifying webhook validation requests: executing the set of one or more operations for validating webhook validation requests, to validate a registration of a consumer with the producer.

Abstract: Aspects of the present disclosure provide security compliance in integration connectors. In one embodiment, a system receives a definition data specifying implementation details of an integration connector. The system checks by inspecting the definition data, whether the implementation details are in compliance with a set of security rules and computes a security score for the integration connector based on the compliance determined by the checking. According to an aspect, the system displays to a user, the security score for the integration connector along with a set of warnings about the compliance. According to another aspect, the system monitors a run-time operation of the integration connector. In response to identifying, based on the monitoring, that a security rule of the set of security rules has been violated, the system stops the operation of the integration connector and sends an error indicating that the security rule has been violated.

Abstract: Aspects of the present disclosure provide security compliance in integration connectors. In one embodiment, a system receives a definition data specifying implementation details of an integration connector. The system checks by inspecting the definition data, whether the implementation details are in compliance with a set of security rules and computes a security score for the integration connector based on the compliance determined by the checking. According to an aspect, the system displays to a user, the security score for the integration connector along with a set of warnings about the compliance. According to another aspect, the system monitors a run-time operation of the integration connector. In response to identifying, based on the monitoring, that a security rule of the set of security rules has been violated, the system stops the operation of the integration connector and sends an error indicating that the security rule has been violated.

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.