Abstract: A plurality of causal ladder is assembled in advance from component system events taken from previous system failures. The ladders classify the various transitions the system goes through from one set of observed states to another in multiple stages representing issues of differing urgency, importance and need for remediation. These stages are used at runtime to determine the criticality of any abnormal system activity and to accurately predict the component failure prior to the system crashing. Each ladder comprises a plurality of elevated stages representing criticality of the problem. At runtime, the causal ladder engine correlates real-time events received from the system to stages of one or more pre-constructed causal ladders and identifies a probable problem (and/or the faulty component) from the corresponding causal ladder. The causal ladder engine also determines the stage of the problem from event occurrences. At each stage, a different potential solution is identified for the problem.

Abstract: A plurality of stochastic models is built that predict the probabilities of state transitions for components in a complex system. The models are trained using output observations from the system at runtime. The overall state and health of the system can be determined at runtime by analyzing the distribution of current component states among the possible states. Subsequent to a low level component failure, the state transition probability stochastic model for the failed component can be analyzed by uncovering the previous states at N time intervals prior to the failure. The resulting state transition path for the component can be analyzed for the causes of the failure. Additionally, component failures resulting from the failure, or worsening state transition, in other components can be diagnosed by uncovering the previous states at the N times prior to the failure for multiple components in the system and then analyzing the state transition paths for correlations to the failed component.

Abstract: A method, apparatus and computer-usable medium for the steps of (1) establishing a first Instant messaging (IM) session with a first user login identifier (ID) on a first client device with a first network routing address; and, when a request to establish a next IM session with the same first user login ID is received from a second client device while the first IM session is active, dynamically enabling a seamless continuation of the first IM session on the second client device.

Abstract: A method, an apparatus, and computer instructions are provided for automatic discovery and maintenance of business processes in Web services and enterprise development environments. A set of agents are deployed to a set of enterprise containers to collect user function calls and report events to a central business workflow language generator. An event handler collects the events reported and an event grouper groups the events into a single workflow activity. An event correlation engine correlates activities to business workflow language constructions by using a temporal condition handler and a collection counting handler. The temporal condition handler maps activities that are in sequence, in parallel, and are repetitive. The collection counting handler counts the number of times an event is handled. Events and Rules for these events are written on the system based on a variety of business constructs that are particular to given business process definition language.

Abstract: The present invention provides a method, system, and computer program product for the autonomic installation and configuration of an enterprise business process on-demand. The method comprises: providing a business process document for expressing the business process, wherein the business process comprises a plurality of components and a workflow; providing a plurality of installation documents, where each installation document describes an installation of a component of the business process; providing a mapping document for mapping each component of the business process to at least one of the installation documents describing the installation of that component; and provisioning the business process on-demand using the business process document, the installation documents, and the mapping document.