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 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: 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: 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: 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: 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: 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: A batched unit of work is associated with a plurality of messages for use with a data store. A backout count, associated with a number of instances that work in association with the batched unit of work, is backed out. A backout threshold is associated with the backout count. A commit count is associated with committing the batched unit of work in response to successful commits for a predefined number of the plurality of messages. A checker checks whether the backout count is greater than zero and less than the backout threshold. An override component, responsive to the backout count being greater than zero and less than the backout threshold, overrides the commit count and commits the batched unit of work for a subset of the plurality of messages.

Abstract: A batched unit of work is associated with a plurality of messages for use with a data store. A backout count, associated with a number of instances that work in association with the batched unit of work, is backed out. A backout threshold is associated with the backout count. A commit count is associated with committing the batched unit of work in response to successful commits for a predefined number of the plurality of messages. A checker checks whether the backout count is greater than zero and less than the backout threshold. An override component, responsive to the backout count being greater than zero and less than the backout threshold, overrides the commit count and commits the batched unit of work for a subset of the plurality of messages.