US20070005610A1 - Method and system for processing directory events - Google Patents
Method and system for processing directory events Download PDFInfo
- Publication number
- US20070005610A1 US20070005610A1 US11/470,443 US47044306A US2007005610A1 US 20070005610 A1 US20070005610 A1 US 20070005610A1 US 47044306 A US47044306 A US 47044306A US 2007005610 A1 US2007005610 A1 US 2007005610A1
- Authority
- US
- United States
- Prior art keywords
- event
- directory
- master
- client
- server
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- 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
-
- 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/99955—Archiving or backup
Definitions
- the present invention generally relates to the management of directory events, and more particularly relates to the synchronization and ordering of directory events in a highly distributed directory environment.
- a directory service provider server which controls any manipulation of data stored within a master directory database as requested by a directory client. For each data manipulation, the directory service provider server transmits an event notification describing the data manipulation to all directory clients.
- the performance of the directory service provider server in manipulating data stored within the master directory database in accordance with numerous received requests from one or more directory clients can be impeded as the directory service provider server concurrently attempts to transmit corresponding event notifications to all of the directory clients. This is particularly true when the directory service provider server is also receiving new data manipulation requests from directory clients.
- transmission of an event notification by the directory service provider server to a directory client can arrive to the directory client a significant amount of time before the manipulated data has been replicated by the master directory database in all replicate directory databases.
- a directory client may therefore futilely attempt to access a corresponding replicate directory database for the manipulated data prior to the master directory database's replication of the manipulated data into that particular replicate directory database.
- a directory service provider server is operated to perform a data manipulation within a master directory database.
- An event master server is operated to assign a sequence number to the data manipulation, and to store the sequence number within the master directory database.
- a second form of the present invention is a directory event system comprising a master directory database, a directory service provider server, and a event master server.
- the master directory database is operable to store data.
- the directory service provider server is operable to manipulate the data.
- the event master server is operable to assign a sequence number to any manipulation of the data within the master directory database by the directory service provider server.
- a third form of the present invention is a computer program product in a computer useable medium.
- the computer program product comprises a means for monitoring a first queue for a modified message; a means for assigning a first sequence number to said modified message when said modified message is within said first queue; a means for storing said first sequence number within a master directory database; and a means for providing an event message including said first sequence number and an event notification.
- FIG. 1A is schematic diagram of network of distributed data processing systems in accordance with the present invention.
- FIG. 1B is a schematic diagram of a computer architecture of a data processing system as known in the art
- FIG. 2 is a block diagram of an architecture of a directory event system in accordance with the present invention.
- FIG. 3A is flowchart of one embodiment of an event message routine in accordance with the present invention.
- FIG. 3B is flowchart of one embodiment of an event notification routine in accordance with the present invention.
- FIG. 1A depicts a network of data processing systems.
- Distributed data processing system 10 contains a network 20 , a network 21 , a network 22 , a network 23 , and a network 24 , which are the media used to provide communications links between various devices and computers connected together within distributed data processing system 10 .
- Network 20 , network 21 , network 22 , network 23 , and network 24 may include permanent connections, such as wire or fiber optic cables, or temporary connections made through telephone or wireless communications.
- a directory service provider server 30 an event master server 40 , an event service server 41 , and an event client server 44 are connected to network 20 along with a master directory database 31 .
- Event service server 41 , an event client 42 and an event client 43 are connected to network 21 along with a replicate directory database 32 .
- Event client 42 , a directory client 50 a, a directory client 50 b, and a directory client 50 c are connected to network 22 .
- Event client 43 , a directory client 50 d, a directory client 50 e, and a directory client 50 f are connected to network 23 .
- Event client server 44 , a directory client 50 g, a directory client 50 h, and a directory client 50 i are connected to network 24 .
- Directory clients 50 a - 50 f are in electrical communication with replicate directory database 32
- directory clients 50 g - 50 i are in electrical communication with master directory database 31 .
- Servers 30 and 40 - 43 , and clients 50 a - 50 i may be represented by a variety of computing devices, such as mainframes, personal computers, personal digital assistants (PDAs), etc.
- Distributed data processing system 10 may includes additional servers, clients, networks, routers, and other devices not shown.
- Distributed data processing system 10 may include the Internet with network 20 , network 21 , network 22 , network 23 and network 24 representing a worldwide collection of networks and gateways that use the TCP/IP suite of protocols to communicate with one another.
- distributed data processing system 10 may also include a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN).
- LAN local area network
- WAN wide area network
- FIG. 1A is intended as an example of a heterogeneous computing environment and not as an architectural limitation for the present invention.
- Data processing system 60 contains one or more central processing units (CPUs) 62 connected to internal system bus 61 , which interconnects random access memory (RAM 63 , read-only memory (ROM) 64 , and input/output adapter 65 , which supports various I/O devices, such as printer 70 , disk units 71 , or other devices not shown, such as a sound system, etc.
- CPUs central processing units
- RAM 63 random access memory
- ROM read-only memory
- input/output adapter 65 which supports various I/O devices, such as printer 70 , disk units 71 , or other devices not shown, such as a sound system, etc.
- a communication adapter 66 , a user interface adapter 67 , and a display adapter 68 are also connected to bus 61 .
- Communication adapter 66 provides bus 61 with access to a communication link 72 .
- User interface adapter 67 connects bus 61 to various user devices, such as keyboard 73 and mouse 74 , or other device not shown, such as a touch screen, stylus, etc.
- Display adapter 68 connects bus 61 to a display device 75 .
- FIG. 1B may vary depending on the system implementation.
- the system may have one or more processors, and other peripheral devices may be used in addition to or in place of the hardware depicted in FIG. 1B .
- the depicted example is not meant to imply architectural limitations with respect to the present invention.
- the present invention may be implemented in a variety of software environments.
- a typical operating system may be used to control program execution within the data processing system.
- directory service provider server 30 manipulates data within master directory database 31 as directed by a directory data manipulation request from one of directory clients 50 a - 50 i, and master directory database 30 thereafter replicates the manipulated data within master directory database 30 to replicate directory database 31 .
- a directory event system 11 in accordance with the present invention provides event notification(s) to one or more of directory clients 50 g - 50 i upon the manipulation of data in master directory database 31 by directory service provider server 10 , and provides the event notification(s) to one or more of directory clients 50 a - 50 f upon a replication of the manipulated data from master directory database 31 to replicate directory database 32 .
- Directory service provider server 30 is therefore not burdened with the task of providing the event notification(s) to directory clients 50 a - 50 i. As a result, directory service provider server 30 is consistently available to timely and effectively handle all directory data manipulation requests from directory clients 50 d - 50 i.
- Directory event system 11 will now be described herein as implemented within event master server 40 , event service server 41 , and event client server 42 .
- event master server 40 event service server 41
- event client server 42 event client server 42
- Directory event system 11 comprises an event message provider 40 a and a queue 40 b within event master server 40 .
- Directory service provider server 30 operatively shares queue 40 b with event message provider 40 a.
- Queue 40 b serves as the only link between directory event system 11 and directory service provider server 30 to thereby enable directory event system 11 and directory service provider server 30 to operate independent of each other.
- Event message provider 40 a implements an event message routine 80 in accordance with the present invention as shown in FIG. 3A .
- event message provider 40 a monitors queue 40 b to determine if directory service provider server 30 has sent a modification message MM N to queue 40 b.
- Modification message MM N is the description of a directory data manipulation request received by directory service provider server 30 and the corresponding manipulated data within master directory database 31 .
- event message provider 40 a proceeds to stage S 84 of routine 80 to assign a sequence number SN N to modification message MM N and to write sequence number SN N to master directory database 31 .
- master directory database 31 replicates all data to replicate directory database 32 to thereby store the manipulated data and sequence number SN N within replicate directory database 32 .
- Sequence number SN N serves as a marker indicating the corresponding manipulated data from master directory database 31 is stored within replicate directory database 32 .
- Event message provider 40 a proceeds to stage S 86 to provide an event message EM N to event service server 41 .
- Event message EM N includes an event notification EN N that is modification message MM N or an edited version thereof.
- Event message EM N further includes sequence number SN N .
- Event message provider 40 a then returns to stage S 82 to await modification message MM N+1 .
- directory event system 11 further comprises a replicate data monitor 41 a and a queue 41 b within event service server 41 .
- replicate data monitor 41 a implements an event notification routine 90 in accordance with the present invention as shown in FIG. 3B .
- replicate data monitor 41 a stores sequence number SN N within queue 41 b.
- Replicate data monitor 41 a proceeds to stage S 94 of routine 90 to poll replicate directory database 32 for a sequence number SN MAX stored therein.
- Those of ordinary skill in the art will appreciate there can be a significant gap of time from a completion of the writing of sequence number SN N to master directory database 31 by event message provider 40 a and a subsequent completion of the replication of all of the data within master directory database 31 , including the manipulated data and sequence number SN N , to replicate directory database 32 .
- sequence number SN N being greater than sequence number SN MAX is an indication that the replication of all of the data within master directory database 31 , including the manipulated data and sequence number SN N , has not occurred.
- sequence number SN N being less than or equal to sequence number SN MAX is an indication that the replication of all of the data within master directory database 31 , including the manipulated data and sequence number SN N has occurred.
- replicate data monitor 41 a compares sequence number SN N and sequence number SN MAX to determine if sequence number SN N is less than or equal to sequence number SN MAX . If sequence number SN N is greater than sequence number SN MAX , replicate data monitor 41 a loops back to stage S 94 . If sequence number SN N is less than or equal to sequence number SN MAX , replicate data monitor 41 a proceeds to stage S 98 to provide event notification EN N (or an edited version thereof) to event client server 42 and event client server 43 .
- directory event system 11 further comprises an event notifier 42 a and a directory client register 42 b within event client server 42 .
- Each directory client of directory clients 50 a - 50 c selectively registers for one or more event services via directory client register 42 b.
- Event notifier 42 a provides event notification EN N to each directory client 50 a - 50 c that registered for an event service corresponding to event notification EN N .
- the registered directory client(s) 50 a - 50 c can immediately poll replicate directory database 32 for the corresponding manipulated data.
- Directory event system 11 also comprises an event notifier analogous to event notifier 42 a and a directory client register analogous directory client register 42 b within event client server 43 and event client server 44 .
- Event client server 43 provides event notification EN N to the registered directory client(s) 50 d - 50 f in response to event notification EN N from event service server 41 .
- event notification EN N the registered directory client(s) 50 d - 50 f can immediately poll replicate directory database 32 for the corresponding manipulated data.
- Event client server 44 provides event notification EN N to the registered directory client(s) 50 g - 50 i in response to event notification EN N from event master server 40 .
- event notification EN N the registered directory client(s) 50 g - 50 i can immediately poll master directory database 31 for the corresponding manipulated data.
Abstract
A directory event system for providing timely event notifications of each data manipulation of a master directory database and for providing timely event notifications of each corresponding data replication to a replicate directory database is disclosed. The directory event system includes an event master server, one or more event service servers, and one or more event client servers. For an event client server having directory clients in electrical communication with the master directory database, the event master server provides an event notification to the event client server in response to a data manipulation of the master directory database by a directory service provider server. The master directory clients can immediately poll the master directory database for the manipulated data upon receipt of an event notification from the event client server. For an event client server having directory clients in electrical communication with the replicate directory database, the event master server provides an event message to an event service server in response to the data manipulation of the master directory database by the directory service provider server. The event message includes the event notification and the sequence number, and the event service server provides the event notification to the event client server upon a replication of the sequence number within the replicate directory database. The replicate directory clients can poll the replicate directory database for the manipulated data upon receipt of the event notification from the event client server.
Description
- 1. Field of the Invention
- The present invention generally relates to the management of directory events, and more particularly relates to the synchronization and ordering of directory events in a highly distributed directory environment.
- 2. Description of the Related Art
- A directory service provider server which controls any manipulation of data stored within a master directory database as requested by a directory client. For each data manipulation, the directory service provider server transmits an event notification describing the data manipulation to all directory clients. The performance of the directory service provider server in manipulating data stored within the master directory database in accordance with numerous received requests from one or more directory clients can be impeded as the directory service provider server concurrently attempts to transmit corresponding event notifications to all of the directory clients. This is particularly true when the directory service provider server is also receiving new data manipulation requests from directory clients.
- Also, in a highly distributed environment where numerous directory clients have registered to receive directory events, the processing overhead for event notification by the directory service provider server can become significant. This will not only affect the directory service provider server's processing of event notifications, but potentially other processes in the environment as well.
- Additionally, transmission of an event notification by the directory service provider server to a directory client can arrive to the directory client a significant amount of time before the manipulated data has been replicated by the master directory database in all replicate directory databases. A directory client may therefore futilely attempt to access a corresponding replicate directory database for the manipulated data prior to the master directory database's replication of the manipulated data into that particular replicate directory database.
- The computer industry is therefore continually striving to improve upon the processing of directory events in a distributed environment.
- One form of the present invention is a directory event method. A directory service provider server is operated to perform a data manipulation within a master directory database. An event master server is operated to assign a sequence number to the data manipulation, and to store the sequence number within the master directory database.
- A second form of the present invention is a directory event system comprising a master directory database, a directory service provider server, and a event master server. The master directory database is operable to store data. The directory service provider server is operable to manipulate the data. The event master server is operable to assign a sequence number to any manipulation of the data within the master directory database by the directory service provider server.
- A third form of the present invention is a computer program product in a computer useable medium. The computer program product comprises a means for monitoring a first queue for a modified message; a means for assigning a first sequence number to said modified message when said modified message is within said first queue; a means for storing said first sequence number within a master directory database; and a means for providing an event message including said first sequence number and an event notification.
- The foregoing forms and other forms, features and advantages of the invention will become further apparent from the following detailed description of the presently preferred embodiments, read in conjunction with the accompanying drawings. The detailed description and drawings are merely illustrative of the invention rather than limiting, the scope of the invention being defined by the appended claims and equivalents thereof.
-
FIG. 1A is schematic diagram of network of distributed data processing systems in accordance with the present invention; -
FIG. 1B is a schematic diagram of a computer architecture of a data processing system as known in the art; -
FIG. 2 is a block diagram of an architecture of a directory event system in accordance with the present invention; -
FIG. 3A is flowchart of one embodiment of an event message routine in accordance with the present invention; and -
FIG. 3B is flowchart of one embodiment of an event notification routine in accordance with the present invention. - With reference now to the figures,
FIG. 1A depicts a network of data processing systems. Distributeddata processing system 10 contains anetwork 20, anetwork 21, anetwork 22, anetwork 23, and anetwork 24, which are the media used to provide communications links between various devices and computers connected together within distributeddata processing system 10.Network 20,network 21,network 22,network 23, andnetwork 24 may include permanent connections, such as wire or fiber optic cables, or temporary connections made through telephone or wireless communications. - In the depicted example, a directory
service provider server 30, anevent master server 40, anevent service server 41, and anevent client server 44 are connected tonetwork 20 along with amaster directory database 31.Event service server 41, anevent client 42 and anevent client 43 are connected tonetwork 21 along with areplicate directory database 32.Event client 42, adirectory client 50 a, adirectory client 50 b, and adirectory client 50 c are connected tonetwork 22.Event client 43, adirectory client 50 d, adirectory client 50 e, and a directory client 50 f are connected tonetwork 23.Event client server 44, adirectory client 50 g, adirectory client 50 h, and a directory client 50 i are connected tonetwork 24. Directory clients 50 a-50 f are in electrical communication withreplicate directory database 32, anddirectory clients 50 g-50 i are in electrical communication withmaster directory database 31. -
Servers 30 and 40-43, and clients 50 a-50 i may be represented by a variety of computing devices, such as mainframes, personal computers, personal digital assistants (PDAs), etc. Distributeddata processing system 10 may includes additional servers, clients, networks, routers, and other devices not shown. - Distributed
data processing system 10 may include the Internet withnetwork 20,network 21,network 22,network 23 andnetwork 24 representing a worldwide collection of networks and gateways that use the TCP/IP suite of protocols to communicate with one another. Of course, distributeddata processing system 10 may also include a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN). - The present invention could be implemented on a variety of hardware platforms.
FIG. 1A is intended as an example of a heterogeneous computing environment and not as an architectural limitation for the present invention. - With reference now to
FIG. 1B , a diagram depicts typical computer architecture of a data processing system, such as those shown inFIG. 1A , in which the present invention may be implemented.Data processing system 60 contains one or more central processing units (CPUs) 62 connected tointernal system bus 61, which interconnects random access memory (RAM 63, read-only memory (ROM) 64, and input/output adapter 65, which supports various I/O devices, such asprinter 70,disk units 71, or other devices not shown, such as a sound system, etc. Acommunication adapter 66, auser interface adapter 67, and a display adapter 68 are also connected tobus 61.Communication adapter 66 providesbus 61 with access to a communication link 72.User interface adapter 67 connectsbus 61 to various user devices, such askeyboard 73 andmouse 74, or other device not shown, such as a touch screen, stylus, etc. Display adapter 68 connectsbus 61 to adisplay device 75. - Those of ordinary skill in the art will appreciate that the hardware in
FIG. 1B may vary depending on the system implementation. For example, the system may have one or more processors, and other peripheral devices may be used in addition to or in place of the hardware depicted inFIG. 1B . The depicted example is not meant to imply architectural limitations with respect to the present invention. In addition to being able to be implemented on a variety of hardware platforms, the present invention may be implemented in a variety of software environments. A typical operating system may be used to control program execution within the data processing system. - Referring to
FIGS. 1A and 2 , as known by those with ordinary skill in the art, directoryservice provider server 30 manipulates data withinmaster directory database 31 as directed by a directory data manipulation request from one of directory clients 50 a-50 i, andmaster directory database 30 thereafter replicates the manipulated data withinmaster directory database 30 to replicatedirectory database 31. Adirectory event system 11 in accordance with the present invention provides event notification(s) to one or more ofdirectory clients 50 g-50 i upon the manipulation of data inmaster directory database 31 by directoryservice provider server 10, and provides the event notification(s) to one or more of directory clients 50 a-50 f upon a replication of the manipulated data frommaster directory database 31 to replicatedirectory database 32. Directoryservice provider server 30 is therefore not burdened with the task of providing the event notification(s) to directory clients 50 a-50 i. As a result, directoryservice provider server 30 is consistently available to timely and effectively handle all directory data manipulation requests fromdirectory clients 50 d-50 i. -
Directory event system 11 will now be described herein as implemented withinevent master server 40,event service server 41, andevent client server 42. However, those of ordinary skill in the art will appreciate software equivalents forevent master server 40,event service server 41, andevent client server 42. -
Directory event system 11 comprises anevent message provider 40 a and aqueue 40 b withinevent master server 40. Directoryservice provider server 30operatively shares queue 40 b withevent message provider 40 a.Queue 40 b serves as the only link betweendirectory event system 11 and directoryservice provider server 30 to thereby enabledirectory event system 11 and directoryservice provider server 30 to operate independent of each other.Event message provider 40 a implements an event message routine 80 in accordance with the present invention as shown inFIG. 3A . - Referring additionally to
FIG. 3A , during stage S82 of routine 80,event message provider 40 amonitors queue 40 b to determine if directoryservice provider server 30 has sent a modification message MMN to queue 40 b. Modification message MMN is the description of a directory data manipulation request received by directoryservice provider server 30 and the corresponding manipulated data withinmaster directory database 31. Upon a determination that modification message MMN is inqueue 40 b,event message provider 40 a proceeds to stage S84 of routine 80 to assign a sequence number SNN to modification message MMN and to write sequence number SNN tomaster directory database 31. During its next replicate cycle,master directory database 31 replicates all data to replicatedirectory database 32 to thereby store the manipulated data and sequence number SNN within replicatedirectory database 32. Sequence number SNN serves as a marker indicating the corresponding manipulated data frommaster directory database 31 is stored within replicatedirectory database 32. -
Event message provider 40 a proceeds to stage S86 to provide an event message EMN toevent service server 41. Event message EMN includes an event notification ENN that is modification message MMN or an edited version thereof. Event message EMN further includes sequence number SNN.Event message provider 40 a then returns to stage S82 to await modification message MMN+1. - Referring again to
FIGS. 1A and 2 ,directory event system 11 further comprises a replicate data monitor 41 a and aqueue 41 b withinevent service server 41. In response to event message EMN, replicate data monitor 41 a implements anevent notification routine 90 in accordance with the present invention as shown inFIG. 3B . - Referring additionally to
FIG. 3B , during stage S92 of routine 90, replicate data monitor 41 a stores sequence number SNN withinqueue 41 b. Replicate data monitor 41 a proceeds to stage S94 of routine 90 to poll replicatedirectory database 32 for a sequence number SNMAX stored therein. Those of ordinary skill in the art will appreciate there can be a significant gap of time from a completion of the writing of sequence number SNN tomaster directory database 31 byevent message provider 40 a and a subsequent completion of the replication of all of the data withinmaster directory database 31, including the manipulated data and sequence number SNN, to replicatedirectory database 32. As such, those of ordinary skill in the art will further appreciate that sequence number SNN being greater than sequence number SNMAX is an indication that the replication of all of the data withinmaster directory database 31, including the manipulated data and sequence number SNN, has not occurred. Conversely, those of ordinary skill in the art will further appreciate that sequence number SNN being less than or equal to sequence number SNMAX is an indication that the replication of all of the data withinmaster directory database 31, including the manipulated data and sequence number SNN has occurred. - Thus, during stage S96 of routine 90, replicate data monitor 41 a compares sequence number SNN and sequence number SNMAX to determine if sequence number SNN is less than or equal to sequence number SNMAX. If sequence number SNN is greater than sequence number SNMAX, replicate data monitor 41 a loops back to stage S94. If sequence number SNN is less than or equal to sequence number SNMAX, replicate data monitor 41 a proceeds to stage S98 to provide event notification ENN (or an edited version thereof) to
event client server 42 andevent client server 43. - Referring again to
FIGS. 1A and 2 ,directory event system 11 further comprises anevent notifier 42 a and a directory client register 42 b withinevent client server 42. Each directory client of directory clients 50 a-50 c selectively registers for one or more event services via directory client register 42 b.Event notifier 42 a provides event notification ENN to each directory client 50 a-50 c that registered for an event service corresponding to event notification ENN. In response to event notification ENN, the registered directory client(s) 50 a-50 c can immediately poll replicatedirectory database 32 for the corresponding manipulated data. -
Directory event system 11 also comprises an event notifier analogous toevent notifier 42 a and a directory client register analogous directory client register 42 b withinevent client server 43 andevent client server 44.Event client server 43 provides event notification ENN to the registered directory client(s) 50 d-50 f in response to event notification ENN fromevent service server 41. In response to event notification ENN, the registered directory client(s) 50 d-50 f can immediately poll replicatedirectory database 32 for the corresponding manipulated data.Event client server 44 provides event notification ENN to the registered directory client(s) 50 g-50 i in response to event notification ENN fromevent master server 40. In response to event notification ENN, the registered directory client(s) 50 g-50 i can immediately pollmaster directory database 31 for the corresponding manipulated data. - It is important to note that while the present invention has been described in the context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the forms of instructions in a computer readable medium and a variety of other forms, regardless of the particular type of signal bearing media actually used to carry out the distribution. Examples of computer readable media include media such as EPROM, ROM, tape, paper, floppy disc, hard disk drive, RAM, CD-ROM, and transmission-type media, such as digital and analog communications links.
- While the embodiments of the present invention disclosed herein are presently considered to be preferred, various changes and modifications can be made without departing from the spirit and scope of the invention. The scope of the invention is indicated in the appended claims, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.
Claims (9)
1-4. (canceled)
5. A method for processing directory events in a computer, comprising:
operating a master database to replicate a data manipulation and a sequence number to a replicate directory database, said sequence number corresponding to an event notification; and
operating an event service server to provide said event notification to an event client server in response to said replication of said sequence number to said replicate directory database
operating said event client server to provide said event notification to at least one directory client registered to receive said event notification.
6-18. (canceled)
19. A system, comprising:
an event master server configured to assign a sequence number to a manipulation of a data within a master directory database;
an event service server configured to determine said sequence number being stored within a replicate directory database; and
an event client server configured to provide an event notification to at least one directory client when said sequence number is being stored within said replicated directory database, said event notification corresponding to said manipulation of said data.
20. (canceled)
21. (canceled)
22. A system comprising:
one or more directory service providers configured to manipulate data stored in at least one master directory database, each data manipulation assigned a sequence number by an event master server and each data manipulation replicated to at least one replicate directory database based on the assigned sequence number; and
an event client server configured to notify at least one directory client based on the replication to each replicate directory database wherein the directory service provider and a directory event system are linked only by a queue.
23-25. (canceled)
26. A system comprising:
one or more directory service providers configured to manipulate data stored in at least one master directory database, each data manipulation assigned a sequence number by an event master server and each data manipulation replicated to at least one replicate directory database based on the assigned sequence number;
an event client server configured to notify at least one directory client based on the replication to each replicate directory database; and
further comprising a directory client register, wherein the directory client register is configured to allow each directory client to selectively register for one or more event services.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/470,443 US20070005610A1 (en) | 2000-12-15 | 2006-09-06 | Method and system for processing directory events |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/738,368 US7136881B2 (en) | 2000-12-15 | 2000-12-15 | Method and system for processing directory events |
US11/470,443 US20070005610A1 (en) | 2000-12-15 | 2006-09-06 | Method and system for processing directory events |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/738,368 Continuation US7136881B2 (en) | 2000-12-15 | 2000-12-15 | Method and system for processing directory events |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070005610A1 true US20070005610A1 (en) | 2007-01-04 |
Family
ID=24967698
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/738,368 Expired - Fee Related US7136881B2 (en) | 2000-12-15 | 2000-12-15 | Method and system for processing directory events |
US11/470,443 Abandoned US20070005610A1 (en) | 2000-12-15 | 2006-09-06 | Method and system for processing directory events |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/738,368 Expired - Fee Related US7136881B2 (en) | 2000-12-15 | 2000-12-15 | Method and system for processing directory events |
Country Status (1)
Country | Link |
---|---|
US (2) | US7136881B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150142725A1 (en) * | 2006-12-19 | 2015-05-21 | Teradata Corporation | High-throughput extract-transform-load (etl) of program events for subsequent analysis |
Families Citing this family (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030182328A1 (en) * | 2001-10-29 | 2003-09-25 | Jules Paquette | Apparatus and method for sharing data between multiple, remote sites of a data network |
US20040066935A1 (en) * | 2002-10-02 | 2004-04-08 | Marino Francis C. | Method and apparatus for providing a message sequence count in a security system |
FI115432B (en) * | 2002-11-27 | 2005-04-29 | Netseal Mobility Technologies | Scalable and secure server cluster for IP traffic |
GB0228279D0 (en) * | 2002-12-04 | 2003-01-08 | Ibm | A synchronization method |
US7577965B2 (en) * | 2003-01-15 | 2009-08-18 | Alcatel | Push-based object request broker |
US8954420B1 (en) | 2003-12-31 | 2015-02-10 | Google Inc. | Methods and systems for improving a search ranking using article information |
US8099407B2 (en) | 2004-03-31 | 2012-01-17 | Google Inc. | Methods and systems for processing media files |
US8386728B1 (en) | 2004-03-31 | 2013-02-26 | Google Inc. | Methods and systems for prioritizing a crawl |
US7581227B1 (en) * | 2004-03-31 | 2009-08-25 | Google Inc. | Systems and methods of synchronizing indexes |
US7412708B1 (en) | 2004-03-31 | 2008-08-12 | Google Inc. | Methods and systems for capturing information |
US8161053B1 (en) | 2004-03-31 | 2012-04-17 | Google Inc. | Methods and systems for eliminating duplicate events |
US7680888B1 (en) | 2004-03-31 | 2010-03-16 | Google Inc. | Methods and systems for processing instant messenger messages |
US8275839B2 (en) | 2004-03-31 | 2012-09-25 | Google Inc. | Methods and systems for processing email messages |
US20050234929A1 (en) * | 2004-03-31 | 2005-10-20 | Ionescu Mihai F | Methods and systems for interfacing applications with a search engine |
US7725508B2 (en) * | 2004-03-31 | 2010-05-25 | Google Inc. | Methods and systems for information capture and retrieval |
US7333976B1 (en) | 2004-03-31 | 2008-02-19 | Google Inc. | Methods and systems for processing contact information |
US8631076B1 (en) | 2004-03-31 | 2014-01-14 | Google Inc. | Methods and systems for associating instant messenger events |
US8346777B1 (en) | 2004-03-31 | 2013-01-01 | Google Inc. | Systems and methods for selectively storing event data |
US7941439B1 (en) * | 2004-03-31 | 2011-05-10 | Google Inc. | Methods and systems for information capture |
US20060031317A1 (en) * | 2004-06-04 | 2006-02-09 | Wanrong Lin | System for synthesizing instant message and presence attributes from polled, queried and event information sources |
US8185555B2 (en) | 2004-10-22 | 2012-05-22 | International Business Machines Corporation | Model extension framework |
US9262446B1 (en) | 2005-12-29 | 2016-02-16 | Google Inc. | Dynamically ranking entries in a personal data book |
KR100823273B1 (en) | 2006-06-30 | 2008-04-21 | 삼성전자주식회사 | Method and apparatus for synchronizing Content Directory Service in Universal Plug and Play network |
KR100902505B1 (en) * | 2006-09-21 | 2009-06-15 | 삼성전자주식회사 | Method and apparatus for synchonizing CDS objects of UPnP Media Servers |
CA2565847A1 (en) * | 2006-10-27 | 2008-04-27 | Cognos Incorporated | System and method for controlling model editing and merging |
US7587435B2 (en) * | 2006-11-10 | 2009-09-08 | Sybase, Inc. | Replication system with methodology for replicating database sequences |
US20080270596A1 (en) * | 2007-04-25 | 2008-10-30 | Mark Frederick Wahl | System and method for validating directory replication |
US8402472B2 (en) * | 2007-09-14 | 2013-03-19 | International Business Machines Corporation | Network management system event notification shortcut |
US7970946B1 (en) * | 2007-11-27 | 2011-06-28 | Google Inc. | Recording and serializing events |
US8997076B1 (en) | 2007-11-27 | 2015-03-31 | Google Inc. | Auto-updating an application without requiring repeated user authorization |
US9122859B1 (en) | 2008-12-30 | 2015-09-01 | Google Inc. | Browser based event information delivery mechanism using application resident on removable storage device |
US8239529B2 (en) * | 2010-11-30 | 2012-08-07 | Google Inc. | Event management for hosted applications |
CN105302409A (en) * | 2014-07-11 | 2016-02-03 | 杭州华三通信技术有限公司 | Web desktop management method and apparatus |
FR3093258B1 (en) * | 2019-02-26 | 2022-03-18 | Alsid | METHOD FOR PROTECTING A PRIVATE COMPUTER NETWORK |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5924096A (en) * | 1997-10-15 | 1999-07-13 | Novell, Inc. | Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand |
US6834301B1 (en) * | 2000-11-08 | 2004-12-21 | Networks Associates Technology, Inc. | System and method for configuration, management, and monitoring of a computer network using inheritance |
US6907455B1 (en) * | 2000-06-29 | 2005-06-14 | Cisco Technology, Inc. | Apparatus and methods for providing an event driven notification over a network to a telephony device |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5819020A (en) * | 1995-10-16 | 1998-10-06 | Network Specialists, Inc. | Real time backup system |
US6052724A (en) * | 1997-09-02 | 2000-04-18 | Novell Inc | Method and system for managing a directory service |
US6192408B1 (en) * | 1997-09-26 | 2001-02-20 | Emc Corporation | Network file server sharing local caches of file access information in data processors assigned to respective file systems |
US6247017B1 (en) * | 1998-03-20 | 2001-06-12 | Sun Microsystems, Inc. | Server-client communication over a network |
US6098099A (en) * | 1998-04-21 | 2000-08-01 | International Business Machines Corporation | Third-party notification by network directory server |
US6249883B1 (en) * | 1998-06-29 | 2001-06-19 | Netpro Computing, Inc. | System and method for monitoring domain controllers |
US6446077B2 (en) * | 1998-09-21 | 2002-09-03 | Microsoft Corporation | Inherited information propagator for objects |
US6510450B1 (en) * | 1999-02-04 | 2003-01-21 | Novell, Inc. | Multiple storage class distributed nametags for locating items in a distributed computing system |
US6615223B1 (en) * | 2000-02-29 | 2003-09-02 | Oracle International Corporation | Method and system for data replication |
US20020042830A1 (en) * | 2000-03-31 | 2002-04-11 | Subhra Bose | System, method and applications real-time messaging over HTTP-based protocols |
-
2000
- 2000-12-15 US US09/738,368 patent/US7136881B2/en not_active Expired - Fee Related
-
2006
- 2006-09-06 US US11/470,443 patent/US20070005610A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5924096A (en) * | 1997-10-15 | 1999-07-13 | Novell, Inc. | Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand |
US6907455B1 (en) * | 2000-06-29 | 2005-06-14 | Cisco Technology, Inc. | Apparatus and methods for providing an event driven notification over a network to a telephony device |
US6834301B1 (en) * | 2000-11-08 | 2004-12-21 | Networks Associates Technology, Inc. | System and method for configuration, management, and monitoring of a computer network using inheritance |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150142725A1 (en) * | 2006-12-19 | 2015-05-21 | Teradata Corporation | High-throughput extract-transform-load (etl) of program events for subsequent analysis |
US10229175B2 (en) * | 2006-12-19 | 2019-03-12 | Teradata Us, Inc. | High-throughput extract-transform-load (ETL) of program events for subsequent analysis |
Also Published As
Publication number | Publication date |
---|---|
US7136881B2 (en) | 2006-11-14 |
US20020078256A1 (en) | 2002-06-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7136881B2 (en) | Method and system for processing directory events | |
KR100763318B1 (en) | Method and system for transaction pipeline decomposition | |
US8200815B1 (en) | Method and apparatus for network services metering | |
US6098093A (en) | Maintaining sessions in a clustered server environment | |
US7441008B2 (en) | Method for correlating transactions and messages | |
US8140644B2 (en) | Method and apparatus for updating application servers | |
JP4900982B2 (en) | Method for managing failover in a server cluster, failover server and computer program | |
US8196150B2 (en) | Event locality using queue services | |
US7426543B2 (en) | Accessing data stored in multiple locations | |
US7711845B2 (en) | Apparatus, method and system for improving application performance across a communications network | |
US20040215672A1 (en) | Accessing data based on user identity | |
KR20010103731A (en) | Method and apparatus for the dynamic filtering and routing of events | |
US20050028171A1 (en) | System and method enabling multiple processes to efficiently log events | |
US7149800B2 (en) | Auditing computer systems components in a network | |
US7680797B1 (en) | Methods and systems for providing a data access layer | |
EP1623558A1 (en) | Accessing data in a computer network | |
US7454501B2 (en) | Most eligible server in a common work queue environment | |
US6934761B1 (en) | User level web server cache control of in-kernel http cache | |
US20030140139A1 (en) | Self-monitoring and trending service system with a cascaded pipeline with a unique data storage and retrieval structures | |
US7526772B2 (en) | Method and apparatus for transforming systems management native event formats to enable correlation | |
US20020078182A1 (en) | Failover service method and system | |
US7792274B2 (en) | Techniques for performing multi-media call center functionality in a database management system | |
US20030225733A1 (en) | Method, system and program product for centrally managing computer backups | |
US20020169881A1 (en) | Method and apparatus for distributed access to services in a network data processing system | |
KR20190015817A (en) | Method, Apparatus and System for Monitoring Using Middleware |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GEHMAN, BYRON C.;ROBINSON, DAVID G.;REEL/FRAME:018211/0745 Effective date: 20001214 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |