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 is a system and method for behavior injection in a cloud computing platform (cloud platform) or software application, including the use of injection points to modify the operation or behavior of a tenant platform environment. An injection service enables a cloud platform provider to configure software code/behaviors to be injected into cloud platform modules or other components associated with tenants, including mapping, for a tenant-specific globally unique identifier (GUID) associated with a lifecycle activity injection point, a behavior including a platform code or process and metadata that can be used to inject and modify operation of a corresponding module. The described approach enables a cloud platform to expose behavioral aspects of the cloud platform or a software application executing therein, so that they can be controlled or modified in a dynamic manner, from outside of the cloud platform.

Abstract: Described herein are systems and methods for suppressing inbound payload to an integration flow of an orchestration based application integration. The systems and methods described herein can, based upon a scan of an integration, identify and exclude from memory certain portions of one or more payloads that are received at the integration flow.

Abstract: In accordance with an embodiment, described herein are systems and methods identifying capabilities and limitations of an orchestration based application integration. The systems and methods described herein can detect and publish/expose such a set of limitations and capabilities of the adapters/connectors to the integration platform. In this way, such metadata can be used, for example, by a user of an integration system in designing an integration of applications, or in selecting an orchestration, based upon, e.g., the published metadata that indicates the capabilities of the individual adapters/connectors, or the orchestration as a whole (or parts thereof). This way, once an orchestration is active for processing requests, then it can also publish a metadata considering the metadata of involved adapters. This metadata can be used in adjusting requests to an integration.

Abstract: In accordance with an embodiment, described herein are systems and methods for suppressing inbound payload to an integration flow of an orchestration based application integration. The systems and methods described herein can, based upon a scan of an integration, identify and exclude from memory certain portions of one or more payloads that are received at the integration flow.

Abstract: In accordance with an embodiment, described herein is a system and method for behavior injection in a cloud computing platform (cloud platform) or software application, including the use of injection points to modify the operation or behavior of a tenant platform environment. An injection service enables a cloud platform provider to configure software code/behaviors to be injected into cloud platform modules or other components associated with tenants, including mapping, for a tenant-specific globally unique identifier (GUID) associated with a lifecycle activity injection point, a behavior including a platform code or process and metadata that can be used to inject and modify operation of a corresponding module. The described approach enables a cloud platform to expose behavioral aspects of the cloud platform or a software application executing therein, so that they can be controlled or modified in a dynamic manner, from outside of the cloud platform.

Abstract: Systems and methods for intelligent distribution of integration artifacts and runtime requests across geographic regions. Integration Platforms as a Service (iPaaS) are generally networks that span multiple, distinct geographic regions, where customers or tenants can have provisioned a service instance in one or more of these regions. In order to take advantage of the infrastructure presented in an iPaaS system that spans multiple geographic regions (also referred to herein as “regions”) a connection configured in one service instance can be synchronized among other service instances in different regions.

Abstract: In accordance with an embodiment, described herein are systems and methods identifying capabilities and limitations of an orchestration based application integration. The systems and methods described herein can detect and publish/expose such a set of limitations and capabilities of the adapters/connectors to the integration platform. In this way, such metadata can be used, for example, by a user of an integration system in designing an integration of applications, or in selecting an orchestration, based upon, e.g., the published metadata that indicates the capabilities of the individual adapters/connectors, or the orchestration as a whole (or parts thereof). This way, once an orchestration is active for processing requests, then it can also publish a metadata considering the metadata of involved adapters. This metadata can be used in adjusting requests to an integration.

Abstract: An aspect of the present disclosure facilitates third parties/server system to perform batch processing of requests requiring authorization from resource owners for repeat access to resources. In one embodiment, a server system/third party selects a next request from a batch of requests, with the next request requiring a protected resource (hosted on a second party) owned by a owner/user (first party). The server system checks whether an access token is present authorizing access of the protected resource by the server system on behalf of the owner. If the access token is not present, the server system communicates in an offline mode with the owner to receive the access token. The server system then processes the next request by accessing the protected resource using the present/received access token.

Abstract: A system and method for error classification in an integration system. The system and method can receive a request to begin a transaction at the integration system. Additionally, the system and method can invoke an application associated with the request. In response to invoking the application, the system and method can receive a formatted error notification, the formatted error notification comprising at least one of a plurality of error formats. Additionally, the system and method can extract an error message text from the formatted error notification, resulting in a plain text of the formatted error notification. The system and method can also classify, at the error classifier, the formatted error notification based at least on training data and the plain text of the formatted error notification.

Abstract: An intermediary messaging system is provided that facilitates exchange of information between service requestor and service providers. In an embodiment, the intermediary messaging system is configured to receive a request from a client, determine one or more target services for servicing the request, communicate information regarding the request to the identified target services, and communicate responses from the target services back to the client. In certain embodiments, the intermediary messaging service enables a single request received from the client to be translated to multiple requests and to possibly multiple target services without the client having to make multiple requests.

Abstract: Techniques are disclosed for deploying services in a server cluster environment. Certain techniques are disclosed for deploying services to a cluster based on a replication policy that includes a plurality of configurable parameters. In some embodiments, the configurable parameters (also referred to herein as replication factors) can define a number of nodes to which a service is to be deployed, a number of nodes to which a service is to be prepared, and/or a number of nodes to which a service is replicated. Based on the configurable parameters, the replication policy enables users and/or cluster providers to guarantee different levels of performance and/or reliability.

Abstract: A system and method for error classification in an integration system. The system and method can receive a request to begin a transaction at the integration system. Additionally, the system and method can invoke an application associated with the request. In response to invoking the application, the system and method can receive a formatted error notification, the formatted error notification comprising at least one of a plurality of error formats. Additionally, the system and method can extract an error message text from the formatted error notification, resulting in a plain text of the formatted error notification. The system and method can also classify, at the error classifier, the formatted error notification based at least on training data and the plain text of the formatted error notification.

Abstract: An intermediary messaging system is provided that facilitates exchange of information between service requestor and service providers. In an embodiment, the intermediary messaging system is configured to receive a request from a client, determine one or more target services for servicing the request, communicate information regarding the request to the identified target services, and communicate responses from the target services back to the client. In certain embodiments, the intermediary messaging service enables a single request received from the client to be translated to multiple requests and to possibly multiple target services without the client having to make multiple requests.

Abstract: Techniques are disclosed for deploying services in a server cluster environment. Certain techniques are disclosed for deploying services to a cluster based on a replication policy that includes a plurality of configurable parameters. In some embodiments, the configurable parameters (also referred to herein as replication factors) can define a number of nodes to which a service is to be deployed, a number of nodes to which a service is to be prepared, and/or a number of nodes to which a service is replicated. Based on the configurable parameters, the replication policy enables users and/or cluster providers to guarantee different levels of performance and/or reliability.

Abstract: An aspect of the present disclosure facilitates third parties/server system to perform batch processing of requests requiring authorization from resource owners for repeat access to resources. In one embodiment, a server system/third party selects a next request from a batch of requests, with the next request requiring a protected resource (hosted on a second party) owned by a owner/user (first party). The server system checks whether an access token is present authorizing access of the protected resource by the server system on behalf of the owner. If the access token is not present, the server system communicates in an offline mode with the owner to receive the access token. The server system then processes the next request by accessing the protected resource using the present/received access token.