Abstract: An issue is detected in the operation of a set of integrated applications. Assistive logic is launched and an application, causing the issue, is identified. Application running logic is controlled to roll the application back to a last known good state.

Abstract: An issue is detected in the operation of a set of integrated applications. Assistive logic is launched and an application, causing the issue, is identified. Application running logic is controlled to roll the application back to a last known good state.

Abstract: A facility executes on a central computer system and applies a time-varying load to an application program under test (AUT). The facility executes in a multiple number of modes or hierarchical levels as dictated by information provided in its configuration file. An instance of the facility executing at the highest or first-level of the hierarchy is responsible for spawning numerous subordinate or second-level instances of the facility on, for example, remote computer systems. These second-level instances of the facility may spawn additional subordinate or third-level executors on the same or remote computer systems. Ultimately, the lowest-level or leaf instances of the facility are spawned, and these leaf instances of the facility are responsible for launching the client test program instances that are used to test the AUT.

Abstract: A client utilizes a backchannel messaging infrastructure and information matching logic to measure server performance characteristics at the client without requiring the server to correlate command responses to command requests. The backchannel messaging infrastructure facilitates the sending of messages between clients, and allows a client to send to the interested clients messages containing an activity start timestamp and identifying the requested activity when sending a command request to a server. The information matching logic enables each client to measure server performance by matching command requests, as indicated by the backchannel messages, and command responses based on message types, identification of the sender (i.e., the client that generated the original command request), and identifier attributes that are unique to the command requests and command responses.