Abstract: An approach to implement an extract, transform and load system, a queue is provided for holding units of data between extraction and transformation. When units of data suffer a rate limit error in the load phase, they are requeued so they can be resubmitted for transformation. The contents of the queue are monitored and, if too many requeued units of data are detected in the queue, then this is taken as an indicator of an unacceptable number of rate limit errors and active pacing management is triggered. A retry schedule is defined for the requeued units of data. Extraction is temporarily halted to allow the requeued units of data to be retransformed without more units of data queuing up. Then, after the suspension is lifted, a pacing delay is inserted between subsequent extract events to avoid the same load phase bottleneck recurring.

Abstract: A method, system, and computer program product are configured to: receive, from a user device of a user, input indicating that a first extract, transform, and load (ETL) flow is incorrect and that a second ETL flow is correct; in response to receiving the input, determine whether a change made by the first ETL flow is reversible; in response to determining the change made by the first ETL flow is reversible, generate a corrective ETL flow that is configured to reverse the change made by the first ETL flow; and in response to determining the change made by the first ETL flow is not reversible, notify a user that the change made by the first ETL flow is not reversible, and inform the user which records have been changed such that they can do a manual correction.

Abstract: A method, computer program product, and computer system are described for providing integration flows between endpoint systems. The method includes providing a delegation integration module for each of multiple disparate types of endpoint systems, wherein a delegation integration module for a type of endpoint system is configured to understand how to construct and coordinate integration artifacts in the endpoint system type. The method includes defining an integration flow with required endpoint systems. This integration flow includes generating required linked integration artifacts, injecting the integration artifacts into the relevant endpoint systems that are ready for execution, delegating integration tasks of the integration flow via the delegation integration modules to the required endpoint systems, and using the linked integration artifacts at the endpoint systems to carry out the integration tasks.

Abstract: A method, system, and computer program product that is configured to: receive inbound data; tag a plurality of data fields of the inbound data; execute at least one integration flow which transforms the inbound data with tagged data fields to transformed data with the tagged data fields; obscure values of the data fields in the transformed data based on the tagged data fields; and send outbound data which includes the transformed data with the obscured values of the data fields.

Abstract: An integration flow can be improved with the use of a pattern identified from a pattern library. The identified pattern can include a snippet of nodes which are functionally equivalent to a subset of nodes in the integration flow. The pattern also lists an endpoint capable of performing the snippet of nodes. The integration flow can therefore be updated to cause the endpoint to perform the snippet of nodes.

Abstract: Embodiments of the present invention provide methods, computer program products, and systems. Embodiments of the present invention can identify a network request as being deferrable and embed data of the deferrable network request within a header of a suitable carrier network request for sending to a remote server. Embodiments of the present invention can receive a carrier network request with embedded data of a deferrable network request within a header of the carrier network request. Embodiments of the present invention can then parse the embedded data from the header into a separate request message for actioning at the server.

Abstract: Approaches presented herein enable a security risk manager embedded in an application to manage security vulnerabilities of the application. More specifically, the application comprises code entities such as components, packages, libraries, or microservices. The entities are modified as part of the application development process to have an enabled state, in which these entities are permitted to run normally when called, and a disabled state, in which these entities do not run when called but instead perform a back-out behavior such as generating an error message. At runtime, the application periodically accesses a security vulnerabilities database to check for security alerts. When a relevant security alert is found, the application changes any code entities that are affected by the security alert to the disabled state pending investigation by an operations team. The application notifies the operations team by sending a notification of the security alert to an external security monitoring tool.

Abstract: An approach to implement an extract, transform and load system, a queue is provided for holding units of data between extraction and transformation. When units of data suffer a rate limit error in the load phase, they are requeued so they can be resubmitted for transformation. The contents of the queue are monitored and, if too many requeued units of data are detected in the queue, then this is taken as an indicator of an unacceptable number of rate limit errors and active pacing management is triggered. A retry schedule is defined for the requeued units of data. Extraction is temporarily halted to allow the requeued units of data to be retransformed without more units of data queuing up. Then, after the suspension is lifted, a pacing delay is inserted between subsequent extract events to avoid the same load phase bottleneck recurring.

Abstract: An approach to implement an extract, transform and load system, a queue is provided for holding units of data between extraction and transformation. When units of data suffer a rate limit error in the load phase, they are requeued so they can be resubmitted for transformation. The contents of the queue are monitored and, if too many requeued units of data are detected in the queue, then this is taken as an indicator of an unacceptable number of rate limit errors and active pacing management is triggered. A retry schedule is defined for the requeued units of data. Extraction is temporarily halted to allow the requeued units of data to be retransformed without more units of data queuing up. Then, after the suspension is lifted, a pacing delay is inserted between subsequent extract events to avoid the same load phase bottleneck recurring.

Abstract: A pull request from a managed cluster may be authorized by, for each managed cluster managed by the service provider, generating an encrypted pull secret for a managed cluster, assigning the generated encrypted pull secret to the managed cluster, and responsive to receiving a pull request from a managed cluster at the service provider. The pull request may have an accompanying encrypted pull secret. The pull request may also determine whether the pull request was initiated by an intended managed cluster by decrypting the encrypted pull secret assigned to the managed cluster using a decryption key. The authorizing the pull request based on whether the decrypted pull secret is assigned to an intended managed cluster.

