Abstract: A method of event based object ranking is described. An object query is computed based upon a user action. The results of the query are ranked based on one or more events associated with objects in the results to create ranked results. The ranked results are provided to the user in response to the query.

Abstract: A method of event based object ranking is described. An object query is computed based upon a user action. The results of the query are ranked based on one or more events associated with objects in the results to create ranked results. The ranked results are provided to the user in response to the query.

Abstract: Disclosed is a technique for flow control. It is detected that a work request is being transferred to an in-memory structure. A maximum limit is compared with a number of work requests stored in the in-memory structure. If the number of work requests stored in the in-memory structure equals the maximum limit, a notification is sent that indicates that additional work requests are not to be sent.

Abstract: Disclosed is a technique for system recovery. Information identifying one or more work requests is retrieved, along with an order of the work requests, for a business process. If the business process is non-transactional, an in-memory structure is created for the business process, a recovery stub is created for each work request, and the recovery stub for each work request is placed into the in-memory structure based on the order.

Abstract: Disclosed is a technique for buffering work requests. It is determined that a work request is about to be placed into an in-memory structure. When the in-memory structure is not capable of storing the work request, a work request ordering identifier for the work request is stored into an overflow structure. When the in-memory structure is capable of storing the work request, a recovery stub is generated for the work request ordering identifier, and the recovery stub is stored into the in-memory structure.

Abstract: Disclosed is a technique for buffering work requests. It is determined that a work request is about to be placed into an in-memory structure. When the in-memory structure is not capable of storing the work request, a work request ordering identifier for the work request is stored into an overflow structure. When the in-memory structure is capable of storing the work request, a recovery stub is generated for the work request ordering identifier, and the recovery stub is stored into the in-memory structure.

Abstract: Disclosed is a technique for system recovery. Information identifying one or more work requests is retrieved, along with an order of the work requests, for a business process. If the business process is non-transactional, an in-memory structure is created for the business process, a recovery stub is created for each work request, and the recovery stub for each work request is placed into the in-memory structure based on the order. Also disclosed is a technique for system recovery in which, if the business process is transactional, an in-memory structure is created for the business process, a recovery stub is created for each work request that indicates that rollback is to be performed, and the recovery stub is placed for each work request into the in-memory structure based on the order.

Abstract: Disclosed is a technique for flow control. It is detected that a work request is being transferred to an in-memory structure. A maximum limit is compared with a number of work requests stored in the in-memory structure. If the number of work requests stored in the in-memory structure equals the maximum limit, a notification is sent that indicates that additional work requests are not to be sent.

Abstract: The present invention provides a method, apparatus, and computer instructions for activating application programs and adapters. In an exemplary embodiment, a reactivation program is provided that includes a queue manager (QM) that operates to monitor for predetermined trigger events (e.g., time out for messages in an application queue) and, when such events occur, to generate a trigger message. The trigger message includes process information associated with the crashed application which is used by a trigger monitor application to issue an appropriate command to the application. In a preferred embodiment, the trigger message is placed in an initiation queue, read out by a trigger monitor, and a restart command message, according to the predetermined parameters, sent to the application. More than one process definition can be used by the initiation queue.

Abstract: A system for integrating applications in different enterprises separated by firewalls comprises: an input for receiving high level business data from a source application; an encryption engine for encrypting the business data to produce encrypted business data; a queue manager for receiving the encrypted business data and for storing the business data for delivery to a target application; and an output for transmitting the encrypted business data to the target application; wherein the system and the target application are separated by at least one firewall.