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: 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: 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: A method, system, and computer program product for determining valid drop targets for nodes within an integration flow using mapping that includes: identifying a first node, identifying one or more input nodes, where the one or more input nodes are nodes within an integration flow of the first node, analyzing a mapping of the first node, where the analyzing includes determining whether the mapping contains one or more inputs from the one or more input nodes, and in response to determining that the mapping contains one or more inputs from an input node of the one or more input nodes, identifying valid drop points for the first node using the input node.

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

Abstract: A method, system, and computer program product for determining valid drop targets for nodes within an integration flow using mapping that includes: identifying a first node, identifying one or more input nodes, where the one or more input nodes are nodes within an integration flow of the first node, analyzing a mapping of the first node, where the analyzing includes determining whether the mapping contains one or more inputs from the one or more input nodes, and in response to determining that the mapping contains one or more inputs from an input node of the one or more input nodes, identifying valid drop points for the first node using the input node.

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: Methods and systems for identifying groups of related nodes in an integration flow are disclosed.

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.