Abstract: A method for dynamically determining a predetermined previous condition of a rule-based system comprising a plurality of rules. Each of the plurality of rules is associated with a transaction and a condition under which the transaction is executed. In one embodiment, the method includes the steps of (a) determining a system condition; (b) determining an immediate previous condition that caused the system condition; (c) setting the immediate previous condition to the system condition; and (d) repeating steps (b) and (c) until the predetermined previous condition is reached.

Abstract: A method of automatically determining firing priority in a plurality of rules. The method includes the steps of determining a level of dependency of each rule; and generating a hierarchy of rules in response to the level of dependency of each rule, wherein the firing priority corresponds to the hierarchy of rules. In another embodiment, the method further includes the step of determining if the hierarchy results in an inconsistency. In another embodiment, the method further comprises the step of determining if the hierarchy results in a loop. In yet another embodiment, the step of determining a level of dependency of each rule is performed in response to an initial event. In one embodiment the method includes the step of determining if there are reciprocal dependencies between any two rules in the set of rules.

Abstract: A method for dynamically determining a predetermined previous condition of a rule-based system comprising a plurality of rules. Each of the plurality of rules is associated with a transaction and a condition under which the transaction is executed. In one embodiment, the method includes the steps of (a) determining a system condition; (b) determining an immediate previous condition that caused the system condition; (c) setting the immediate previous condition to the system condition; and (d) repeating steps (b) and (c) until the predetermined previous condition is reached.

Abstract: A method of automatically determining firing priority in a plurality of rules. The method includes the steps of determining a level of dependency of each rule; and generating a hierarchy of rules in response to the level of dependency of each rule, wherein the firing priority corresponds to the hierarchy of rules. In another embodiment, the method further includes the step of determining if the hierarchy results in an inconsistency. In another embodiment, the method further comprises the step of determining if the hierarchy results in a loop. In yet another embodiment, the step of determining a level of dependency of each rule is performed in response to an initial event.

Abstract: The invention includes a method for determining whether a node in a non-recursive network can be removed. The method includes the steps of executing a reachability algorithm for a resource of a system upon initialization of the system. The resource is accessible to the system upon the initialization. A safe to pull manager evaluates the reachability algorithm for each node situated on the network to determine whether the node can be removed without interrupting resource accessibility to the system.

Abstract: A method and apparatus for managing session information. In one embodiment, a communication session is established between a client computer and a server computer. When the client computer and the server computer establish the communication session, the client or the server typically stores information about the communication session, which is referred to as “session information.” The session information is stored in a first log file stored in a persistent volatile memory and in a cache file stored in a volatile memory of the server. The cache file is reconstructed after a server failure by retrieving the session information stored in the first log file.

Abstract: A method and apparatus for managing session information. In one embodiment, a communication session is established between a client computer and a server computer. When the client computer and the server computer establish the communication session, the client or the server typically stores information about the communication session, which is referred to as “session information.” The session information is stored in a first log file stored in a persistent volatile memory and in a cache file stored in a volatile memory of the server. The cache file is reconstructed after a server failure by retrieving the session information stored in the first log file.

Abstract: A method and apparatus for managing one or more records. A scan module transmits a scan request to a session storage manager. The scan request identifies a particular record at which the scan module 612 starts a scan session. The session storage manager also receives an application request from an application to modify the record. The session storage manager then transforms the requested record into a version if the record exhibits a predetermined characteristic.