Abstract: An integration flow can be improved with the use of a pattern identified from a pattern library. The identified pattern can include a snippet of nodes which are functionally equivalent to a subset of nodes in the integration flow. The pattern also lists an endpoint capable of performing the snippet of nodes. The integration flow can therefore be updated to cause the endpoint to perform the snippet of nodes.

Abstract: An application configuration tool and associated method for supporting deployment of an application on a server that has a set of configurations available for applications deployed on the server. The method attempts to match every configuration required by the application to a configuration available on the server. In case of multiple candidates that match, one is selected. When there is no match an error message is generated. The method is iterated to inspect each selected configuration to identify any references contained in the selected configuration that themselves need further configurations. The iteration of inspecting and the matching to follow the references is continued until all such references are exhausted either by matching or failure to match and consequent error message generation. Finally, a configuration report is output specifying the selected configurations and, to the extent that not all required configurations have been matched to available configurations, the error messages.

Abstract: A method includes: receiving an indication of a new integration flow document that updates a current integration flow document of an integration flow; determining a last switchable node that is included in both the current integration flow document and the new integration flow document; determining, for each running instance of the integration flow using the current integration flow document, whether a currently executing node of the instance is less than or equal to the last switchable node; in response to determining the currently executing node of the instance is less than or equal to the last switchable node, switching the instance to the new integration flow document; and in response to determining the currently executing node of the instance is greater than or the last switchable node, waiting for completion of the instance using the current integration flow document.

Abstract: A method includes: receiving an indication of a new integration flow document that updates a current integration flow document of an integration flow; determining a last switchable node that is included in both the current integration flow document and the new integration flow document; determining, for each running instance of the integration flow using the current integration flow document, whether a currently executing node of the instance is less than or equal to the last switchable node; in response to determining the currently executing node of the instance is less than or equal to the last switchable node, switching the instance to the new integration flow document; and in response to determining the currently executing node of the instance is greater than or the last switchable node, waiting for completion of the instance using the current integration flow document.

Abstract: An application configuration tool and associated method for supporting deployment of an application on a server that has a set of configurations available for applications deployed on the server. The method attempts to match every configuration required by the application to a configuration available on the server. In case of multiple candidates that match, one is selected. When there is no match an error message is generated. The method is iterated to inspect each selected configuration to identify any references contained in the selected configuration that themselves need further configurations. The iteration of inspecting and the matching to follow the references is continued until all such references are exhausted either by matching or failure to match and consequent error message generation. Finally, a configuration report is output specifying the selected configurations and, to the extent that not all required configurations have been matched to available configurations, the error messages.

Abstract: Approaches presented herein enable a security risk manager embedded in an application to manage security vulnerabilities of the application. More specifically, the application comprises code entities such as components, packages, libraries, or microservices. The entities are modified as part of the application development process to have an enabled state, in which these entities are permitted to run normally when called, and a disabled state, in which these entities do not run when called but instead perform a back-out behavior such as generating an error message. At runtime, the application periodically accesses a security vulnerabilities database to check for security alerts. When a relevant security alert is found, the application changes any code entities that are affected by the security alert to the disabled state pending investigation by an operations team. The application notifies the operations team by sending a notification of the security alert to an external security monitoring tool.

Abstract: An approach to implement an extract, transform and load system, a queue is provided for holding units of data between extraction and transformation. When units of data suffer a rate limit error in the load phase, they are requeued so they can be resubmitted for transformation. The contents of the queue are monitored and, if too many requeued units of data are detected in the queue, then this is taken as an indicator of an unacceptable number of rate limit errors and active pacing management is triggered. A retry schedule is defined for the requeued units of data. Extraction is temporarily halted to allow the requeued units of data to be retransformed without more units of data queuing up. Then, after the suspension is lifted, a pacing delay is inserted between subsequent extract events to avoid the same load phase bottleneck recurring.

Abstract: A method and system are provided for customizing integration flow templates. The method can include can include monitoring user interaction with a plurality of systems external to an integration system to read data changes at the external systems and identifying at least one event pair, wherein each event pair is between two external systems having a same data change event in the two external systems. The identified event pairs are filtered for inclusion in an events chain and the external systems of the filtered event pairs are ordered in the events chain based on timestamps of the data change events. The method outputs integration flow templates based on the ordered external systems of the event pairs that define a flow trigger and at least one flow node.

Abstract: Embodiments of the present invention provide methods, computer program products, and systems. Embodiments of the present invention can identify a network request as being deferrable and embed data of the deferrable network request within a header of a suitable carrier network request for sending to a remote server. Embodiments of the present invention can receive a carrier network request with embedded data of a deferrable network request within a header of the carrier network request. Embodiments of the present invention can then parse the embedded data from the header into a separate request message for actioning at the server.

Abstract: A method, system, and computer program product for applying a profile to an assistive device based on a multitude of cues includes: gathering audio inputs surrounding an assistive device; analyzing, by the assistive device, the audio inputs; determining, based on the analyzing, scenario cues; classifying a current environment surrounding the assistive device from the scenario cues; comparing the current environment to device profiles of the assistive device; determining, based on the comparing, a matching profile; and, in response to determining the matching profile, executing the matching profile on the assistive device.