Abstract: A system and method for automatic remediation of non-compliance events are provided. In embodiments, a computer-implemented method includes: accessing a compliance profile and a remediation profile, wherein the compliance profile includes compliance data regarding rules for an enterprise and the remediation profile includes remediation data regarding remediation actions to address non-compliance with one or more of the rules; generating mapped data by mapping compliance data in the compliance profile to remediation data in the remediation profile; receiving non-compliance event data from a workload node in a network; extracting information from the non-compliance event data including the workload node associated with the event and a cause of event; determining a remediation action for the event based on the information and the mapped data; and invoking automatic performance of the remediation action at the workload node based on the determined remediation action.

Abstract: A system and method for automatic remediation of non-compliance events are provided. In embodiments, a computer-implemented method includes: accessing a compliance profile and a remediation profile, wherein the compliance profile includes compliance data regarding rules for an enterprise and the remediation profile includes remediation data regarding remediation actions to address non-compliance with one or more of the rules; generating mapped data by mapping compliance data in the compliance profile to remediation data in the remediation profile; receiving non-compliance event data from a workload node in a network; extracting information from the non-compliance event data including the workload node associated with the event and a cause of event; determining a remediation action for the event based on the information and the mapped data; and invoking automatic performance of the remediation action at the workload node based on the determined remediation action.

Abstract: In an approach to improve recommendation generating through IoT devices, embodiments abstract specific messaging formats from various IoT devices, map, the abstracted messaging formats to a canonical model associated to device types using based on collected IoT device data, and determine a context of data received from the plurality of IoT devices based on the type of IoT device and historical trend analysis of canonical data points from similar device types. Further, embodiments derive an association between data points among the plurality of IoT devices in a solution, determine one or more contexts of the established data point associations in the solution, and recommend one or more charts, events, and associated data based on a derived context and a visualization map. Additionally, embodiments output, by a user interface, the recommended chart events and associated data.

Abstract: Provided is a method for generating a data backup strategy for a computer system. The method comprises receiving an event related to a change in a computer system. The method further comprises applying regression techniques on historical data related to previous events for the computer system to determine a failure prediction score for the computer system. The method further comprises calculating a set of backup parameters for performing a backup of data of the computer system. The method further comprises generating a score for the backup using the set of backup parameters. The method further comprises determining a backup strategy for the computer system based on the score.

Abstract: A method for orchestrating a provisioning of a computer workload includes determining characteristics of a computing pattern, determining health data of a computing environment based on the characteristics of the computing pattern, determining a confidence score based on the health data, and determining whether to proceed with provisioning the computer workload based on the confidence score.

Abstract: A method for orchestrating a provisioning of a computer workload includes determining characteristics of a computing pattern, determining health data of a computing environment based on the characteristics of the computing pattern, determining a confidence score based on the health data, and determining whether to proceed with provisioning the computer workload based on the confidence score.

Abstract: Systems and methods for sharing transactional context between Java and traditional language applications are disclosed. In embodiments, a method comprises: receiving, by a computing device, a transaction request to execute a program, wherein the program comprises non-Java program components and Java program components; executing, by a transaction middleware of the computing device, the non-Java program components; contacting, by the transaction middleware, a resource manager server and registering with the resource manager server using global transaction ID data; transferring, by the transaction middleware of the computing device, the Java program components to a transaction coordinator of the computing device, along with thread ID data and the global transaction ID data; and storing, by the transaction coordinator, the thread ID data and global transaction ID data in a recoverable transaction log store.

Abstract: A system and method for automatic remediation of non-compliance events are provided. In embodiments, a computer-implemented method includes: accessing a compliance profile and a remediation profile, wherein the compliance profile includes compliance data regarding rules for an enterprise and the remediation profile includes remediation data regarding remediation actions to address non-compliance with one or more of the rules; generating mapped data by mapping compliance data in the compliance profile to remediation data in the remediation profile; receiving non-compliance event data from a workload node in a network; extracting information from the non-compliance event data including the workload node associated with the event and a cause of event; determining a remediation action for the event based on the information and the mapped data; and invoking automatic performance of the remediation action at the workload node based on the determined remediation action.

Abstract: Disclosed is a computer implemented method to adjust device health weighting factors, the method comprising, determine a set of monitored devices including a first monitored device. The method comprises, determining a set of parameters, wherein each parameter is associated with one operating metric of each of the monitored devices. The method comprises, receiving a set of usage data, including a usage history for each parameter. The method further comprises, performing trend analysis on the set of usage data configured to identify a relative influence of each parameter on the set of monitored devices. The method also comprises, generating a set of weighting factors based on the trend analysis, and wherein each parameter in the set of parameters is associated with a weighting factor, and calculating a health score for the first monitored device, wherein the calculation is based on the set of weighting factors.

Abstract: A method, system, and computer program product to integrate service management tools with enterprise product development tools to determine Ops readiness scores. The method may include receiving one or more logs of bug tracking information from a client module, where the bug tracking information corresponds to one or more applications with one or more production bugs. The method may also include compiling the one or more logs. The method may also include receiving reports of at least Ops issues of the one or more applications and latest requirements of the one or more applications from a company module, where the latest requirements include at least current deliverables. The method may also include mapping the compiled one or more logs and the reports. The method may also include generating an Ops readiness score for each of the current deliverables, based on the mapping.

Abstract: An approach is provided for providing transactional operations in an event-driven polyglot language runtime environment. Native functionalities of a transaction processing system are exposed as interfaces to multiple languages and frameworks in the runtime environment. The transactional operations are called from modules. The transaction processing system is integrated with the modules. A prepare operation is sent to a resource manager (RM) via a resolution thread. For a committed transaction outcome of the resolution thread, the commit is logged, an indication of the commit is sent to the RM, the commit is performed, a completion indication of the commit is sent, and a forget operation is logged. For a rollback transaction outcome of the resolution thread, the rollback is logged, an indication of the rollback is sent to the RM, the rollback is performed, a completion indication of the rollback is sent, and the forget operation is logged.

