Abstract: A model is used to provide a user interface to track flows through at least one application of a computer system. The model relates the structural aspects of the at least one application to a behavioral model such as a business transaction hierarchy. The structural part of the model includes linked Vertex and Edge records. Vertex records for different instances of a component can be aggregated to provide a single vertex or node for display in a user interface. A Vertex record is linked to an Agent record and a Metric Path record. The Edge records identify tail and head components of a call. A set of Edge records can be associated with a Transaction record in the behavioral part of the model. A Transaction record can be associated with a Business Transaction Record, and a Business Transaction record can be associated with a Business Service Record.

Abstract: A method for tracking a patient in a medical facility is disclosed. The method includes determining whether a patient is to be moved, indicating the time at which the patient should start to be moved, and interrogating a RFID sensor on the patient at a predetermined time interval to determine when the patient has been moved.

Abstract: Transaction-segregated metrics are obtained for component invocations of different transactions of an application. Corresponding tree data structures are maintained by an agent and a manager which describe sequences of invoked components of the different transactions. The start and end of each component are each represented by a node in each branch of the tree data structure. Each transaction is identified by matching a branch to a transaction trace. Gatherers are linked to one or more nodes to collect the transaction-segregated metrics. For example, metrics can be gathered separately for component invocations in different transactions. Metrics can also be gathered together for instances of different components in one or more transactions. A user interface includes a directed graph having vertices connected by edges. Edge portions are visually distinguished from one another based on the metrics of the gatherers. Each edge portion can be associated with one or more of the gatherers.

Abstract: Transaction-segregated metrics are obtained for component invocations of different transactions of an application. Corresponding tree data structures are maintained by an agent and a manager which describe sequences of invoked components of the different transactions. The start and end of each component are each represented by a node in each branch of the tree data structure. Each transaction is identified by matching a branch to a transaction trace. Gatherers are linked to one or more nodes to collect the transaction-segregated metrics. For example, metrics can be gathered separately for component invocations in different transactions. Metrics can also be gathered together for instances of different components in one or more transactions. A user interface includes a directed graph having vertices connected by edges. Edge portions are visually distinguished from one another based on the metrics of the gatherers. Each edge portion can be associated with one or more of the gatherers.

Abstract: A model is used to provide a user interface to track flows through at least one application of a computer system. The model relates the structural aspects of the at least one application to a behavioral model such as a business transaction hierarchy. The structural part of the model includes linked Vertex and Edge records. Vertex records for different instances of a component can be aggregated to provide a single vertex or node for display in a user interface. A Vertex record is linked to an Agent record and a Metric Path record. The Edge records identify tail and head components of a call. A set of Edge records can be associated with a Transaction record in the behavioral part of the model. A Transaction record can be associated with a Business Transaction Record, and a Business Transaction record can be associated with a Business Service Record.

Abstract: A method of using a wireless scheduling device to determine schedule availability for a set of attendees includes communicating an availability request to a server using the wireless scheduling device. The server has access to calendar data for each attendee on the set of attendees. In response to the availability request, a search is conducted of the calendar data of each attendee to produce an availability data set. The availability data set is transmitted to the wireless scheduling device. The availability data set may then be displayed on the wireless scheduling device.