IP Library Granted Patent US 7,552,445
Granted Patent B2
US 7,552,445 · App. 10/318,025 · Granted Jun 23, 2009

Systems and methods for monitoring events from multiple brokers

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,552,445
App. No.
10/318,025
Granted
Jun 23, 2009
Kind
B2
Abstract

An event monitoring system includes a plurality of enterprise brokers; and an event monitor coupled to at least some of the enterprise brokers using a network. The event monitor receives data event information from enterprise brokers connected thereto, and generates an incoming events list including the data event information received from at least some of the enterprise brokers. The event monitor may maintain connections to at least some of the enterprise brokers. The event monitor may simulate the flow of simulated data events throughout an enterprise.

Claims (71)

1. An event monitoring system comprising:

a computer system including a processor, the computer system being connected to a plurality of enterprise brokers;

the event monitoring system including a simulation module configured to determine propagation times for simulated events flowing though at least some of the plurality of enterprise brokers, according to at least one communication topology; and

the event monitoring system including an event monitor coupled to the at least some of said plurality of enterprise brokers using a network and configured to receive data event information from the at least some of the enterprise brokers connected thereto, wherein

the event monitor is configured to generate an incoming events list including the data event information received from the at least some of the enterprise brokers connected thereto, and to further generate an historical events list based on user input date event parameters in response to a user selection, and wherein

the event monitor includes a user interface configured to output the incoming events list, simulation results, and historical events list to a user.

2. The event monitoring system of claim 1 , further configured to maintain connections to the at least some of said plurality of enterprise brokers.

3. The event monitoring system of claim 2 , wherein the event monitor further comprises:

a listener associated with each of the connections, each said listener being configured to detect a desired set of data events.

4. The event monitoring system of claim 1 , further comprising an event database operably coupled to the event monitor, and wherein the event monitor is further configured to store data events using the event database.

5. The event monitoring system of claim 1 , in which the event monitor is further configured to simulate a flow of data events throughout an enterprise.

6. An event monitor comprising:

a computer system including a processor, the computer system being connected to a plurality of enterprise brokers using a network,

the computer system further including a server listener module and a corresponding client listener module for each enterprise broker connection,

wherein each client listener module is configured to detect data events flowing through a corresponding enterprise broker, the computer system further including an event tracking module to configure the processor to receive data event information from at least some of the enterprise brokers via the network and to generate an incoming events list including the data event information received from the enterprise brokers,

the computer system further including a simulation module to configure the processor to determine propagation times for simulated events flowing though at least one enterprise broker and at least one enterprise broker client or application according to at least one communication topology, the event tracking module further configured to cause the processor to generate an historical events list based on user input data event parameters in response to a user selection,

the computer system further including a user interface module to configure the processor to output at least some of the incoming events list, simulation results, and historical events list to a user.

7. The event monitor of claim 6 , further comprising an event database including a broker connections property file containing broker connection information, and wherein the processor is further configured to store data events using the event database.

8. The event monitor of claim 6 , wherein the user interface module further includes a graphical user interface, the graphical user interface being configured to output a monitor page containing the incoming events list to the user.

9. The event monitor of claim 6 , wherein the simulation module is further configured to compare propagation times and includes a simulation report generator.

10. The event monitor of claim 6 , wherein the event tracking module data event parameters further include a work order number.

11. An event monitoring method comprising, at an event monitoring device:

establishing connections between the event monitoring device and at least some of a plurality of enterprise brokers;

detecting the occurrence of one of a particular set of data events at the at least some of said plurality of enterprise brokers;

outputting data event information associated with the detected data event to the event monitoring device;

using a simulator to determine propagation times for simulated events flowing though the at least some of the plurality of enterprise brokers according to at least one communication topology;

generating an incoming events list including the data event information received from the at least some of said plurality of enterprise brokers;

generating an historical events list based on user input data event parameters in response to a user selection; and

outputting the incoming event list, simulation results, and historical events list to a user.

12. The method of claim 11 , further comprising:

maintaining a persistent copy of the data event information at the event monitoring device;

storing the data event information using a database; and

updating an incoming events list in response to receiving the detected data event.

13. The method of claim 12 , wherein the updating the incoming events list is performed in response to said event monitoring device receiving new data event information from at least one of said plurality of enterprise brokers.

14. The method of claim 12 , wherein the updating the incoming events list is performed periodically.

15. The method of claim 12 , wherein the outputting the incoming events list to the user is accomplished using a graphical user interface.

16. The method of claim 11 , further comprising:

simulating a flow of simulated data events throughout an enterprise according to at least one communication topology;

determining propagation times of said simulated data events; and

comparing the propagation times of said simulated data events.

17. The method of claim 11 , further comprising generating an historical events list based on user input data event parameters in response to a user selection.

18. The method of claim 11 , wherein the detecting is accomplished using a listener module in said event monitoring device.

19. The method of claim 11 , wherein the establishing a connection includes reading a broker connections property file containing broker connection information.

20. An event monitoring system having at least one processor, said event monitoring system comprising:

an event monitor including a computer system; and

