Business event tracking system

• US 8,825,798 B1
• Filed: 02/02/2012
• Issued: 09/02/2014
• Est. Priority Date: 02/02/2012
• Status: Active Grant

• Current Assignee: Wells Fargo Bank NA (Wells Fargo & Company)
• Original Assignee: Wells Fargo Bank NA (Wells Fargo & Company)
• Inventors: Ortega, Robert J., Johnson, Terry Alan, Fung, Kwok-Keung
• Primary Examiner(s): Gillis, Brian J
• Assistant Examiner(s): TOKUTA, SHEAN S
• Application Number:
  US13/364,699
• Time in Patent Office: 943 Days
• Field of Search: 709/217, 705 1-912
• US Class Current: 709/217
• CPC Class Codes: G06F 11/3075 the data filtering being achieved in order to maintain consistency among the monitored data, e.g. ensuring that the monitored data belong to the same timeframe, to the same system or component
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

A networked system includes a processing system and a tracking system. The processing system includes applications for processing business events and between which the business events may be transferred. The tracking system monitors a status of each business event as the business event flows through the processing system. Each application of the processing system generates an event message at a predetermined stage and sends the event message to the tracking system. The event message includes correlation information generated by the application based on predetermined rules. The tracking system matches the event message to a previous event message based on the correlation information and assigns a tracking identifier of the previous event message to the current event message.

Claims

1. A system network comprising:

one or more computing devices with at least a processing unit and memory;

a processing system implemented by the processing unit and memory of at least one of the computing devices, the processing system including a plurality of applications, each application being associated with at least one other of the applications in an application pair, each application pair being configured to transfer business events there between, each application pair having a corresponding set of rules for generating correlation information based on the business events being transferred, different application pairs being capable of having different sets of rules for generating correlation information based on the business events being transferred, each application being configured to generate and send event messages including the correlation information when a business event occurs, the correlation information being generated and sent based on the set of rules for each application pair; and

a tracking system implemented by the processing unit and memory of one of the computing devices, the tracking system including an event collector configured to receive the messages from the applications, the tracking system also including an event aggregation module having a relations data store, the event aggregation module being configured to generate unique tracking identifiers for each business event, the relations data store containing a record of messages for a plurality of business events that are associated with each unique tracking number for each business event, the event aggregation module being configured to correlate related messages based at least in part on the correlation information contained in the messages, and to update the relations data store to associate the related messages pertaining to the business event with the respective unique tracking identifier, wherein the tracking system does not correlate related messages using the unique tracking identifiers.

2. The system network of claim 1, wherein related messages include messages sent by different applications in response to the same business event.

3. The system network of claim 1, wherein the event aggregation module also correlates the related messages based on source application information, destination application information, direction information, and status information.

4. The system network of claim 1, wherein each message includes at least current correlation information that is generated based on a current application pair between which a business event is being transferred.

5. The system network of claim 4, wherein some of the messages also include previous correlation information that is generated based on a previous application pair between which the respective business event was transferred.

6. The system network of claim 1, wherein the event aggregation module includes a hold data store in which the event aggregation module stores messages that the event aggregation module is unable to correlate.

7. A method of monitoring a processing system including a plurality of applications, the method comprising

receiving at least one message at an event collector module, each message identifying correlation information pertaining to a business event, the correlation information having been generated by an application of the processing system based on rules associated with an upstream-downstream application pair, different application pairs being capable of having different sets of rules for generating correlation information based on the business event, the correlation information being an identifier generated based on the rules;

determining whether the message is associated with a new business event or an existing business event;

storing the message in a relations data store with a newly generated unique tracking identifier if the message is associated with a new business event;

correlating the message to a previous message contained in the relations data store if the message is associated with an existing business event, wherein correlating the message includes matching at least the correlation information of the message to correlation information of the previous message;

identifying a unique identifier associated with the previous message; and

updating the relations data store to add the message in association with the identified unique identifier.

8. The method of claim 7, wherein each message received at the event collector module identifies a source application, a destination application;

and wherein correlating the message to a previous message includes verifying a potential match using at least one of the source application and destination application identified by the message.

9. The method of claim 7, wherein each message received at the event collector module includes a generate flag;

and wherein the message is determined to be associated with a new business event if the generate flag has a value of true and wherein the message is determined to be associated with an existing business event if the generate flag has a value of false.

10. The method of claim 7, further comprising:

adding the message to a reporting queue; and

presenting a report based on messages contained in the reporting queue.

11. The method of claim 10, wherein presenting the report based on messages contained in the reporting queue comprises generating an interactive web page displaying metadata pertaining to at least some of the messages contained in the reporting queue.

12. The method of claim 11, wherein the reporting queue includes a business activity monitoring (BAM) server queue.

13. The method of claim 10, wherein presenting a report based on messages contained in the reporting queue comprises sending a notification to a user in response to one of the messages contained in the reporting queue.

14. The method of claim 13, wherein sending a notification includes sending an email.

15. The method of claim 10, wherein presenting a report based on messages contained in the reporting queue comprises forwarding one of the messages to an application in the processing system.