CA2121483C - Open office directory database views - Google Patents
Open office directory database views Download PDFInfo
- Publication number
- CA2121483C CA2121483C CA002121483A CA2121483A CA2121483C CA 2121483 C CA2121483 C CA 2121483C CA 002121483 A CA002121483 A CA 002121483A CA 2121483 A CA2121483 A CA 2121483A CA 2121483 C CA2121483 C CA 2121483C
- Authority
- CA
- Canada
- Prior art keywords
- local
- view
- views
- entry
- stored
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
- G06F16/24534—Query rewriting; Transformation
- G06F16/24539—Query rewriting; Transformation using cached or materialised query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/217—Database tuning
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
- Y10S707/99934—Query formulation, input preparation, or translation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
Abstract
An open office directory system stores information in the form of entries in a global database and views in a local database along with a time stamp indicating the date the view was originally written or last modified. Subsets of the selected global entries are stored as views in a local database with the time stamp of the last generation or modification of that view in the global data-base. The entries in the global database are queried periodically by the local site to compare the time stamps of the local views with the respective entries in the global database. The result of a non-comparison is to update the local view including its time stamp to agree with the global database entry(s).
Description
._, 21~1~~~
BACKGROUND OF THE INVENTION
1. Scope of the Invention This invention relates to Data Processing Systems, and more specifically to the ability of providing selected and automatically updated database views.
BACKGROUND OF THE INVENTION
1. Scope of the Invention This invention relates to Data Processing Systems, and more specifically to the ability of providing selected and automatically updated database views.
2. Description of the Prior Art In the fall of 1988 two of the worlds foremost standards organizations, the Consultative Committee on Internal Telephone and Telegraph (CCITT) and the International Standards Organization (ISO), set forth a standard for global Directory Service.
Even through the two organizations collaborated on setting this standard, they each maintain their own name for it. To the CCITT it is knows as CCITT recommendation X.500, whereas for the ISO it is known as International Standard 9594. To simplify the disparate naming for the virtually identical standard, most people refer to it as the Open Systems Interconnection Directory Service - or the OSI
Directory.
The architecture of this OSI directory can be described as a group of cooperating server processes which collectively hold a single global information base about objects of interest and provide read and write access to this information through a query based interface. In essence, the OSI Directory is an iteration of a Distributed Data Base which exhibits some very specific characteristics.
Four characteristics of the OSI Directory which placed some constraints on directory use are:
- Access to the Directory Information is through an interactive query/response mechanism. . .
<. _ _ W li~~
2 7. 12 93 WO 93/12499 ~ ~ PCT/US92/04151 - The scope of distribution for the OSI Directory is global in nature.
- The information held about objects tends to be long lived in nature and is thus rarely changed.
- All the information for a particular object of interest is maintained in a single Directory entry at only one of the cooperating servers.
Because of the access mechanism used and the global nature of the Directory Information base, any service request could be distributed across a number of widely separated but cooperating Directory servers. And real performance constraints can arise when the Directory is used in a local manner. The effect is that any Directory Operation which is targeted to gather information from a number of widely distributed Directory entries can be an extremely time consuming and cumbersome operation to handle in an on-line fashion.
One popular method of eliminating the burden of such lengthy request times is to provide an adjunct process which issues the global queries in a scheduled but off-line fashion. The results are then subsequently stored in a non-volatile cache, typically a local file, and are available for quick local access by the end service consumers. Given the long lived and stable characteristic of the information, the use of a scheduled off-line caching method is an appropriate approach.
The OSI Directory was intended to provide service to a wide range of consumers, each with a special interest. Any particular Directory Service consumer may only be interested in a subset of the total information stored in a particular entry or group of entries.
The single entry characteristic, described above, creates a need for a querying ability which only retrieves selected information. The OSI
Directory, through options provided in its query operations (Read & Search) does in fact fulfill this selected information requirement.
As further pertinent background information one must consider the concepts of traditional relational databases. Many traditional relational databases are modelled in terms of tables, columns and rows. And if one were to make an analogy of the traditional relational database model to the WQ 93/12499 : , ~-$ PCT/US92/04151 OSI Directory Information Base model the following correlations would be true.
- A database table, more appropriately known as a relation, corresponds to a set of one or more instances of Directory entries all of the same Object Class.
- A database column, more appropriately known as an attribute, exactly corresponds to a Directory entry attribute.
- Finally, a database row, more appropriately known as a tuple, corresponds to one instance of a Directory entry.
A further refinement of relational databases concerns the concept of a database views. Although there is a large body of work published on this particular subject, one such work "Distributed Databases Principals &
Systems", by Stefano Ceri and Giuseppe Pelagatti, McGraw-Hill, 1984, pp.
330-332, gives the following classic definition of database views as provided through the industry standard SQL language.
"In SQUDS, views are defined as the result of an SQL select statement, producing a result relation from one or more operand relations.
The result relation gives to the user a new "view" of the database (or external schema in the ANSI-SPARC terminology), which is built through the standard query language."
To paraphrase Ceri and Pelagatti, a view can be likened to a new table formed from a selected subset of other tables. A similar concept can be achieved with the OSI Directory. By using existing OSI Directory query operations in a fashion which corresponds to an SQL select, one can create a new set of related entries from an existing set(s). This new set of selected entries corresponds to a relational database view.
Objects of the Invention Accordingly, it is an object of the invention to remove the burden of rather lengthy global Directory queries from the end directory service consumer.
WO 93/12499 ~ ~. ~ PCT/US92/04151_ It is also the object of this invention to present the cached results, in a form which corresponds to selected relational database views.
Summary of the Invention An Open Office Product Architecture of an Open System includes a global database which stores information in the form of entries for an entire organization. The organization may be organized in divisions. Each division may be organized in operations. Each operation may include a number of organizations. An entry for an organization may include an object class, in this case, people. Therefore the entry could include an employee name and number, an employee job title, an E-mail address, an organization identification and a time stamp. The time stamp includes the date and time the entry was made or last modified.
The entries which apply to a particular division or operation are stored locally. The information in each local entry may be a selected subset of the entry stored in the global database, but it will include the time stamp read from the global database the last time the global database was queried for that entry.
Each entry (view) is configured by the Systems Administrator and is called upon periodically, typically once an hour, to check if there are any changes to the global database that have an impact on, and require an update to the local views.
Scheduling information controls when the application that builds and updates the views comes up and runs.
The update process is controlled by storing a pair of time stamp values, or time frame, which define a window in time from which completed update transactions are to be extracted, and thereafter periodically checking the global database for further changes which have occurred during subsequent and later windows in time. Thus only the changed entries are retrieved and updated in the views.
Also provided are the selection criteria and predicates for reading selected attributes from an entry or a number of entries stored in the global database.
The invention may be summarized, according to a first aspect, as a method of formulating a search for changed entries in a global database and updating local views including the steps of at selected time frame intervals, A. building a list of all installed local view names;
B. developing a list of desired attributes for display in each local view identified in the list of installed local view names, the attributes for each local view including a latest time stamp value for the local view wherein each latest time stamp value indicates the time of a last change to the local view and definitions of the local view; C. selecting a local view name from the list of installed local view names;
D. reading from the attribute list for the selected local view name the view definitions and the latest time stamp value for the selected local view name; E. searching the global database using said view definitions to locate an entry corresponding to the selected local view name; F. when the entry corresponding to the selected local view name is a non-leaf entry, selecting a next entry; G. when the entry corresponding to the selected local view name is a leaf entry, comparing the time stamp value of the entry with the latest time stamp value for the selected view name from the list of attributes corresponding to the selected local view name; H. updating the local view corresponding to the selected local view name when the time stamp value of the entry is different from the latest time stamp value for the selected view name; I. determining when all entries corresponding to the selected local view name are processed; J. selecting a next entry corresponding to the selected local view name when all entries corresponding to the selected local view name are not processed; K. selecting a next local view name when all entries corresponding to the selected local view name are processed; and L. repeating steps C through K until all local view names in the list of all installed local view names are processed.
According to a second aspect, the present invention provides an Open Office Directory System for building and updating views stored in a local subdirectory comprises:
global database means for storing a global distributed directory; a builder means for controlling when an application that builds and updates said views is to be executed; a view management means for periodically scanning the global database for the views stored in the local subdirectory for changes in the views stored in the local subdirectory and for storing a latest time stamp value in attributes associated with each view in the local subdirectory wherein each latest time stamp value represents a time at which the associated view stored in the local subdirectory was last changed; an update means coupled to said builder means for working cooperatively with the view management means to determine a change in said global database for a view stored in the local subdirectory in a current update scan by storing a time frame of a last update scan in said update means wherein the view management means is responsive to the stored time frame of the last update scan for comparing the latest time stamp values of the views stored - 5a -in the global database for the views stored in the local subdirectory with the stored time frame of the last update scan and determining when a change in a view stored in the local subdirectory occurred subsequent to the last update scan; a definition means coupled to said update means and to global database means for providing selection criteria and predicates from the attributes associated with views stored in the local subdirectory for each view stored for which a change is determined in said current update scan to have occurred subsequent to the last update scan for reading the selected attributes from entries stored in said global database means for which a change has occurred subsequent to the last update scan; and an entry means coupled to said global database means for storing the local entries which are received from said global database means in the local subdirectory, thereby updating the views stored in the local subdirectory.
Brief Description of the Drawings Figure 1 shows a block diagram of an Open Office Product Architecture of an Open Systems.
Figure 2 shows a block diagram of the Directory Service.
Figure 3 presents a Functional Component design illustration of the View Builder Application.
Figure 4 is a block diagram showing the operation of the View Builder Application.
Figure 5 is a block diagram of the View Builder Scheduling Daemon.
Figures 6A, 6B, 6C and 6D show the iterations to - 5b -develop the local views.
Description of the preferred Embodiment Figure 1 shows a block diagram of an Open Office Product Architecture of an Open Systems offering of a UNIX
iteration of E-mail. An Open Office System 1 includes three service components, a Data Service 2, a Mail Service 4 and a Directory Service 6.
Data Service 2 retrieves work flow packages, calendar scheduling packages and mail data. Mail Service 4 is the local and remote mail handling service which is based on X.400. The Directory Service 6 is used by both the Data Service 2 and Mail Service 4 to do name and address mapping.
As an example, the Data Service 2 would query the Directory Service 6 for the name of an office data service and the name of an office service user. The Mail Service 4 would obtain mail addressing information including a list of possible names if the user was not sure of the correct spelling of the name.
Figure 2 shows a block diagram of the Directory Service 6 which includes a View Builder Scheduling Entry 12, Views Update Control Entries - 5c -~121~8~ _ 14, Views Definition Entries 16 and Views Alias Data Entries 18 which are all stored in a local subdirectory, and Distinguished Name Data Entries (Database) 20 which are part of the global distributed directory date base.
Database 20 is the global directory database, and although to the local directory user a virtual unified view is presented, the actual physical global allocation of the data is hidden and only known to the internal directory service components.
A view is a selected subset of an entry stored in Database 20. View Builder 12 contains scheduling information which controls when the application that builds and updates the views comes up and runs. This entry is configured by the Systems Administrator and is called upon periodically, typically once an hour, to check if there are any changes to Database 20 that have an impact on, and require an update to the local views. Every entry in the Database 20 includes the date and time the entry was rnade, or last modified, and is in the form of a time stamp.
Views Update 14 controls the update process by storing the time stamp of the last update scan, and thereafter periodically checks the Database 20 via View Builder 12 for changes which have occurred after the time of the last update scan. Thus only the changed entries are retrieved and updated in the views.
Views Definition 16 provides the selection criteria and predicates for reading selected attributes from an entry or a number of entries stored in Database 20. The attributes could include job description, phone number, organization, and the like.
Views Alias Data Entry 18 stores the local entries which are received from Database 20 and include the selected attributes.
Directory Server Process 10 is a commercially available X.500 server software program.
The View Builder Application 22, when run, reads the data structure of Views Definition 16 to determine how to formulate the operation to search for changed entries; and uses the control structures which it updates after it does the read to precisely specify the search operation in Database Vl~ 93/12499 ~~ ~ PCT/US92/04151 20 for time stamps later than the time stamps stored in Views Update 14.
View Builder 22 then updates the local database entries in Data Entries 18.
View Client Applications 26 and 28 are end user applications that use the entries in Data Entries 18 or Database 20. As an example, Application 26 could be a misspelled name finder, and Application 28 could correct misspelled addresses, or verify zip codes.
Other Directory Clients 30 may also be connected to Server 10.
Figure 3 presents a Functional Component design illustration of the View Builder application. The essence of this application is the View management Routine 22-2 which is described in further detail in Figure 4. In order for the View Management routine 22-2 to pertorm its task it relies on and uses the services of; A Unix Kernel calls 22-7 for memory management of Allocated Memory 22-1, an X.500 Directory API 22-9 for Directory query &
modify operations, a Directory Operation Formatting API 22-4, and a Directory Argument Formatting API 22-6.
The View Management Routine 22-2 functional component controls the order of processing when scanning the global directory for changed entries; similarly it controls the order of processing when the local views are updated to reflect these changes. It makes use of all the other functional components comprising the View Builder Application.
Directory Operation Formatting API 22-4 is called directly by the View Management Routine 22-2 formatting and executing a Directory operation on its behalf.
Directory Argument Formatting API 22-6 is called directly by Directory Operation Formatting API 22-4 in support of the Directory Operation Formatting process, this is the indirect result of the call made to Directory Operation Formatting API 22-4 by the View Management Routine 22-2.
Directory API 22-9 are ultimately called by Directory Operation Formatting API 22-4 on behalf of the View Management Routine 22-2.
These API's directly access the Directory Server.
Unix Kernel calls 22-7 is called directly and indirectly by View Management Routine 22-2, Directory Operation Formatting API 22-4, and WO 93/12499 ~ ~ 1 ;3 PGT/US92/04151,_ Directory Argument Formatting API 22-6 for standard operating system service functions.
The interaction of all these functional components comprises the View builder application.
Figure 4 is a block diagram showing the operation of the View Builder Application 22 of Figure 2 which reads the data structure of Views Definition 16 to determine how to formulate the operation to search for changed entries. View Builder 22 then uses the control structures which it updates after it does the read to precisely specify the search operation in Database 20 for time stamps later than the time stamps stored in Views Update 14.
View Builder 22 then updates the local database entries in Data Entries 18.
Block 22-8 starts the search and update operations.
Block 22-10 searches Views Definition 16 for the names of all installed Views. Then block 22-12 builds a List in memory 22-1 of all the installed view names and sets a pointer to the first entry in the List.
Block 22-14 reads a listed by view name in Views Definition 16 of Figure 2 for the selected attributes, the predicate, whether a time stamp is present and the name of a parent entry in Database 20. The parent entry name establishes a downward starting point for querying into the data tree in Database 20 for all subordinate children entries.
Block 22-16 reads Views control 14 for the latest time stamp value for the entry.
Block 22-18 searches Database 20 for the entries defined by the search in blocks 22-14 and Directory Argument Formatting API 22-16.
Decision block 22-20 determines if the entry satisfying the criteria and returned by block 22-18 is to be updated to Views Control 14, if so then Block 22-24 updates the entry in Views Control 14. Then decision block 22-26 may call block 22-18 to start the search for the next entry, or call block 22-28 to check for more View Names in the List. The entries are either leaf entries or non-leaf entries. If decision block 22-20 determined the entry returned by 22-18 was not a non-leaf then a leaf was found. Found leaf entries satisfying all of the criteria and are added or updated in Views Data WQ 93/12499 '~ ~ ,~ ~ ~.,~ ~ PCT/US92/04151 Entry 18 in block 22-22.
Then decision block 22-26 may repeat the loop to block 22-18 until all of the leaf entries are stored in Views Data Entry 18, then Block 22-28 is invoked to determine if all View Names in the list have been processed. If more names are in the View Name List the list pointer is moved to the next entry by block 22-30, if not the process ends at 22-32.
Referring to Figure 5, View Builder Scheduling Daemon 24, when requested by the Unix kernel time scheduling service (Chron} 24-2, runs on the UNIX system and does a Database 20 read of View Builder Scheduling Entry 12, in block 24-4. Decision block 24-6, using the information it retrieved from View Builder 12, compares the elapsed time since last running and, if appropriate, either schedules (fork) 24-10 the View Builder Application 22, or suspends it at block 24-8. If and when the View Builder Application 22 runs and completes its task, control is returned back in line at block 24-8 at which point the View Builder Scheduling Daemon 24 sleeps.
Figures 6A, 6B, 6C and 6D show, in a typical example, the iterations of Figure 4 to develop the local views. Figure 6A shows the attributes in the local views and the information in the Database 20 immediately after installation.
The Database 20 stores a number of trees including a tree headed by a US tree 51 which includes a Company entry 53 which has, as an example, a time stamp 2. Tree 51 includes a non-leaf Research & Development (R &
D) entry 55 with a time stamp 2, and a non-leaf Marketing (Mkt) entry 57 with a time stamp 3. Under R & D 55 are two leaf entries, Art L 59 with a time stamp 003 and Geo G 61 with a time stamp 004. Under Mkt 63 is a leaf entry for Joe S with a time stamp 002.
A number of attributes are shown for each entry. A local tree 50 is subordinate to US entry 51 and is accessed through server 10 at Local Service Name 56. Then under control of View Management routine 22-2, Directory Formatting Operation 22-4 and the Directory Argument Formatting API 22-6 of Figure 3, Block 22-10, Figure 4, searches Views Definition 16 for all installed view names. Block 22-12 builds a list of all installed view names in memory 22-1. Block 22-14 retrieves for a names view; the starting point of where to search, - i.e. Base Name = US/COMPANY;
the definition of the selected attributes, - i.e. name, job title, E-mail number and organization; the predicate, - i.e. object class=people and time frame=present as shown in block 58.
Block 22-16 searches for any view update control entries, if this is the first pass through none will be found as creation of this type of entry is the result of the later operation performed by block 22-24.
If this is not the first pass then Views Control entry 14 is returned from block 60, identified as time 1 (TS 1 ) which describes the tree 51 and Company 53 identifiers in Database 20, and a highest time stamp 0.
Figure 6B shows local tree 50 after pass 1. There is not change in block 58 of Views Befinition 16, however under control of block 22-18 of Figure 4, Views Control 14 searches Database 20 for US/COMPANY
and finds tree 51. Decision Block 22-20 finds that the first entry TS 1 is a non-leaf entry and block 22-24 updates Views Control 14 by TS 1 block 62 with a highest time stamp 3. Decision block 22-16 determines that not all entries were processed and branches to block 22-18. The loop, blocks 22-18, 22-20, 22-24 and 22-26 are repeated to store TS2 R&D block 64 with a highest times stamp ;0 and TS3 Mkt block 66 with a highest time stamp 0 in Views Control 14.
Figure 6C shows local tree 50 after pass 2. There is no change in block 58 of Views Definition 16. Views Control 14 now includes TS 1 block 62 with the same time stamp 3, TS2 R&D block 64 with a highest time stamp 4 and TS3 Mkt block 66 with a highest time stamp 2. The time stamps- are updated from blocks 59, 61 and 63 respectively and were received via blocks 22-18, 22020, 22-24 and 22-26 as above.
Decision block 22-20 determines that the next entry is a leaf entry and branches to block 22-22 which adds the first leaf entry 68 to Views Data 18. The loop of blocks 22-22, 22-26, 22-18 and 22-20 are repeated to add leaf entries 70 and 72 to Views Data 18. Dote that Blocks 68, 70 and 72 of Views Data 18 each include the selected data and its tree path in Database ~J~i~J
W,Q 93/12499 ~ 8 ~ PCT/US92/04151 20.
Decision block 22-28 tests if the View List Pointer is set to the end of the list and if not, calls block 22-30 to advance the pointer to the next View Name. Otherwise the operation ends at block 22-32 as is the case in this example and Block 6D shows the result at the end of this final pass.
While the invention has been shown and described with reference to the preferred embodiment thereof, it will be understood by those skilled in the art that the above and other changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Even through the two organizations collaborated on setting this standard, they each maintain their own name for it. To the CCITT it is knows as CCITT recommendation X.500, whereas for the ISO it is known as International Standard 9594. To simplify the disparate naming for the virtually identical standard, most people refer to it as the Open Systems Interconnection Directory Service - or the OSI
Directory.
The architecture of this OSI directory can be described as a group of cooperating server processes which collectively hold a single global information base about objects of interest and provide read and write access to this information through a query based interface. In essence, the OSI Directory is an iteration of a Distributed Data Base which exhibits some very specific characteristics.
Four characteristics of the OSI Directory which placed some constraints on directory use are:
- Access to the Directory Information is through an interactive query/response mechanism. . .
<. _ _ W li~~
2 7. 12 93 WO 93/12499 ~ ~ PCT/US92/04151 - The scope of distribution for the OSI Directory is global in nature.
- The information held about objects tends to be long lived in nature and is thus rarely changed.
- All the information for a particular object of interest is maintained in a single Directory entry at only one of the cooperating servers.
Because of the access mechanism used and the global nature of the Directory Information base, any service request could be distributed across a number of widely separated but cooperating Directory servers. And real performance constraints can arise when the Directory is used in a local manner. The effect is that any Directory Operation which is targeted to gather information from a number of widely distributed Directory entries can be an extremely time consuming and cumbersome operation to handle in an on-line fashion.
One popular method of eliminating the burden of such lengthy request times is to provide an adjunct process which issues the global queries in a scheduled but off-line fashion. The results are then subsequently stored in a non-volatile cache, typically a local file, and are available for quick local access by the end service consumers. Given the long lived and stable characteristic of the information, the use of a scheduled off-line caching method is an appropriate approach.
The OSI Directory was intended to provide service to a wide range of consumers, each with a special interest. Any particular Directory Service consumer may only be interested in a subset of the total information stored in a particular entry or group of entries.
The single entry characteristic, described above, creates a need for a querying ability which only retrieves selected information. The OSI
Directory, through options provided in its query operations (Read & Search) does in fact fulfill this selected information requirement.
As further pertinent background information one must consider the concepts of traditional relational databases. Many traditional relational databases are modelled in terms of tables, columns and rows. And if one were to make an analogy of the traditional relational database model to the WQ 93/12499 : , ~-$ PCT/US92/04151 OSI Directory Information Base model the following correlations would be true.
- A database table, more appropriately known as a relation, corresponds to a set of one or more instances of Directory entries all of the same Object Class.
- A database column, more appropriately known as an attribute, exactly corresponds to a Directory entry attribute.
- Finally, a database row, more appropriately known as a tuple, corresponds to one instance of a Directory entry.
A further refinement of relational databases concerns the concept of a database views. Although there is a large body of work published on this particular subject, one such work "Distributed Databases Principals &
Systems", by Stefano Ceri and Giuseppe Pelagatti, McGraw-Hill, 1984, pp.
330-332, gives the following classic definition of database views as provided through the industry standard SQL language.
"In SQUDS, views are defined as the result of an SQL select statement, producing a result relation from one or more operand relations.
The result relation gives to the user a new "view" of the database (or external schema in the ANSI-SPARC terminology), which is built through the standard query language."
To paraphrase Ceri and Pelagatti, a view can be likened to a new table formed from a selected subset of other tables. A similar concept can be achieved with the OSI Directory. By using existing OSI Directory query operations in a fashion which corresponds to an SQL select, one can create a new set of related entries from an existing set(s). This new set of selected entries corresponds to a relational database view.
Objects of the Invention Accordingly, it is an object of the invention to remove the burden of rather lengthy global Directory queries from the end directory service consumer.
WO 93/12499 ~ ~. ~ PCT/US92/04151_ It is also the object of this invention to present the cached results, in a form which corresponds to selected relational database views.
Summary of the Invention An Open Office Product Architecture of an Open System includes a global database which stores information in the form of entries for an entire organization. The organization may be organized in divisions. Each division may be organized in operations. Each operation may include a number of organizations. An entry for an organization may include an object class, in this case, people. Therefore the entry could include an employee name and number, an employee job title, an E-mail address, an organization identification and a time stamp. The time stamp includes the date and time the entry was made or last modified.
The entries which apply to a particular division or operation are stored locally. The information in each local entry may be a selected subset of the entry stored in the global database, but it will include the time stamp read from the global database the last time the global database was queried for that entry.
Each entry (view) is configured by the Systems Administrator and is called upon periodically, typically once an hour, to check if there are any changes to the global database that have an impact on, and require an update to the local views.
Scheduling information controls when the application that builds and updates the views comes up and runs.
The update process is controlled by storing a pair of time stamp values, or time frame, which define a window in time from which completed update transactions are to be extracted, and thereafter periodically checking the global database for further changes which have occurred during subsequent and later windows in time. Thus only the changed entries are retrieved and updated in the views.
Also provided are the selection criteria and predicates for reading selected attributes from an entry or a number of entries stored in the global database.
The invention may be summarized, according to a first aspect, as a method of formulating a search for changed entries in a global database and updating local views including the steps of at selected time frame intervals, A. building a list of all installed local view names;
B. developing a list of desired attributes for display in each local view identified in the list of installed local view names, the attributes for each local view including a latest time stamp value for the local view wherein each latest time stamp value indicates the time of a last change to the local view and definitions of the local view; C. selecting a local view name from the list of installed local view names;
D. reading from the attribute list for the selected local view name the view definitions and the latest time stamp value for the selected local view name; E. searching the global database using said view definitions to locate an entry corresponding to the selected local view name; F. when the entry corresponding to the selected local view name is a non-leaf entry, selecting a next entry; G. when the entry corresponding to the selected local view name is a leaf entry, comparing the time stamp value of the entry with the latest time stamp value for the selected view name from the list of attributes corresponding to the selected local view name; H. updating the local view corresponding to the selected local view name when the time stamp value of the entry is different from the latest time stamp value for the selected view name; I. determining when all entries corresponding to the selected local view name are processed; J. selecting a next entry corresponding to the selected local view name when all entries corresponding to the selected local view name are not processed; K. selecting a next local view name when all entries corresponding to the selected local view name are processed; and L. repeating steps C through K until all local view names in the list of all installed local view names are processed.
According to a second aspect, the present invention provides an Open Office Directory System for building and updating views stored in a local subdirectory comprises:
global database means for storing a global distributed directory; a builder means for controlling when an application that builds and updates said views is to be executed; a view management means for periodically scanning the global database for the views stored in the local subdirectory for changes in the views stored in the local subdirectory and for storing a latest time stamp value in attributes associated with each view in the local subdirectory wherein each latest time stamp value represents a time at which the associated view stored in the local subdirectory was last changed; an update means coupled to said builder means for working cooperatively with the view management means to determine a change in said global database for a view stored in the local subdirectory in a current update scan by storing a time frame of a last update scan in said update means wherein the view management means is responsive to the stored time frame of the last update scan for comparing the latest time stamp values of the views stored - 5a -in the global database for the views stored in the local subdirectory with the stored time frame of the last update scan and determining when a change in a view stored in the local subdirectory occurred subsequent to the last update scan; a definition means coupled to said update means and to global database means for providing selection criteria and predicates from the attributes associated with views stored in the local subdirectory for each view stored for which a change is determined in said current update scan to have occurred subsequent to the last update scan for reading the selected attributes from entries stored in said global database means for which a change has occurred subsequent to the last update scan; and an entry means coupled to said global database means for storing the local entries which are received from said global database means in the local subdirectory, thereby updating the views stored in the local subdirectory.
Brief Description of the Drawings Figure 1 shows a block diagram of an Open Office Product Architecture of an Open Systems.
Figure 2 shows a block diagram of the Directory Service.
Figure 3 presents a Functional Component design illustration of the View Builder Application.
Figure 4 is a block diagram showing the operation of the View Builder Application.
Figure 5 is a block diagram of the View Builder Scheduling Daemon.
Figures 6A, 6B, 6C and 6D show the iterations to - 5b -develop the local views.
Description of the preferred Embodiment Figure 1 shows a block diagram of an Open Office Product Architecture of an Open Systems offering of a UNIX
iteration of E-mail. An Open Office System 1 includes three service components, a Data Service 2, a Mail Service 4 and a Directory Service 6.
Data Service 2 retrieves work flow packages, calendar scheduling packages and mail data. Mail Service 4 is the local and remote mail handling service which is based on X.400. The Directory Service 6 is used by both the Data Service 2 and Mail Service 4 to do name and address mapping.
As an example, the Data Service 2 would query the Directory Service 6 for the name of an office data service and the name of an office service user. The Mail Service 4 would obtain mail addressing information including a list of possible names if the user was not sure of the correct spelling of the name.
Figure 2 shows a block diagram of the Directory Service 6 which includes a View Builder Scheduling Entry 12, Views Update Control Entries - 5c -~121~8~ _ 14, Views Definition Entries 16 and Views Alias Data Entries 18 which are all stored in a local subdirectory, and Distinguished Name Data Entries (Database) 20 which are part of the global distributed directory date base.
Database 20 is the global directory database, and although to the local directory user a virtual unified view is presented, the actual physical global allocation of the data is hidden and only known to the internal directory service components.
A view is a selected subset of an entry stored in Database 20. View Builder 12 contains scheduling information which controls when the application that builds and updates the views comes up and runs. This entry is configured by the Systems Administrator and is called upon periodically, typically once an hour, to check if there are any changes to Database 20 that have an impact on, and require an update to the local views. Every entry in the Database 20 includes the date and time the entry was rnade, or last modified, and is in the form of a time stamp.
Views Update 14 controls the update process by storing the time stamp of the last update scan, and thereafter periodically checks the Database 20 via View Builder 12 for changes which have occurred after the time of the last update scan. Thus only the changed entries are retrieved and updated in the views.
Views Definition 16 provides the selection criteria and predicates for reading selected attributes from an entry or a number of entries stored in Database 20. The attributes could include job description, phone number, organization, and the like.
Views Alias Data Entry 18 stores the local entries which are received from Database 20 and include the selected attributes.
Directory Server Process 10 is a commercially available X.500 server software program.
The View Builder Application 22, when run, reads the data structure of Views Definition 16 to determine how to formulate the operation to search for changed entries; and uses the control structures which it updates after it does the read to precisely specify the search operation in Database Vl~ 93/12499 ~~ ~ PCT/US92/04151 20 for time stamps later than the time stamps stored in Views Update 14.
View Builder 22 then updates the local database entries in Data Entries 18.
View Client Applications 26 and 28 are end user applications that use the entries in Data Entries 18 or Database 20. As an example, Application 26 could be a misspelled name finder, and Application 28 could correct misspelled addresses, or verify zip codes.
Other Directory Clients 30 may also be connected to Server 10.
Figure 3 presents a Functional Component design illustration of the View Builder application. The essence of this application is the View management Routine 22-2 which is described in further detail in Figure 4. In order for the View Management routine 22-2 to pertorm its task it relies on and uses the services of; A Unix Kernel calls 22-7 for memory management of Allocated Memory 22-1, an X.500 Directory API 22-9 for Directory query &
modify operations, a Directory Operation Formatting API 22-4, and a Directory Argument Formatting API 22-6.
The View Management Routine 22-2 functional component controls the order of processing when scanning the global directory for changed entries; similarly it controls the order of processing when the local views are updated to reflect these changes. It makes use of all the other functional components comprising the View Builder Application.
Directory Operation Formatting API 22-4 is called directly by the View Management Routine 22-2 formatting and executing a Directory operation on its behalf.
Directory Argument Formatting API 22-6 is called directly by Directory Operation Formatting API 22-4 in support of the Directory Operation Formatting process, this is the indirect result of the call made to Directory Operation Formatting API 22-4 by the View Management Routine 22-2.
Directory API 22-9 are ultimately called by Directory Operation Formatting API 22-4 on behalf of the View Management Routine 22-2.
These API's directly access the Directory Server.
Unix Kernel calls 22-7 is called directly and indirectly by View Management Routine 22-2, Directory Operation Formatting API 22-4, and WO 93/12499 ~ ~ 1 ;3 PGT/US92/04151,_ Directory Argument Formatting API 22-6 for standard operating system service functions.
The interaction of all these functional components comprises the View builder application.
Figure 4 is a block diagram showing the operation of the View Builder Application 22 of Figure 2 which reads the data structure of Views Definition 16 to determine how to formulate the operation to search for changed entries. View Builder 22 then uses the control structures which it updates after it does the read to precisely specify the search operation in Database 20 for time stamps later than the time stamps stored in Views Update 14.
View Builder 22 then updates the local database entries in Data Entries 18.
Block 22-8 starts the search and update operations.
Block 22-10 searches Views Definition 16 for the names of all installed Views. Then block 22-12 builds a List in memory 22-1 of all the installed view names and sets a pointer to the first entry in the List.
Block 22-14 reads a listed by view name in Views Definition 16 of Figure 2 for the selected attributes, the predicate, whether a time stamp is present and the name of a parent entry in Database 20. The parent entry name establishes a downward starting point for querying into the data tree in Database 20 for all subordinate children entries.
Block 22-16 reads Views control 14 for the latest time stamp value for the entry.
Block 22-18 searches Database 20 for the entries defined by the search in blocks 22-14 and Directory Argument Formatting API 22-16.
Decision block 22-20 determines if the entry satisfying the criteria and returned by block 22-18 is to be updated to Views Control 14, if so then Block 22-24 updates the entry in Views Control 14. Then decision block 22-26 may call block 22-18 to start the search for the next entry, or call block 22-28 to check for more View Names in the List. The entries are either leaf entries or non-leaf entries. If decision block 22-20 determined the entry returned by 22-18 was not a non-leaf then a leaf was found. Found leaf entries satisfying all of the criteria and are added or updated in Views Data WQ 93/12499 '~ ~ ,~ ~ ~.,~ ~ PCT/US92/04151 Entry 18 in block 22-22.
Then decision block 22-26 may repeat the loop to block 22-18 until all of the leaf entries are stored in Views Data Entry 18, then Block 22-28 is invoked to determine if all View Names in the list have been processed. If more names are in the View Name List the list pointer is moved to the next entry by block 22-30, if not the process ends at 22-32.
Referring to Figure 5, View Builder Scheduling Daemon 24, when requested by the Unix kernel time scheduling service (Chron} 24-2, runs on the UNIX system and does a Database 20 read of View Builder Scheduling Entry 12, in block 24-4. Decision block 24-6, using the information it retrieved from View Builder 12, compares the elapsed time since last running and, if appropriate, either schedules (fork) 24-10 the View Builder Application 22, or suspends it at block 24-8. If and when the View Builder Application 22 runs and completes its task, control is returned back in line at block 24-8 at which point the View Builder Scheduling Daemon 24 sleeps.
Figures 6A, 6B, 6C and 6D show, in a typical example, the iterations of Figure 4 to develop the local views. Figure 6A shows the attributes in the local views and the information in the Database 20 immediately after installation.
The Database 20 stores a number of trees including a tree headed by a US tree 51 which includes a Company entry 53 which has, as an example, a time stamp 2. Tree 51 includes a non-leaf Research & Development (R &
D) entry 55 with a time stamp 2, and a non-leaf Marketing (Mkt) entry 57 with a time stamp 3. Under R & D 55 are two leaf entries, Art L 59 with a time stamp 003 and Geo G 61 with a time stamp 004. Under Mkt 63 is a leaf entry for Joe S with a time stamp 002.
A number of attributes are shown for each entry. A local tree 50 is subordinate to US entry 51 and is accessed through server 10 at Local Service Name 56. Then under control of View Management routine 22-2, Directory Formatting Operation 22-4 and the Directory Argument Formatting API 22-6 of Figure 3, Block 22-10, Figure 4, searches Views Definition 16 for all installed view names. Block 22-12 builds a list of all installed view names in memory 22-1. Block 22-14 retrieves for a names view; the starting point of where to search, - i.e. Base Name = US/COMPANY;
the definition of the selected attributes, - i.e. name, job title, E-mail number and organization; the predicate, - i.e. object class=people and time frame=present as shown in block 58.
Block 22-16 searches for any view update control entries, if this is the first pass through none will be found as creation of this type of entry is the result of the later operation performed by block 22-24.
If this is not the first pass then Views Control entry 14 is returned from block 60, identified as time 1 (TS 1 ) which describes the tree 51 and Company 53 identifiers in Database 20, and a highest time stamp 0.
Figure 6B shows local tree 50 after pass 1. There is not change in block 58 of Views Befinition 16, however under control of block 22-18 of Figure 4, Views Control 14 searches Database 20 for US/COMPANY
and finds tree 51. Decision Block 22-20 finds that the first entry TS 1 is a non-leaf entry and block 22-24 updates Views Control 14 by TS 1 block 62 with a highest time stamp 3. Decision block 22-16 determines that not all entries were processed and branches to block 22-18. The loop, blocks 22-18, 22-20, 22-24 and 22-26 are repeated to store TS2 R&D block 64 with a highest times stamp ;0 and TS3 Mkt block 66 with a highest time stamp 0 in Views Control 14.
Figure 6C shows local tree 50 after pass 2. There is no change in block 58 of Views Definition 16. Views Control 14 now includes TS 1 block 62 with the same time stamp 3, TS2 R&D block 64 with a highest time stamp 4 and TS3 Mkt block 66 with a highest time stamp 2. The time stamps- are updated from blocks 59, 61 and 63 respectively and were received via blocks 22-18, 22020, 22-24 and 22-26 as above.
Decision block 22-20 determines that the next entry is a leaf entry and branches to block 22-22 which adds the first leaf entry 68 to Views Data 18. The loop of blocks 22-22, 22-26, 22-18 and 22-20 are repeated to add leaf entries 70 and 72 to Views Data 18. Dote that Blocks 68, 70 and 72 of Views Data 18 each include the selected data and its tree path in Database ~J~i~J
W,Q 93/12499 ~ 8 ~ PCT/US92/04151 20.
Decision block 22-28 tests if the View List Pointer is set to the end of the list and if not, calls block 22-30 to advance the pointer to the next View Name. Otherwise the operation ends at block 22-32 as is the case in this example and Block 6D shows the result at the end of this final pass.
While the invention has been shown and described with reference to the preferred embodiment thereof, it will be understood by those skilled in the art that the above and other changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (2)
PROPERTY OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A method of formulating a search for changed entries in a global database and updating local views including the steps of at selected time frame intervals, A. building a list of all installed local view names;
B. developing a list of desired attributes for display in each local view identified in the list of installed local view names, the attributes for each local view including a latest time stamp value for the local view wherein each latest time stamp value indicates the time of a last change to the local view and definitions of the local view;
C. selecting a local view name from the list of installed local view names;
D. reading from the attribute list for the selected local view name the view definitions and the latest time stamp value for the selected local view name;
E. searching the global database using said view definitions to locate an entry corresponding to the selected local view name;
F. when the entry corresponding to the selected local view name is a non-leaf entry, selecting a next entry;
G. when the entry corresponding to the selected local view name is a leaf entry, comparing the time stamp value of the entry with the latest time stamp value for the selected view name from the list of attributes corresponding to the selected local view name;
H. updating the local view corresponding to the selected local view name when the time stamp value of the entry is different from the latest time stamp value for the selected view name;
I. determining when all entries corresponding to the selected local view name are processed;
J. selecting a next entry corresponding to the selected local view name when all entries corresponding to the selected local view name are not processed;
K. selecting a next local view name when all entries corresponding to the selected local view name are processed;
and L. repeating steps C through K until all local view names in the list of all installed local view names are processed.
B. developing a list of desired attributes for display in each local view identified in the list of installed local view names, the attributes for each local view including a latest time stamp value for the local view wherein each latest time stamp value indicates the time of a last change to the local view and definitions of the local view;
C. selecting a local view name from the list of installed local view names;
D. reading from the attribute list for the selected local view name the view definitions and the latest time stamp value for the selected local view name;
E. searching the global database using said view definitions to locate an entry corresponding to the selected local view name;
F. when the entry corresponding to the selected local view name is a non-leaf entry, selecting a next entry;
G. when the entry corresponding to the selected local view name is a leaf entry, comparing the time stamp value of the entry with the latest time stamp value for the selected view name from the list of attributes corresponding to the selected local view name;
H. updating the local view corresponding to the selected local view name when the time stamp value of the entry is different from the latest time stamp value for the selected view name;
I. determining when all entries corresponding to the selected local view name are processed;
J. selecting a next entry corresponding to the selected local view name when all entries corresponding to the selected local view name are not processed;
K. selecting a next local view name when all entries corresponding to the selected local view name are processed;
and L. repeating steps C through K until all local view names in the list of all installed local view names are processed.
2. An Open Office Directory System for building and updating views stored in a local subdirectory comprises:
global database means for storing a global distributed directory;
a builder means for controlling when an application that builds and updates said views is to be executed;
a view management means for periodically scanning the global database for the views stored in the local subdirectory for changes in the views stored in the local subdirectory and for storing a latest time stamp value in attributes associated with each view in the local subdirectory wherein each latest time stamp value represents a time at which the associated view stored in the local subdirectory was last changed;
an update means coupled to said builder means for working cooperatively with the view management means to determine a change in said global database for a view stored in the local subdirectory in a current update scan by storing a time frame of a last update scan in said update means wherein the view management means is responsive to the stored time frame of the last update scan for comparing the latest time stamp values of the views stored in the global database for the views stored in the local subdirectory with the stored time frame of the last update scan and determining when a change in a view stored in the local subdirectory occurred subsequent to the last update scan;
a definition means coupled to said update means and to global database means for providing selection criteria and predicates from the attributes associated with views stored in the local subdirectory for each view stored for which a change is determined in said current update scan to have occurred subsequent to the last update scan for reading the selected attributes from entries stored in said global database means for which a change has occurred subsequent to the last update scan; and an entry means coupled to said global database means for storing the local entries which are received from said global database means in the local subdirectory, thereby updating the views stored in the local subdirectory.
global database means for storing a global distributed directory;
a builder means for controlling when an application that builds and updates said views is to be executed;
a view management means for periodically scanning the global database for the views stored in the local subdirectory for changes in the views stored in the local subdirectory and for storing a latest time stamp value in attributes associated with each view in the local subdirectory wherein each latest time stamp value represents a time at which the associated view stored in the local subdirectory was last changed;
an update means coupled to said builder means for working cooperatively with the view management means to determine a change in said global database for a view stored in the local subdirectory in a current update scan by storing a time frame of a last update scan in said update means wherein the view management means is responsive to the stored time frame of the last update scan for comparing the latest time stamp values of the views stored in the global database for the views stored in the local subdirectory with the stored time frame of the last update scan and determining when a change in a view stored in the local subdirectory occurred subsequent to the last update scan;
a definition means coupled to said update means and to global database means for providing selection criteria and predicates from the attributes associated with views stored in the local subdirectory for each view stored for which a change is determined in said current update scan to have occurred subsequent to the last update scan for reading the selected attributes from entries stored in said global database means for which a change has occurred subsequent to the last update scan; and an entry means coupled to said global database means for storing the local entries which are received from said global database means in the local subdirectory, thereby updating the views stored in the local subdirectory.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US810,245 | 1991-12-19 | ||
| US07/810,245 US5388255A (en) | 1991-12-19 | 1991-12-19 | System for updating local views from a global database using time stamps to determine when a change has occurred |
| PCT/US1992/004151 WO1993012499A1 (en) | 1991-12-19 | 1992-05-18 | Open office directory database views |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2121483A1 CA2121483A1 (en) | 1993-06-24 |
| CA2121483C true CA2121483C (en) | 2002-06-11 |
Family
ID=25203380
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002121483A Expired - Fee Related CA2121483C (en) | 1991-12-19 | 1992-05-18 | Open office directory database views |
Country Status (7)
| Country | Link |
|---|---|
| US (1) | US5388255A (en) |
| EP (1) | EP0617814B1 (en) |
| JP (1) | JPH07506443A (en) |
| AU (1) | AU668093B2 (en) |
| CA (1) | CA2121483C (en) |
| DE (1) | DE69229056T2 (en) |
| WO (1) | WO1993012499A1 (en) |
Families Citing this family (100)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5666526A (en) * | 1993-09-02 | 1997-09-09 | Microsoft Corp. | Method and system for supporting scrollable, updatable database queries |
| US5555407A (en) * | 1993-02-17 | 1996-09-10 | Home Information Services, Inc. | Method of and apparatus for reduction of bandwidth requirements in the provision of electronic information and transaction services through communication networks |
| JPH06324928A (en) * | 1993-05-14 | 1994-11-25 | Mitsubishi Electric Corp | Log generating device, device for arbitrating versions different in file and device for arbitrating version different in computer file being at different places |
| US5544353A (en) * | 1993-06-14 | 1996-08-06 | International Business Machines Corporation | Distributed processing object shared resource control apparatus and method |
| US5630116A (en) * | 1993-08-11 | 1997-05-13 | Nec Corporation | Automatic delivery system for master files in a distributed processing system |
| US6289390B1 (en) | 1993-08-18 | 2001-09-11 | Microsoft Corporation | System and method for performing remote requests with an on-line service network |
| US5606705A (en) * | 1994-04-15 | 1997-02-25 | Honeywell Inc. | Communication coordinator for messages to be sent from at least one data source to a plurality of clients |
| US7315860B1 (en) * | 1994-09-01 | 2008-01-01 | Computer Associates Think, Inc. | Directory service system and method with tolerance for data entry storage and output |
| EP0777883B1 (en) * | 1994-09-01 | 2003-05-02 | Computer Associates Think, Inc. | X.500 system and methods |
| JP3302522B2 (en) | 1994-12-26 | 2002-07-15 | 富士通株式会社 | Database system and its information utilization support device |
| US6240451B1 (en) * | 1995-05-25 | 2001-05-29 | Punch Networks Corporation | Method and apparatus for automatically disseminating information over a network |
| US5694596A (en) | 1995-05-25 | 1997-12-02 | Kangaroo, Inc. | On-line database updating network system and method |
| US5774668A (en) * | 1995-06-07 | 1998-06-30 | Microsoft Corporation | System for on-line service in which gateway computer uses service map which includes loading condition of servers broadcasted by application servers for load balancing |
| US6901433B2 (en) | 1995-06-07 | 2005-05-31 | Microsoft Corporation | System for providing users with a filtered view of interactive network directory obtains from remote properties cache that provided by an on-line service |
| US5956489A (en) * | 1995-06-07 | 1999-09-21 | Microsoft Corporation | Transaction replication system and method for supporting replicated transaction-based services |
| US5933599A (en) * | 1995-07-17 | 1999-08-03 | Microsoft Corporation | Apparatus for presenting the content of an interactive on-line network |
| US5941947A (en) * | 1995-08-18 | 1999-08-24 | Microsoft Corporation | System and method for controlling access to data entities in a computer network |
| US5956509A (en) | 1995-08-18 | 1999-09-21 | Microsoft Corporation | System and method for performing remote requests with an on-line service network |
| US8065338B2 (en) * | 1995-08-30 | 2011-11-22 | Computer Associates Think, Inc. | Directory searching methods and systems |
| US6134551A (en) * | 1995-09-15 | 2000-10-17 | Intel Corporation | Method of caching digital certificate revocation lists |
| JPH09218815A (en) * | 1996-01-31 | 1997-08-19 | Toshiba Corp | Information equipment provided with network communication function and information access method in the same |
| US6151643A (en) * | 1996-06-07 | 2000-11-21 | Networks Associates, Inc. | Automatic updating of diverse software products on multiple client computer systems by downloading scanning application to client computer and generating software list on client computer |
| US5864837A (en) * | 1996-06-12 | 1999-01-26 | Unisys Corporation | Methods and apparatus for efficient caching in a distributed environment |
| US5832514A (en) * | 1996-06-26 | 1998-11-03 | Microsoft Corporation | System and method for discovery based data recovery in a store and forward replication process |
| US6412017B1 (en) * | 1996-07-01 | 2002-06-25 | Microsoft Corporation | Urgent replication facility |
| US5905978A (en) * | 1996-07-15 | 1999-05-18 | Unisys Corporation | Window size determination using fuzzy logic |
| US5919247A (en) * | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
| US6195096B1 (en) | 1996-08-14 | 2001-02-27 | International Business Machines Corporation | Graphical interface method, apparatus and application for creating and modifying a multiple-value text list |
| US5818444A (en) * | 1996-08-14 | 1998-10-06 | International Business Machines Corporation | Method, apparatus and application for object selective but global attribute modification |
| US5784057A (en) * | 1996-08-14 | 1998-07-21 | International Business Machines Corporation | Dynamically modifying a graphical user interface window title |
| US5781193A (en) * | 1996-08-14 | 1998-07-14 | International Business Machines Corporation | Graphical interface method, apparatus and application for creating multiple value list from superset list |
| US5774119A (en) * | 1996-08-14 | 1998-06-30 | International Business Machines Corporation | Graphical interface method, apparatus and application for selection of target object |
| US5774120A (en) * | 1996-08-14 | 1998-06-30 | International Business Machines Corporation | Refresh and select-all actions in graphical user interface |
| US6104395A (en) * | 1996-08-14 | 2000-08-15 | International Business Machines Corporation | Graphical interface method, apparatus and application for opening window of all designated container objects |
| US5872568A (en) * | 1996-08-14 | 1999-02-16 | International Business Machines Corporation | Application and method for creating a list from pre-defined and user values |
| US5867157A (en) * | 1996-08-14 | 1999-02-02 | International Business Machines Corporation | Graphical interface method, apparatus and application for creating and modifying a list of values with multiple components |
| US5970247A (en) * | 1996-10-07 | 1999-10-19 | Wolf; William M. | Methods for encoding decoding and processing six character date designations for the year 2000 and beyond |
| US6144962A (en) * | 1996-10-15 | 2000-11-07 | Mercury Interactive Corporation | Visualization of web sites and hierarchical data structures |
| US5870559A (en) * | 1996-10-15 | 1999-02-09 | Mercury Interactive | Software system and associated methods for facilitating the analysis and management of web sites |
| US5974572A (en) * | 1996-10-15 | 1999-10-26 | Mercury Interactive Corporation | Software system and methods for generating a load test using a server access log |
| US5958008A (en) * | 1996-10-15 | 1999-09-28 | Mercury Interactive Corporation | Software system and associated methods for scanning and mapping dynamically-generated web documents |
| US6049809A (en) * | 1996-10-30 | 2000-04-11 | Microsoft Corporation | Replication optimization system and method |
| US6049812A (en) * | 1996-11-18 | 2000-04-11 | International Business Machines Corp. | Browser and plural active URL manager for network computers |
| US6061740A (en) * | 1996-12-09 | 2000-05-09 | Novell, Inc. | Method and apparatus for heterogeneous network management |
| US6708221B1 (en) * | 1996-12-13 | 2004-03-16 | Visto Corporation | System and method for globally and securely accessing unified information in a computer network |
| US20060195595A1 (en) * | 2003-12-19 | 2006-08-31 | Mendez Daniel J | System and method for globally and securely accessing unified information in a computer network |
| US7287271B1 (en) | 1997-04-08 | 2007-10-23 | Visto Corporation | System and method for enabling secure access to services in a computer network |
| US5978842A (en) * | 1997-01-14 | 1999-11-02 | Netmind Technologies, Inc. | Distributed-client change-detection tool with change-detection augmented by multiple clients |
| US5898836A (en) * | 1997-01-14 | 1999-04-27 | Netmind Services, Inc. | Change-detection tool indicating degree and location of change of internet documents by comparison of cyclic-redundancy-check(CRC) signatures |
| JP3139408B2 (en) * | 1997-03-17 | 2001-02-26 | カシオ計算機株式会社 | Homepage update notification device |
| US5950198A (en) * | 1997-03-24 | 1999-09-07 | Novell, Inc. | Processes and apparatuses for generating file correspondency through replication and synchronization between target and source computers |
| US6766454B1 (en) | 1997-04-08 | 2004-07-20 | Visto Corporation | System and method for using an authentication applet to identify and authenticate a user in a computer network |
| US7631012B2 (en) | 1997-05-22 | 2009-12-08 | Computer Associates Think, Inc. | System and method of operating a database |
| AU8485498A (en) * | 1997-07-14 | 1999-02-08 | Infosquare Corporation | Static views of data bases |
| US6078952A (en) * | 1997-08-01 | 2000-06-20 | International Business Machines Corporation | Method and apparatus for maintaining directory services for a video transmission network |
| US6078873A (en) * | 1997-10-02 | 2000-06-20 | Cummins Engine Company, Inc. | Method and apparatus for real-time data stamping via datalink and volatile ECM timer/clock |
| US6195666B1 (en) | 1997-12-15 | 2001-02-27 | International Business Machines Corporation | Web interface and method for displaying directory information |
| US6192362B1 (en) * | 1997-12-15 | 2001-02-20 | International Business Machines Corporation | System and method for creating a search form for accessing directory information |
| US6208986B1 (en) | 1997-12-15 | 2001-03-27 | International Business Machines Corporation | Web interface and method for accessing and displaying directory information |
| US6260039B1 (en) * | 1997-12-15 | 2001-07-10 | International Business Machines Corporation | Web interface and method for accessing directory information |
| US6058391A (en) * | 1997-12-17 | 2000-05-02 | Mci Communications Corporation | Enhanced user view/update capability for managing data from relational tables |
| US6438585B2 (en) | 1998-05-29 | 2002-08-20 | Research In Motion Limited | System and method for redirecting message attachments between a host system and a mobile data communication device |
| US7209949B2 (en) | 1998-05-29 | 2007-04-24 | Research In Motion Limited | System and method for synchronizing information between a host system and a mobile data communication device |
| US7305451B2 (en) * | 1998-08-24 | 2007-12-04 | Microsoft Corporation | System for providing users an integrated directory service containing content nodes located in different groups of application servers in computer network |
| US6510462B2 (en) * | 1998-09-01 | 2003-01-21 | Nielsen Media Research, Inc. | Collection of images in Web use reporting system |
| US6366902B1 (en) * | 1998-09-24 | 2002-04-02 | International Business Machines Corp. | Using an epoch number to optimize access with rowid columns and direct row access |
| US6266774B1 (en) | 1998-12-08 | 2001-07-24 | Mcafee.Com Corporation | Method and system for securing, managing or optimizing a personal computer |
| US7373517B1 (en) | 1999-08-19 | 2008-05-13 | Visto Corporation | System and method for encrypting and decrypting files |
| US7171616B1 (en) | 1999-09-27 | 2007-01-30 | International Business Machines Corporation | Method, system and computer program product for keeping files current |
| AUPQ428499A0 (en) | 1999-11-26 | 1999-12-23 | Computer Associates Pty. Ltd. | A method and apparatus for operating a data base |
| US7720833B1 (en) * | 2000-02-02 | 2010-05-18 | Ebay Inc. | Method and system for automatically updating search results on an online auction site |
| US7739334B1 (en) | 2000-03-17 | 2010-06-15 | Visto Corporation | System and method for automatically forwarding email and email events via a computer network to a server computer |
| US6826750B1 (en) | 2000-03-23 | 2004-11-30 | International Business Machines Corporation | Method of automatically selecting program and data updates based upon versions |
| US7069292B2 (en) * | 2000-08-29 | 2006-06-27 | Fujitsu Limited | Automatic display method and apparatus for update information, and medium storing program for the method |
| US7225231B2 (en) * | 2000-09-20 | 2007-05-29 | Visto Corporation | System and method for transmitting workspace elements across a network |
| US20030074635A1 (en) * | 2001-10-11 | 2003-04-17 | International Business Machines Corporation | Method, apparatus, and program for finding and navigating to items in a set of web pages |
| GB0114904D0 (en) * | 2001-06-19 | 2001-08-08 | Hewlett Packard Co | Portable audio device and network including an audio device |
| US7191209B1 (en) | 2001-07-30 | 2007-03-13 | Bellsouth Intellectual Property Corp. | Application server and method to perform hierarchical configurable data manipulation |
| US7353248B1 (en) * | 2001-07-30 | 2008-04-01 | At&T Delaware Intellectual Property, Inc. | Application server and method to perform hierarchical configurable data validation |
| US7441007B1 (en) | 2001-07-30 | 2008-10-21 | At&T Intellectual Property I, L.P. | System and method for allowing applications to retrieve properties and configuration information from a persistent store |
| US6889333B2 (en) * | 2001-11-01 | 2005-05-03 | Microsoft Corporation | System and method for replicating data in a distributed system |
| CA2467404A1 (en) * | 2001-11-15 | 2003-05-30 | Visto Corporation | System and methods for asychronous synchronization |
| US7370044B2 (en) | 2001-11-19 | 2008-05-06 | Equifax, Inc. | System and method for managing and updating information relating to economic entities |
| US20040010522A1 (en) * | 2002-05-24 | 2004-01-15 | Shulok Thomas Aaron | Method and system for detecting significant changes in dynamic datasets |
| US8230026B2 (en) | 2002-06-26 | 2012-07-24 | Research In Motion Limited | System and method for pushing information between a host system and a mobile data communication device |
| US7174345B2 (en) * | 2003-05-30 | 2007-02-06 | Oracle International Corporation | Methods and systems for auto-partitioning of schema objects |
| US7493321B2 (en) | 2005-02-23 | 2009-02-17 | International Business Machines Corporation | Method, system, and computer program product for creating navigation views based on historical user behavior |
| US20080235255A1 (en) * | 2007-03-19 | 2008-09-25 | Redknee Inc. | Extensible Data Repository |
| US9483755B2 (en) * | 2008-03-04 | 2016-11-01 | Apple Inc. | Portable multifunction device, method, and graphical user interface for an email client |
| US20100262625A1 (en) * | 2009-04-08 | 2010-10-14 | Glenn Robert Pittenger | Method and system for fine-granularity access control for database entities |
| US20120254134A1 (en) * | 2011-03-30 | 2012-10-04 | Google Inc. | Using An Update Feed To Capture and Store Documents for Litigation Hold and Legal Discovery |
| US9881017B2 (en) | 2012-08-03 | 2018-01-30 | Egnyte, Inc. | System and method for event-based synchronization of remote and local file systems |
| US10380076B2 (en) | 2014-07-21 | 2019-08-13 | Egnyte, Inc. | System and method for policy based synchronization of remote and local file systems |
| WO2016036509A1 (en) | 2014-09-02 | 2016-03-10 | Apple Inc. | Electronic mail user interface |
| US10437789B2 (en) | 2015-04-10 | 2019-10-08 | Egnyte, Inc. | System and method for delete fencing during synchronization of remote and local file systems |
| US11144510B2 (en) | 2015-06-11 | 2021-10-12 | Egnyte, Inc. | System and method for synchronizing file systems with large namespaces |
| AU2016340043A1 (en) * | 2015-10-15 | 2018-05-24 | Big Ip Pty Ltd | A system, method, computer program and data signal for conducting an electronic search of a database |
| WO2017063048A1 (en) * | 2015-10-15 | 2017-04-20 | Big Ip Pty Ltd | A system, method, computer program and data signal for the provision of a database of information for lead generating purposes |
| US10810228B2 (en) * | 2015-11-02 | 2020-10-20 | Servicenow, Inc. | Universal automatic data update detection and publication |
| US20170177613A1 (en) | 2015-12-22 | 2017-06-22 | Egnyte, Inc. | Event-Based User State Synchronization in a Cloud Storage System |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB1521600A (en) * | 1975-12-31 | 1978-08-16 | Ibm | Digital data processing apparatus |
| US4769772A (en) * | 1985-02-28 | 1988-09-06 | Honeywell Bull, Inc. | Automated query optimization method using both global and parallel local optimizations for materialization access planning for distributed databases |
| JPS61204733A (en) * | 1985-03-07 | 1986-09-10 | Oki Electric Ind Co Ltd | Visual field managing system |
| US4897781A (en) * | 1987-02-13 | 1990-01-30 | International Business Machines Corporation | System and method for using cached data at a local node after re-opening a file at a remote node in a distributed networking environment |
| US4855906A (en) * | 1987-10-23 | 1989-08-08 | Allen-Bradley Company, Inc. | System for handling unsolicited messages from lower-tier controllers |
| EP0320266A3 (en) * | 1987-12-11 | 1992-03-11 | Hewlett-Packard Company | View composition in a data base management system |
| US5113519A (en) * | 1989-05-15 | 1992-05-12 | International Business Machines Corporation | Maintenance of file attributes in a distributed data processing system |
| US5181162A (en) * | 1989-12-06 | 1993-01-19 | Eastman Kodak Company | Document management and production system |
| US5226117A (en) * | 1990-05-15 | 1993-07-06 | International Business Machines Corporation | Method for simultaneous update and change in parent and child windows |
-
1991
- 1991-12-19 US US07/810,245 patent/US5388255A/en not_active Expired - Lifetime
-
1992
- 1992-05-18 AU AU19985/92A patent/AU668093B2/en not_active Ceased
- 1992-05-18 WO PCT/US1992/004151 patent/WO1993012499A1/en active IP Right Grant
- 1992-05-18 JP JP5510860A patent/JPH07506443A/en active Pending
- 1992-05-18 EP EP92912477A patent/EP0617814B1/en not_active Expired - Lifetime
- 1992-05-18 CA CA002121483A patent/CA2121483C/en not_active Expired - Fee Related
- 1992-05-18 DE DE69229056T patent/DE69229056T2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| EP0617814B1 (en) | 1999-04-28 |
| DE69229056D1 (en) | 1999-06-02 |
| US5388255A (en) | 1995-02-07 |
| JPH07506443A (en) | 1995-07-13 |
| WO1993012499A1 (en) | 1993-06-24 |
| EP0617814A1 (en) | 1994-10-05 |
| AU1998592A (en) | 1993-07-19 |
| AU668093B2 (en) | 1996-04-26 |
| DE69229056T2 (en) | 1999-12-09 |
| CA2121483A1 (en) | 1993-06-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2121483C (en) | Open office directory database views | |
| US7089228B2 (en) | Computer apparatus and method for caching results of a database query | |
| EP1610235B1 (en) | A data processing system and method | |
| US8738592B2 (en) | Managing data transaction requests | |
| US7047242B1 (en) | Weighted term ranking for on-line query tool | |
| US8301590B2 (en) | Custom caching | |
| US6826559B1 (en) | Hybrid category mapping for on-line query tool | |
| US6564218B1 (en) | Method of checking the validity of a set of digital information, and a method and an apparatus for retrieving digital information from an information source | |
| US7725447B2 (en) | Method, apparatus, and system for searching based on search visibility rules | |
| US20050234890A1 (en) | Generation of database queries from database independent selection conditions | |
| US20070294050A1 (en) | Apparatus and method for monitoring usage of components in a database index | |
| US20060224603A1 (en) | System and methods for facilitating a linear grid database with data organization by dimension | |
| US6651070B1 (en) | Client/server database system | |
| US10599692B2 (en) | Modification of a saved database query based on a change in the meaning of a query value over time | |
| US20050216451A1 (en) | Generation of database queries from predefined query strings | |
| US20090204566A1 (en) | Processing of Deterministic User-Defined Functions Using Multiple Corresponding Hash Tables | |
| US8275661B1 (en) | Targeted banner advertisements | |
| US20080215539A1 (en) | Data ordering for derived columns in a database system | |
| US20080109423A1 (en) | Apparatus and method for database partition elimination for sampling queries | |
| US20040193568A1 (en) | Abstract data model filters | |
| US7925642B2 (en) | Apparatus and method for reducing size of intermediate results by analyzing having clause information during SQL processing | |
| US7779057B2 (en) | Method and apparatus for retrieving and sorting entries from a directory | |
| EP1566745A1 (en) | Generation of database queries from database independent selection conditions | |
| EP1566746A1 (en) | Generation of database queries from predefined query strings | |
| Goldstein et al. | Database management with sequence trees and tokens |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |