Abstract: A computer system performs decentralized collection and aggregation of data. A plurality of requests for data are transmitted, by a data collection server, to a corresponding plurality of remote servers, wherein the plurality of remote server submit responses to the plurality of requests for data to a distributed data structure. The distributed data structure is accessed, by the data collection server, to retrieve the plurality of responses to the plurality of requests. The plurality of responses are aggregated, by the data collection server, into a message and the message is transmitted to an entity requesting data collection. Embodiments of the present invention further include a method and program product for performing decentralized collection and aggregation of data in substantially the same manner described above.

Abstract: Disclosed embodiments provide improvements in integration template generation. In embodiments, existing customer integration flows already created by users are analyzed using computer-implemented methods, and from these customer integration flows, templates are created that encapsulate the general patterns that are seen in existing customer integration flows. The customer integration flows are anonymized by removing proprietary and/or identifying data. The result is customer integration templates based on actual real-world usage, which can more accurately resemble the needs of customers as compared to traditional templates that are authored by someone envisioning how he thinks the applications will be linked together, but not based on how they actually are used. Disclosed embodiments can generate integration templates based on general patterns encountered by multiple users that serve as a good starting point for any user that wants to do similar integrations.

Abstract: A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: Methods and systems for identifying groups of related nodes in an integration flow are disclosed.

Abstract: A computer system performs decentralized collection and aggregation of data. A plurality of requests for data are transmitted, by a data collection server, to a corresponding plurality of remote servers, wherein the plurality of remote server submit responses to the plurality of requests for data to a distributed data structure. The distributed data structure is accessed, by the data collection server, to retrieve the plurality of responses to the plurality of requests. The plurality of responses are aggregated, by the data collection server, into a message and the message is transmitted to an entity requesting data collection. Embodiments of the present invention further include a method and program product for performing decentralized collection and aggregation of data in substantially the same manner described above.

Abstract: A method and system for mapping data elements between a source data structure and a target data structure. A source data element is mapped to a target data element by matching a source key and value pair to a target key and value pair. A parent source Soundex key for each parent element of the source data element is created. A parent target Soundex key for each parent element of a plurality of target data elements snatching the first Soundex key of the source data element is created. The parent source Soundex key for each parent element of the source data element is compared with each parent target Soundex key. The source data element is mapped to the target data element having the parent target Soundex key that matches the parent source Soundex key.

Abstract: Provided is an apparatus, method and computer program product for executing an aggregation method in an integration environment comprising: issuing, in response to receiving an input message from a requesting application, a first control signal, using, in response to receiving the first control signal, a single logical thread to: generate an entry associated with an in-memory data structure, wherein the entry comprises: an aggregation identifier associated with the input message and a response identifier associated with a response message associated with a target application; update, in response to receiving the response message from the target application, the entry with the response message; and add the updated entry to the in-memory data structure.

Abstract: Passing a result of batch processing into a data integration flow is provided. Each data record of a plurality of data records corresponding to a specified data record collection is processed within a different thread of a different execution branch in parallel. At an end of each processing of each different execution branch, a new value is computed for each processed data record based on a previously stored value and an execution branch context for each processed data record. It is determined whether all data records in the plurality of data records have been processed. In response to determining that all of the data records in the plurality of data records have been processed, a data accumulation object corresponding to the batch processing is updated within a data assembly context based on a computed new value for each processed data record to form an updated data assembly context.

Abstract: Proposed are concepts for managing communication between off-premises and on-premises servers. A file system event request from an application of a first server (such as an off-premises server or an on-premises server) is received and a requested file system is determined based on the received file system event request. Stored file system path data associated with the requested file system can then be identified. The file system event request is then communicated to a second server (such as an on-premises server or off-premises server) based on the identified file system path data.

Abstract: Provided is an apparatus, method and computer program product for executing an aggregation method in an integration environment comprising: issuing, in response to receiving an input message from a requesting application, a first control signal, using, in response to receiving the first control signal, a single logical thread to: generate an entry associated with an in-memory data structure, wherein the entry comprises: an aggregation identifier associated with the input message and a response identifier associated with a response message associated with a target application; update, in response to receiving the response message from the target application, the entry with the response message; and add the updated entry to the in-memory data structure.

Abstract: Methods and systems for identifying groups of related nodes in an integration flow are disclosed.

Abstract: Disclosed embodiments provide improvements in integration template generation. In embodiments, existing customer integration flows already created by users are analyzed using computer-implemented methods, and from these customer integration flows, templates are created that encapsulate the general patterns that are seen in existing customer integration flows. The customer integration flows are anonymized by removing proprietary and/or identifying data. The result is customer integration templates based on actual real-world usage, which can more accurately resemble the needs of customers as compared to traditional templates that are authored by someone envisioning how he thinks the applications will be linked together, but not based on how they actually are used. Disclosed embodiments can generate integration templates based on general patterns encountered by multiple users that serve as a good starting point for any user that wants to do similar integrations.

Abstract: A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: Automated software-testing systems and computer program products use mock software entities to perform integration testing on a microservices-based application. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: Proposed are concepts for managing communication between off-premises and on-premises servers. A file system event request from an application of a first server (such as an off-premises server or an on-premises server) is received and a requested file system is determined based on the received file system event request. Stored file system path data associated with the requested file system can then be identified. The file system event request is then communicated to a second server (such as an on-premises server or off-premises server) based on the identified file system path data.

Abstract: Passing a result of batch processing into a data integration flow is provided. Each data record of a plurality of data records corresponding to a specified data record collection is processed within a different thread of a different execution branch in parallel. At an end of each processing of each different execution branch, a new value is computed for each processed data record based on a previously stored value and an execution branch context for each processed data record. It is determined whether all data records in the plurality of data records have been processed. In response to determining that all of the data records in the plurality of data records have been processed, a data accumulation object corresponding to the batch processing is updated within a data assembly context based on a computed new value for each processed data record to form an updated data assembly context.

Abstract: Proposed are concepts for managing communication between off-premises and on-premises servers. A file system event request from an application of a first server (such as an off-premises server or an on-premises server) is received and a requested file system is determined based on the received file system event request. Stored file system path data associated with the requested file system can then be identified. The file system event request is then communicated to a second server (such as an on-premises server or off-premises server) based on the identified file system path data.

Abstract: An approach is provided for determining inputs to a component of an integration flow. First component(s) that are upstream of the component in a given level of the integration flow are identified. First output schema(s) of the first component(s) are determined. In response to determining one or more components of the integration flow contain the component from one or more levels above the given level of the hierarchy of the integration flow, second component(s) that are upstream of the one or more components that contain the component are identified, second output schema(s) of the second component(s) are determined, and the first and second output schemas are presented as the inputs to the component.

Abstract: Proposed are concepts for managing communication between off-premise and on-premise servers. A flow execution request from an application of an off-premise server or an on-premise server is received and a requested flow is determined based on the received flow execution request. Stored endpoint data associated with the requested flow can then be identified. The flow execution request is then communicated to an on-premise server or off-premise server based on the identified endpoint data.