Abstract: A method, system, and computer program product to integrate service management tools with enterprise product development tools to determine Ops readiness scores. The method may include receiving one or more logs of bug tracking information from a client module, where the bug tracking information corresponds to one or more applications with one or more production bugs. The method may also include compiling the one or more logs. The method may also include receiving reports of at least Ops issues of the one or more applications and latest requirements of the one or more applications from a company module, where the latest requirements include at least current deliverables. The method may also include mapping the compiled one or more logs and the reports. The method may also include generating an Ops readiness score for each of the current deliverables, based on the mapping.

Abstract: Disclosed is a computer implemented method to adjust device health weighting factors, the method comprising, determine a set of monitored devices including a first monitored device. The method comprises, determining a set of parameters, wherein each parameter is associated with one operating metric of each of the monitored devices. The method comprises, receiving a set of usage data, including a usage history for each parameter. The method further comprises, performing trend analysis on the set of usage data configured to identify a relative influence of each parameter on the set of monitored devices. The method also comprises, generating a set of weighting factors based on the trend analysis, and wherein each parameter in the set of parameters is associated with a weighting factor, and calculating a health score for the first monitored device, wherein the calculation is based on the set of weighting factors.

Abstract: Systems, methods, and apparatuses to perform an operation receiving, by a first workload manager in a first middleware environment, state information for a plurality of applications executing in a second middleware environment defining, by the first workload manager based on the received state information, a first routing rule in the first middleware environment, and, based on the first routing rule: identifying, by a first application of a plurality of applications executing in the first middleware environment, a second application of the plurality of applications executing in the second middleware environment, and forwarding, by the first application of the plurality of applications executing in the first middleware environment, a first workload to the second application of the plurality of applications executing in the second middleware environment.

Abstract: Systems and methods for sharing transactional context between Java and traditional language applications are disclosed. In embodiments, a method comprises: receiving, by a computing device, a transaction request to execute a program, wherein the program comprises non-Java program components and Java program components; executing, by a transaction middleware of the computing device, the non-Java program components; contacting, by the transaction middleware, a resource manager server and registering with the resource manager server using global transaction ID data; transferring, by the transaction middleware of the computing device, the Java program components to a transaction coordinator of the computing device, along with thread ID data and the global transaction ID data; and storing, by the transaction coordinator, the thread ID data and global transaction ID data in a recoverable transaction log store.

Abstract: Systems and methods for sharing transactional context between Java and traditional language applications are disclosed. In embodiments, a method comprises: receiving, by a computing device, a transaction request to execute a program, wherein the program comprises non-Java program components and Java program components; executing, by a transaction middleware of the computing device, the non-Java program components; contacting, by the transaction middleware, a resource manager server and registering with the resource manager server using global transaction ID data; transferring, by the transaction middleware of the computing device, the Java program components to a transaction coordinator of the computing device, along with thread ID data and the global transaction ID data; and storing, by the transaction coordinator, the thread ID data and global transaction ID data in a recoverable transaction log store.

Abstract: An approach is provided for providing transactional operations in an event-driven polyglot language runtime environment. Native functionalities of a transaction processing system are exposed as interfaces to multiple languages and frameworks in the runtime environment. The transactional operations are called from modules. The transaction processing system is integrated with the modules. A prepare operation is sent to a resource manager (RM) via a resolution thread. For a committed transaction outcome of the resolution thread, the commit is logged, an indication of the commit is sent to the RM, the commit is performed, a completion indication of the commit is sent, and a forget operation is logged. For a rollback transaction outcome of the resolution thread, the rollback is logged, an indication of the rollback is sent to the RM, the rollback is performed, a completion indication of the rollback is sent, and the forget operation is logged.

Abstract: A first request to a first thread-based server from a first thread-based client is detected. The first request is derived by the first thread-based client in response to a first call from a first user program running on process-based middleware. The first request is intercepted from a communication pathway. The first request is converted to a merged request. The merged request is intended for a merged thread-based server of the thread-based middleware. The merged request is sent to the merged thread-based server.

Abstract: An approach is provided for providing transactional operations in an event-driven polyglot language runtime environment. Native functionalities of a transaction processing system are exposed as interfaces to multiple languages and frameworks in the event-driven polyglot language runtime environment. Application programming interfaces (APIs) are generated for the event-driven polyglot language runtime environment. Via the APIs, the transactional operations are called from modules within the event-driven polyglot language runtime environment. Based on the native functionalities of the transaction processing system being exposed and the transactional operations being called from the modules within the event-driven polyglot language runtime environment via the APIs, the transaction processing system is integrated with the modules within the event-driven polyglot language runtime environment.

Abstract: The present disclosure relates to techniques for discovering and exposing middleware applications as service endpoints through a universal connector in a middleware-agnostic fashion that does not require additional coding. In one embodiment, a back-end middleware system identifies a set of middleware applications that operate on an input/output (I/O) data area. Next, the back-end middleware system generates a set of discovery artifacts describing the middleware applications and the I/O data area. A discovery client sends a discovery request to a the back-end middleware system, which sends structured information from the discovery artifacts in response. Based on the structured information, the discovery client creates a REST model for the set of middleware applications, mapper artifacts that map REST operations to the middleware applications, and transformer artifacts that indicate how to convert data between Javascript-object-notation (JSON) format and format that is compatible with the I/O data area.