a plurality of enterprise brokers coupled to the event monitor using a network, each of the enterprise brokers including a client listener module configured to detect the occurrence of data events at the respective enterprise broker, each enterprise broker coupled to at least one broker client or application using the network, wherein the event monitor is configured to receive data event information from each enterprise broker connected thereto via the listener module, and to generate an incoming events list including the data event information received from each of the enterprise brokers connected thereto;

a simulation module configured to determine propagation times for simulated events flowing though at least one of the plurality of enterprise brokers and the at least one broker client or application according to at least one communication topology;

an event tracking module configured to generate an historical events list based on user input data event parameters in response to a user selection; and

a user interface configured to output the incoming events list, simulation results, and historical events list to a user.

21. The event monitoring system of claim 20 , further comprising an event database operably coupled to the event monitor, and wherein the event monitor is further configured to store data events using the event database.

22. The event monitoring system of claim 20 , in which the event monitor is further configured to simulate the flow of data events throughout an enterprise.

23. A computer-readable storage medium upon which is embodied a set of programmable instructions that when executed cause a processor to:

establish connections to a plurality of enterprise brokers;

detect the occurrence of one of a particular set of data events at at least one of said enterprise brokers;

output data event information associated with the detected data event to an event monitor;

use a simulator to determine propagation times for simulating events flowing though the at least one of said enterprise brokers according to at least one communication topology;

maintain a persistent copy of the data event information at the event monitor;

store the data event information using a database;

generate an incoming events list including the data event information received from the at least one of said enterprise brokers;

update the incoming events list in response to receiving the detected data event;

simulate events flowing though the at least one of the plurality of enterprise brokers;

generate an historical events list based on user input data event parameters in response to a user selection; and

output the incoming event list, simulation results, and historical events list to a user.

24. The computer-readable storage medium of claim 23 , further configured to cause the processor to update the incoming events list in response to receiving new data event information.

25. The computer-readable storage medium of claim 23 , further configured to cause the processor to update the incoming events list periodically.

26. The computer-readable storage medium of claim 23 , further configured to cause the processor to:

simulate the flow of simulated data events throughout an enterprise according to at least one communication topology;

determine the propagation times of simulated data events; and

compare the propagation times of simulated data events.

27. The computer-readable medium of claim 23 , further configured to cause the processor to generate a historical events list based on user input data event parameters in response to a user selection.

28. The computer-readable storage medium of claim 23 , further configured to cause the processor to establish a connection includes to one or more enterprise brokers by reading a broker connections property file containing broker connection information.

Assignments (12)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 6, 2017
From: SAVVIS COMMUNICATIONS, LLC; SAVVIS INC.
To: COLORADO WSC, LLC
Reel/Frame 041887/0106 →
CHANGE OF NAME Recorded Apr 6, 2017
From: SAVVIS COMMUNICATIONS CORPORATION
To: SAVVIS COMMUNICATIONS, LLC
Reel/Frame 042177/0819 →
RELEASE OF SECURITY INTEREST Recorded Jul 15, 2011
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: SAVVIS, INC.; SAVVIS COMMUNICATIONS CORPORATION
Reel/Frame 026601/0689 →
PATENT RELEASE Recorded Aug 5, 2010
From: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT, A DELAWARE LIMITED LIABILITY COMPANY
To: SAVVIS COMMUNICATIONS CORPORATION, A MISSOURI CORPORATION
Reel/Frame 024785/0942 →
SECURITY AGREEMENT Recorded Aug 5, 2010
From: SAVVIS COMMUNICATIONS CORPORATION, A MISSOURI CORPORATION; SAVVIS, INC., A DELAWARE CORPORATION
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 024794/0088 →
CHANGE OF NAME Recorded Feb 26, 2010
From: WELLS FARGO FOOTHILL, LLC
To: WELLS FARGO CAPITAL FINANCE, LLC
Reel/Frame 023985/0837 →
AGREEMENT REGARDING AGENCY RESIGNATION, APPOINTMENT AND ACCEPTANCE Recorded Dec 8, 2008
From: WELLS FARGO FOOTHILL, INC.
To: WELLS FARGO FOOTHILL, LLC
Reel/Frame 021936/0321 →
SECURITY INTEREST Recorded Jun 17, 2005
From: SAVVIS COMMUNICATIONS CORPORATION
To: WELLS FARGO FOOTHILL, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 016353/0633 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2005
From: CABLE & WIRELESS INTERNET SERVICES, INC.
To: SAVVIS ASSET HOLDINGS, INC.
Reel/Frame 017073/0142 →
MERGER Recorded May 12, 2005
From: SAVVIS, INC.
To: SAVVIS COMMUNCIATIONS CORPORATION
Reel/Frame 016004/0209 →
CHANGE OF NAME Recorded Dec 3, 2004
From: SAVVIS ASSET HOLDING, INC.
To: SAVVIS, INC.
Reel/Frame 016038/0526 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 13, 2002
From: GREEN, JAMES D.
To: CABLE AND WIRELESS PLC
Reel/Frame 013588/0799 →