Method and system for processing directory events

• US 7,136,881 B2
• Filed: 12/15/2000
• Issued: 11/14/2006
• Est. Priority Date: 12/15/2000
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gehman, Byron C., Robinson, David G.
• Primary Examiner(s): Gaffin, Jeffrey
• Assistant Examiner(s): ABEL JALIL, NEVEEN
• Application Number:
  US09/738,368
• Publication Number:
  US 20020078256A1
• Time in Patent Office: 2,160 Days
• Field of Search: 707/10, 707/100, 707/102, 707/209, 707/202, 707 1-1041, 707/103.R, 707/218, 707/230, 714/5, 714/42, 714/25, 709/229, 709/226, 709/217
• US Class Current: 1/1
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A directory event system for providing timely event notifications of each corresponding data replication of a master directory database to a replicate directory database 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 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 a 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.

Claims

1. A method of processing directory events in a computer, comprising:

operating a directory service provider server to perform a data manipulation within a master directory database;

operating an event master server to assign a sequence number to said data manipulation; and

operating said event master server to store said sequence number within said master directory database;

operating said event master server to provide an event message to an event service server, said event message including said sequence number and an event notification;

operating said master database to replicate said sequence number to a replicate directory database; and

operating ,said 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.

2. The method of claim 1, further comprising:

operating said event client server to provide said event notification to at least one directory client registered to receive said event notification.

3. A system, comprising:

a master directory database configured to store data;

a directory service provider server configured to manipulate said data;

an event master server configured to assign a first sequence number to any manipulation of said data within said master directory database by said directory service provider server, wherein said event master server is further configured to store said first sequence number within said master directory database;

a replicate directory database configured to store said data, wherein said master directory database is further configured to replicate said data and a second sequence number to said replicate directory database;

an event service server configured to poi said replicate directory database for said second sequence number in response to said first sequence number from said event master server;

a directory client; and

an event client server configured to provide an event notification to said directory client, wherein said event service server is further configured to provide said event notification to said event client server when said first sequence number is less than or equal to said second sequence number.

4. 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 a queue,

wherein the queue stores modification messages, wherein a modification message is stored in the queue, an event message provider assigns a sequence number to the modification message, wherein the sequence number serves as a marker indicating that the corresponding manipulated data from the master directory database is stored within each replicate directory database.

5. The system of claim 4 wherein the event message provider provides an event message to the event service server, the event message including an event notification comprising the modification message or an edited version of the modification message, the event message further including the sequence number.

6. The system of claim 5 further comprising a replicate data monitor, the replicate data monitor configured to poll the replicate directory database for the maximum sequence number, the replicate data monitor further configured to compare the maximum sequence number to a current sequence number to determine whether the current sequence number is equal to or less than the maximum sequence number, and the replicate data monitor configured to provide an event notification to the event client server when the current sequence number is equal to the maximum sequence number.