Directory server schema replication

• US 20030088654A1
• Filed: 11/02/2001
• Published: 05/08/2003
• Est. Priority Date: 11/02/2001
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Good, Gordon, Smith, Mark C.
• Application Number:
  US10/003,040
• Publication Number:
  US 20030088654A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories

Abstract

A method of schema replication in a directory server including updating a schema at a replication supplier, computing a change sequence number, placing the change sequence number in an attribute on the replication supplier, initiating a replication session to a replication consumer, reading the change sequence number on the replication consumer, updating the schema on the replication consumer if the change sequence number on the replication consumer is less than the change sequence number on the replication supplier, and propagating a schema update from the replication supplier to each replication consumer.

Claims

1. A method of schema replication in a directory server, comprising:

updating a schema at a replication supplier;

computing a change sequence number;

placing the change sequence number in an attribute on the replication supplier;

initiating a replication session to a replication consumer;

reading the change sequence number on the replication consumer;

updating the schema on the replication consumer if the change sequence number on the replication consumer is less than the change sequence number on the replication supplier; and

propagating a schema update from the replication supplier to each replication consumer.

2. The method of claim 1, further comprising:

replacing contents of a schema entry on each replication consumer with contents of a schema entry on the replication supplier.

4. The method of claim 1, further comprising:

maintaining the schema on a master supplier server.

5. The method of claim 4, further comprising:

copying the schema to a plurality of servers after updating the master supplier.

6. The method of claim 1, further comprising:

holding the change sequence number on the replication consumer in an attribute.

7. The method of claim 1, further comprising:

querying the schema with standard Lightweight Directory Access Protocol operations.

8. The method of claim 1, further comprising:

modifying the schema with standard Lightweight Directory Access Protocol operations.

9. The method of claim 1, wherein the schema is updateable on an updateable master.

3. The method of claim 3, wherein contents are replaced using an update operation on the schema entry.

10. A method of schema replication in a directory server, comprising:

updating a schema at a replication supplier;

computing a change sequence number;

placing the change sequence number in an attribute on the replication supplier;

initiating a replication session to a replication consumer;

reading the change sequence number on the replication consumer;

updating the schema on the replication consumer if the change sequence number on the replication consumer is less than the change sequence number on the replication supplier;

propagating a schema update from the replication supplier to each replication consumer;

replacing contents of a schema entry on each replication consumer with contents of a schema entry on the replication supplier;

maintaining the schema on a master supplier server;

copying the schema to a plurality of servers after updating the master supplier;

holding the change sequence number on the replication consumer in an attribute;

querying the schema with standard Lightweight Directory Access Protocol operations; and

modifying the schema with standard Lightweight Directory Access Protocol operations.

11. A method of defining a schema in a directory server, comprising

identifying an object class in the schema;

placing the object class on an entry;

storing a data element in an attribute in the directory server used by the schema;

extending the schema with a new object class and a new attribute;

describing a document with a private field comprising a description of the object class and the attribute; and

representing the data element as an attribute-data pair.

12. The method of claim 11, further comprising:

defining the object class in the directory server;

storing the object class in the directory server; and

maintaining integrity of the data element stored in the directory server is by imposing constraints on data values.

13. The method of claim 11, wherein the object class defines allowed attribute types and required attribute types.

14. The method of claim 11, wherein the attribute is multi-valued.

15. The method of claim 11, wherein the attribute is single-valued.

16. The method of claim 11, wherein the private field is a human-readable description.

17. The method of claim 11, wherein the attribute-data pair comprises a descriptive attribute associated with a data element.

18. The method of claim 11, wherein the entry in the directory server is customizable.

19. The method of claim 11, wherein the attribute available for the entry in the directory server is customizable.

20. A method of defining a schema in a directory server, comprising

identifying an object class in the schema;

placing the object class on an entry;

storing a data element in an attribute in the directory server used by the schema;

extending the schema with a new object class and a new attribute;

describing a document with a private field comprising a description of the object class and the attribute;

representing the data element as an attribute-data pair;

defining the object class in the directory server;

storing the object class in the directory server; and

maintaining integrity of the data element stored in the directory server by imposing constraints on data values.

21. A computer system for schema replication a directory server, comprising:

a processor;

a memory; and

software instructions stored in the memory for enabling the computer system under control of the processor, to perform;

updating a schema at a replication supplier;

computing a change sequence number;

placing the change sequence number in an attribute on the replication supplier;

initiating a replication session to a replication consumer;

reading the change sequence number on the replication consumer;

updating the schema on the replication consumer if the change sequence number on the replication consumer is less than the change sequence number on the replication supplier; and

propagating a schema update from the replication supplier to each replication consumer.

22. The computer system of claim 21, wherein the software instructions further comprise instructions to perform:

replacing the contents of a schema entry on each replication consumer with contents of a schema entry on the replication supplier using an update operation.

23. The computer system of claim 21, wherein the software instructions further comprise instructions to perform:

maintaining the schema on a master supplier server.

24. The computer system of claim 21, wherein the software instructions further comprise instructions to perform:

copying the schema to a plurality of servers after updating the master supplier.

25. The computer system of claim 21, wherein the software instructions further comprise instructions to perform:

holding the change sequence number on the replication consumer in the attribute.

26. The computer system of claim 21, wherein the software instructions further comprise instructions to perform:

querying the schema with standard Lightweight Directory Access Protocol operations.

27. The computer system of claim 21, wherein the software instructions further comprise instructions to perform:

modifying the schema with standard Lightweight Directory Access Protocol operations.

28. An apparatus for replicating a schema in a directory server, comprising:

means for updating a schema at a replication supplier;

means for computing a change sequence number;

means for placing the change sequence number in an attribute on the replication supplier;

means for initiating a replication session to a replication consumer;

means for reading the change sequence number on the replication consumer;

means for updating the schema on the replication consumer if the change sequence number on the replication consumer is less than the change sequence number on the replication supplier; and

means for propagating a schema update from the replication supplier to each replication consumer.

29. An apparatus for defining a schema in a directory server, comprising:

means for identifying an object class in the schema;

means for placing the object class on an entry;

means for storing a data element in an attribute in the directory server used by the schema;

means for extending the schema with a new object class and a new attribute;

means for describing a document with a private field comprising a description of the object class and the attribute; and

means for representing the data element as an attribute-data pair.

30. The apparatus of claim 29, further comprising:

means for defining the object class in the directory server;

means for storing the object class in the directory server; and

means for maintaining integrity of the data element stored in the directory server by imposing constraints on data values.