Distributed directory deployment

• US 7,373,348 B2
• Filed: 04/14/2005
• Issued: 05/13/2008
• Est. Priority Date: 04/14/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cavage, Mark Joseph, Hazlewood, Kristin Marie, Heller, Richard Allyn, Bell, Jason Murray
• Primary Examiner(s): Chace; Christian
• Assistant Examiner(s): Veillard; Jacques
• Application Number:
  US11/106,396
• Publication Number:
  US 20060248117A1
• Time in Patent Office: 1,125 Days
• Field of Search: 707 1- 4, 707/9, 707/10, 707100-102, 707/103.R, 707/104.1, 709/203, 709/219, 709/220, 709/223, 709/225, 709/226, 709/229
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Each LDIF entry of a directory tree is read, split to a domain of LDIF fragments (corresponding to backend servers) and written to each LDIF fragment. The split may be accomplished through a hash function, establishing, for that iteration of LDIF entry, a write file. The LDIF entry is appended to the write file. A subsequent LDIF entry is read. A corresponding LDIF fragment is determined, which need not be different from the LDIF fragment to which the first LDIF entry was written. The current LDIF entry is written to the currently selected write file. The process continues until all LDIF entries are exhausted from the directory tree. LDIF fragments are each copied to distinct backend servers, where, each LDIF fragment may be loaded into a distributed directory data structure.

Claims

1. A method for creating at least two LDIF (Lightweight Directory Access Protocol Data Interchange Format) fragments the method comprising the computer implemented steps of:

reading a setup configuration having a first LDIF fragment name corresponding to a first LDIF fragment and a second LDIF fragment name corresponding to a second LDIF fragment;

reading a plurality of successive LDIF entries from a directory information tree (DIT);

determining for each LDIF entry whether each LDIF entry should be written to a first LDIF fragment or to a second LDIF fragment based on a split function; and

writing each LDIF entry to the first LDIF fragment or to the second LDIF fragment based on the split function.

2. The method of claim 1 further comprising:

bulkloading the first LDIF fragment to a first backend server; and

bulkloading the second LDIF fragment to a second backend server, wherein the bulkloading of the first LDIF fragment and the bulkloading of the second LDIF fragment occur in parallel.

3. The method of claim 1 further comprising:

determining for each LDIF entry whether each LDIF entry is a descendant node of a BaseDN, wherein the BaseDN specifies a split point of the DIT; and

writing each LDIF entry to a root output file based on determining each LDIF entry is not a descendant node of the BaseDN.

4. The method of claim 3 further comprising:

bulkloading the root output file to a third backend server.

5. The method of claim 4 further comprising:

bulkloading the first LDIF fragment to a first backend server; and

bulkloading the second LDIF fragment to a second backend server, wherein the bulkloading of the first LDIF fragment, bulkloading the second LDIF fragment and the bulkloading of the root output file occur in parallel.

6. The method of claim 5 further comprising:

constructing a setup configuration prior to reading the setup configuration.

7. The method of claim 6 further comprising:

parsing a command line to locate a setup configuration file.