US 6,738,757 B1Grant
System for database monitoring and agent implementation
Issue Date:2004-05-18
•12 Claims
•4 Drawing Sheets
Abstract
Comprising an engine and intelligent agents, the invented system monitors a data network for important events selected by the user and upon detection puts the information into action. Examples of actions that can be initiated include: updating ODBC compliant databases, sending E-mail (with file attachments) to a customer, partner or employee, merging data with and printing RTF documents, invoking VBScript or Jscript, running a program, executing SQL statements or stored procedures. The invented system incorporates a data monitor, process scheduler, and an event logging system. It establishes a snapshot of a data network, without replication, and compares this snapshot with the data viewed subsequently to determine if any data in the table being monitored has been changed, deleted, or added. Using an interface that guides users through the database selection process and that guides the user through the data server agent process, the query builder writes standard SQL statements to access and take action on data adds, changes and deletes.
Metadata
Assignee
- Workwise, Inc.
Inventors
- Thomas David Wynne
- Clifford John Monlux
Application Information
Application Number:US 09/416,460
Filing Date:1999-10-12
Priority Date:1999-06-02
Art Unit:7
Classifications
IPC:
G06F 1730
Field of Search:
707 3707201707204
Patent Drawings (4 sheets)
Description
[0002] This application is entitled to the benefit of Provisional Application Ser. No. 60/137,091, filed Jun. 2, 1999.
Background—field
[0003] This invention is in the field of client-server computer systems and the use of business rules to trigger informational events and update events as a result of the application of those rules.
Background—prior Art
[0004] The field of client server computing has grown tremendously in the past few years. In an enterprise environment many separate computer systems may contain many different electronic databases. These islands of data can cause a serious communication problem when a database changes. These changes may require that one or more people are informed, or a different database be corrected to reflect the new information. The present software tools available to the average user are very complicated to use. In many cases extensive programming experience may be required to do something as simple as linking two disparate databases together so that when one changes the other reflects that change. This invention simplifies the process of communicating when a database changes. The preferred embodiment of this invention also allows business rules to be applied to the database change. Both the type of information sent and even where that information may go can be determined by comparing the data that changed to a predetermined parameter. The outcome of that comparison then can determine the business rule that is to be applied to the changed data.
Brief Description of the Drawings
[0005] FIG. 1 is a pictorial representation of how the invented system is integrated into a network along with peripheral devices.
[0006] FIG. 2 is a pictorial representation of the elements that make up the present invention and their relationship to various other devices.
[0007] FIG. 3 is a block diagram representing the steps taken to monitor a database.
[0008] FIG. 4 is a block diagram representing the steps taken to initialize the system to monitor and update databases and files.
Detailed Description of the Invention
[0009] Comprising an engine and intelligent agents, the invented system monitors a data network for important events selected by the user and upon detection puts the information into action. Examples of actions that can be initiated include: updating ODBC compliant databases, sending E-mail (with file attachments) to a customer, partner or employee, merging data with and printing RTF documents, invoking VBScript or Jscript, running a program, executing SQL statements or stored procedures. The invented system incorporates a data monitor, process scheduler, and an event logging system. It establishes a snapshot of your data network, without replication, and compares this snapshot with the data viewed subsequently to determine if any data in the table being monitored has been changed, deleted, or added. Using an interface that guides users through the database selection process and that guides the user through the data server agent process the query builder writes standard SQL statements to access and take action on data adds, changes and deletes.
| TABLE 1 |
|---|
| Showing a Typical Relational Database Table |
[0010] Table 1. represents a table in a typical relational database. A database is an organized collection of information. The information may consist of numbers such as a persons age or strings which may be a collection of numbers and letters that carry information that cannot be put into a mathematical formula. An example of this is a persons address which contains a street number, but, of course, it would not make any sense to add, subtract or multiply such a number with any other number.
[0011] In database terminology a file is called a table, each record in the file is called a row, and each field is called a column.
[0012] The table above shows a column called a record number. Each row has a unique record number. In the table above, since it is a relational database, there is usually another table that contains more information about a particular field than is shown in the primary table. To be able to find the information in the second table that corresponds to the information in the first table there has to be a correspondence between the information in the first table and the information in the second table. The information in the first table that establishes that correspondence is called the primary key. That key must also be found in the second table, that key in the second table is called the foreign key.
[0013] What the present invention does is allow the user to select a database that is going to be monitored for changes. These changes may be a row that has been added or deleted or a field in a particular row has been added, deleted or changed. The user not only can select the database table to be monitored but the user can also select the particular columns that the user wants to be monitored.
[0014] In Table 1. assume that Field 1 is our primary field. The database is sorted (organized from top to bottom) alphabetically. Field 2 is assumed to be the field that we want to monitor for changes. When the data monitor first retrieves a snapshot of this database table it hashes the values of Field 2 in each row in the table in turn. If in Record 2 the data changes value in Field 2 then the hash value in the snapshot database will not match the current hash value of Field 2 Record 2. The actual data value of Field 2 Record 2 is then extracted from the database. If a record is deleted from the database table or added to the database table then we also have a mismatch in the hash values.
[0015] The data that has changed can then be evaluated using the tools provided by this invention. Depending on what the user decides is the criteria the invention then acts as an agent and takes another predetermined action.
[0016] When more than one field of a particular record is monitored the data agent monitor first determines that a change has occurred by comparing the hash values. The monitor then determines which field changed. The changed data then has business rules applied to said data and the data is subsequently packaged and transmitted to the appropriate predetermined agent.
[0017] FIG. 1 shows a typical network of devices that may be a local area network (LAN) 15 to which the querying site is connected or remote to the site and connected to the site via a wide area network (WAN). The Data Agent Server 18 is composed of two primary structural elements. They are the engine and the software agents. The engine is in turn composed of the shell, the database monitor agent and the data log agent. These three are tightly integrated to schedule, launch and record Data Agent Server processes. The engine enables the user to coordinate the activities of the software agents and to generate an automatic logfile of all scheduled activity. The snapshot database 12 is the memory location where the values representing the state of the database being monitored are kept. The values are kept in a condensed form known in the art as the hash value of the data being monitored. The Data Agent Server 18 can monitor databases and file servers and also update databases and file servers. The SQL file server 11 may contain the database to be monitored and the Oracle server may contain the database that is updated with changes that occur in the SQL server 11. It is also possible that a change in the SQL server 11 will require a change in the file server 10.
[0018] The software agents that are resident in the Data Agent Server may also be used to communicate to a fax machine 14 to send a fax concerning the date that changed, use a printer 20 to print out a report, or generate E-mail, or to send the changed information to a remote location via a World Wide Web (WWW) server 16.
[0019] FIG. 2 shows another representation of the preferred embodiment. The database monitor agent 30 and the file monitor agent communicate with the databases to be monitored 44, 46, 48, and the file servers to be monitored 50. The time intervals that the user selects to monitor the database and file servers are stored in memory in the scheduler 34. At this predetermined interval the database monitor agent 30 or as the case may be, the file monitor agent 31, query the predetermined data to be monitored and compare that data with the data values stored in memory in the snapshot memory location 32. If a change is determined to have occurred the new data is then examined according to a set of predetermined business rules residing in the respective agents. The data that has changed is then packaged into a data object, recorded in the event log 33 and handed off to the appropriate predetermined agent. That agent may be the print agent 36, the script agent 38, the E-mail agent 40, the fax agent 42 or the update agent 52. This is not an exhaustive list of agents but is a representative sample of the agents that may be engaged by the data or file monitor agents to be activated in the case of the change. It is also possible that agents may be activated when the data and file monitor agents detect no change in the databases or files. This may often be as significant as a change would be.
[0020] FIG. 3 describes how the data is monitored, compared to previous data, and how the results of the comparison are handled. When the data/file monitor agent 60 is triggered by the time scheduler 68 then the agent communicates with the database/file that the user has predetermined 62. The data/file monitor then returns a snapshot of the current data 64 while dwelling on the designated row. The new snapshot is then compared to the previous snapshot 66 to determine if any data has been added, deleted, or changed. If there is a difference 72 then the predetermined update agent is engaged 74. If there is no change then the monitor request returns to the schedule queue 70. When the user is interested in using the update agent to take an action when there is no change in the data then the user can select that the agents engage when this occurs.
[0021] FIG. 4 shows the steps a user takes to initialize the system for use in monitoring, updating or informing when a database or file has been added to, deleted from, changed or left the same. The process is started 80 when the user starts the executable run file that applies the invented application software to the users operating system. The user then names the process that is to be generated 82. Next the process that the user wants to run is scheduled 84, the schedule can vary anywhere from every minute, every hour, every week, every month or anything in between. Then the source of the data or file that is to be monitored must be selected 86, followed by selecting the particular database and file 88. If selecting a database then it is necessary to pick the particular database table and fields that are to be monitored. If there are tables to be joined 92, a term of database art well known by practitioners, the user selects the joins that are required 100. Also the criteria that will trigger an update must be selected 94. The user then selects the particular agents that the user desires to be updated or informed of the change 96 and configures that update agent to perform the updating 98. This concludes the initialization 102.
[0022] When the preferred embodiment of the invention needs to communicate to the change agents what the data that changed is, then the preferred embodiment packages the changed data into an object prior to handing the changed data off to the change agent. The following pseudocode that packages the information that is handed off to the update agents will be easily recognized by those familiar with the programming art.
[0023] Terms: Data item—One distinct piece of information, for example a name, address or number are all Data Items in this context.
[0024] Recordset—The set of data to be stored. Usually the result of a query against a database.
[0025] Collection—A pre-defined, zero based array which is inherent in the object definition.
[0026] Adding Data:
[0027] Query source database or read formatted data file to obtain the desired data block or recordset.
[0028] Create a new instance of the PackageItem object.
[0029] Assign (Set) the PackageItem's Value, ItemType, ItemDefinedSize and ItemTypeName properties for the first data item with the Package Object's WriteItem Method.
[0030] WriteItem(“Name”,Y, 100, pkgString)
[0031] Use the Package Object's Add method to append the Packageitem to the PackageItem collection of the Package Object (Assuming that an instance of the Package Object has been created. If not, then create it).
| MyDataObj.Add “Name” | ‘MyDataObj is the name of Package |
[0032] Repeat the last three steps above until the entire recordset or data block has been assigned to PackageItems and those PackageItems have been added to the Package object.
| Dim I as integer | |
| For I=0 To X |
[0033] Retrieving Data:
[0034] Use the Package object's Data or Read Property to obtain the data item(s) from the package object. This function returns all the data in the object as a string.
| Astring = MyDataObj.Read | ‘AString is a string variable to hold the data |
[0035] To retrieve one data item at a time, use the Package object's Item property
[0036] Astring=MyDataObj.Item(Index)
[0037] To verify the existence of a data item (Packageltem) in the object, use the ItemExists property of the Package Object.
[0038] If MyDataObj.ItemExists(Index) Then
[0039] End If
[0040] Object Management:
[0041] To clear (empty) a Package Object instance, use the clear method.
[0042] MyDataObj.Clear
[0043] Or destroy the instance of the object.
[0044] MyDataObj=Nothing
[0045] To obtain the number of PackageItems contained in the Package Object, use the Count property of the Package Object.
[0046] Aint=MyDataObj.Count
[0047] To obtain the Name of the person who created the current instance of the object, use the Created By property of the Package object.
[0048] Astring=MyDataObj.CreatedBy
[0049] Similarly to obtain the date when the instance was created, use the DateCreated property of the Package object.
[0050] Adate=MyDataObj.DateCreated
[0051] To load data from a file (formatted), use the Load function of the Package object.
[0052] MyDataObj.Load Filename
[0053] To get the name of the Package object instance use the Name property.
[0054] Astring=MyDataObj.Name
[0055] To get or set the owner of the Package object instance, use the owner property.
| Astring = MyDataObj.Owner | ‘Gets the Owner | |
| MyDataObj.Owner = Astring | ‘Sets the Owner | |
[0056] To remove a data item (PackageItem) from the Package object, use the Remove method of the package object.
[0057] MyDataObj.Remove Packageltem(Index)
[0058] To write the Package object contents to a data file, use the Store method of the Package object.
[0059] MyDataObj.Store Filename
[0060] To append any additional data to the Package object, use the Tag property of the Package object.
[0061] MyDataObj.Tag=“Zevatech”
[0062] This package object is handed off to the preselected agent to communicate the change to the preselected entity. While preferred embodiments of the invention have been shown and described, it will be apparent to those skilled in the art that various modifications may be made in these embodiments without departing from the spirit of the present invention. For that reason, the scope of the invention is set forth in the following claims.
Claims
What is claimed is:
1. A method of comparing data contents contained in user predefined fields of a user predefined database table of a user predefined database at user predefined intervals, the method allowing for one or more of a plurality of actions to be taken, the method comprising the steps of:
a) sending a query to said user predefined fields, extracting a first instance number representing the data contents of one or more fields associated with a primary field, wherein said one or more fields used in extracting said first instance number are selectable by a user and wherein said first instance number is a hashed value, and placing said first instance number in a “snapshot” data record;
b) at said user predetermined time interval, sending said query to said predefined fields, and extracting a second instance number representing the data contents of said one or more fields associated with said primary field at said user predetermined interval, wherein said second instance number is a hashed value;
c) comparing said first instance number with said second instance number, wherein a mismatch between the first instance number and the second instance number indicates the data contents of said one or more fields associated with said primary field have changed over said predetermined intervals;
d) applying a business rule to determine which of said plurality of actions to take if a mismatch exists between the first instance number and the second instance number; and,
e) performing at least one of said plurality of actions if no mismatch exists between the first instance number and the second instance number.
2. The method of claim 1 further including the acts of packaging said changed data into a software object format that is thereby sent to at least one update agent.
3. The method of claim 2 wherein the update agent communicates said changed data to at least one of a plurality of destinations preselected by the user.
4. The method of claim 3 further including the acts of recording into an accessible and retrievable memory location the acts of determining when said data contents changed and the acts of which update agents were activated whenever said data contents changed and whenever said update agents were activated.
5. A computer implemented system for comparing data contents contained in user predefined fields of a user predefined database table of a user predefined database at user predefined intervals, wherein said computer implemented system allows one or more of a plurality of actions to be taken, the computer implemented system comprising:
a) sending a query to said user predefined fields, extracting a first instance number representing the data contents of one or more fields associated with a primary field, wherein said one or more fields used in extracting said first instance number are selectable by a user and wherein the first instance number is a hashed value, and placing said first instance number in a “snapshot” data record;
b) at said user predetermined interval, sending said query to said predefined fields, and extracting a second instance number representing the data contents of said one or more fields associated with said primary field at said user predetermined interval, wherein said second instance number is a hashed value;
c) comparing said first instance number with said second instance number, wherein a mismatch between the first instance number and the second instance number indicates the data contents of said one or more fields associated with said primary field have changed over said predetermined interval;
d) applying a business rule to determine which of said plurality of actions to take if a mismatch exists between the first instance number and the second instance number; and,
e) performing at least one of said plurality of actions if no mismatch exists between the first instance number and the second instance number.
6. The system of claim 5 further including packaging said changed data into a software object format that is thereby sent to at least one update agent.
7. The system of claim 6 wherein the update agent communicates said changed data to at least one of a plurality of destinations preselected by the user.
8. The system of claim 7 further including recording into an accessible and retrievable memory location the acts of determining when said data contents changed and the acts of which update agents were activated whenever said data contents changed and whenever said update agents were activated.
9. A computer implemented system for comparing data contents contained in user predefined fields of a user predefined database table of a user predefined database at user predefined intervals, wherein said computer implemented system allows one or more of a plurality of actions to be taken, the computer implemented system comprising:
a) means for sending a query to said user predefined fields, extracting a first instance number representing the data contents of one or more fields associated with a primary field, wherein said one or more fields used in extracting said first instance number are selectable by a user and wherein said first instance number is a hashed value, and placing said first instance number in a “snapshot” data record;
b) at said user predetermined interval, sending said query to said predefined fields, and extracting a second instance number representing the data contents of said one or more fields associated with said primary field at said user predetermined interval, wherein said second instance number is a hashed value;
c) comparing said first instance number with said second instance number, wherein a mismatch between the first instance number and the second instance number indicates the data contents of said one or more fields associated with the primary field have changed over said predetermined interval;
d) applying a business rule to determine which of said plurality of actions to take if a mismatch exists between the first instance number and the second instance number; and,
e) performing at least one of said plurality of actions if no mismatch exists between the first instance number and the second instance number.
10. The system of claim 9 further including packaging said changed data into a software object format that is thereby sent to at least one update agent.
11. The system of claim 10 wherein the update agent includes means for communicating said changed data to at least one of a plurality of destinations preselected by the user.
12. The system of claim 11 further including means for recording into an accessible and retrievable memory location the acts of determining when said data contents changed and the acts of which update agents were activated whenever said data contents changed and whenever said update agents were activated.
Patent Citations (22)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5216603(A) | 1993-06-01 | Flores et al. | Applicant |
| US5287496(A) | 1994-02-01 | Chen et al. | Examiner |
| US5338255(A) | 1994-08-01 | Akehurst | Applicant |
| US5369757(A) | 1994-11-01 | Spiro et al. | Examiner |
| US5530939(A) | 1996-06-01 | Mansfield et al. | Examiner |
| US5561793(A) | 1996-10-01 | Bennett et al. | Applicant |
| US5666526(A) | 1997-09-01 | Reiter et al. | Applicant |
| US5701480(A) | 1997-12-01 | Raz | Examiner |
| US5734837(A) | 1998-03-01 | Flores et al. | Applicant |
| US5765028(A) | 1998-06-01 | Gladden | Examiner |
| US5926819(A) | 1999-07-01 | Doo et al. | Examiner |
| US5991758(A) | 1999-11-01 | Ellard | Examiner |
| US5999943(A) | 1999-12-01 | Nori et al. | Examiner |
| US6085197(A) | 2000-07-01 | Federighi et al. | Examiner |
| US6112197(A) | 2000-08-01 | Chatterjee et al. | Examiner |
| US6125390(A) | 2000-09-01 | Touboul | Examiner |
| US6151602(A) | 2000-11-01 | Hejlsberg et al. | Examiner |
| US6167535(A) | 2000-12-01 | Foote et al. | Examiner |
| US6237001(B1) | 2001-05-01 | Bamford et al. | Examiner |
| US6243718(B1) | 2001-06-01 | Klein et al. | Examiner |
| US6341287(B1) | 2002-01-01 | Sziklai et al. | Examiner |
| US6434681(B1) | 2002-08-01 | Armangau | Examiner |