Previous Contents Index Next
List of Figures Figure 2-1 Sample DSML-Enabled Directory Deployment Figure 4-1 Two Root Suffixes in a Single Directory Server Figure 4-2 One Root Suffix with Multiple Subsuffixes Figure 4-3 Two Suffixes Stored in Two Different Databases Figure 4-4 Sample Directory Information Tree Using 5 Branching Points Figure 4-5 ISP ExampleHost.com Directory Information Tree Figure 4-6 Example.com Corporation Directory Information Tree Figure 4-7 ExampleHost.com Internet Host Directory Information Tree Figure 4-8 Three Primary Networks in Example.com Corporation DIT Figure 4-9 Detailed View of Three Primary Networks in Example.com Corporation DIT Figure 4-10 Directory Information Tree for ExampleHost.com Figure 4-11 Detailed View of the DIT for ExampleHost.com Figure 4-12 Example of a Pointer CoS Definition and Template Figure 4-13 Example of an Indirect CoS Definition and Template Figure 4-14 Example of a Classic CoS Definition and Template Figure 5-1 Directory Tree With Three Subsuffixes Figure 5-2 Three Subsuffixes Stored in Three Separate Databases Figure 5-3 Example.com's Three Databases Stored on Two Servers A and B Figure 5-4 Example.com Directory Tree Figure 5-5 Example.com Corporation's Directory Tree Split Across Five Databases Figure 5-6 Example.com Corporation Suffixes and Associated Entries Figure 5-7 ExampleISP.com Directory Tree with One Suffix Figure 5-8 ExampleISP.com's Directory Tree With Two Suffixes Figure 5-9 Smart Referral From American Directory to European Directory Figure 5-10 Smart Referral Traffic Figure 5-11 Circular Referral Pattern Caused by the Overuse of Smart Referrals Figure 5-12 Chaining Operation Figure 5-13 Client Application Search Request Redirected Through a Referral Figure 5-14 Search Request using Chaining Figure 5-15 Chaining Using Two Chained Suffixes to Process a Client's Search Request Figure 6-1 Single-Master Replication Figure 6-2 Multi-Master Replication Configuration (Two Masters) Figure 6-3 Fully Meshed, Four-Way, Multi-Master Replication Configuration Figure 6-4 Replication Configuration for Master A (Fully Meshed Topology) Figure 6-5 Replication Configuration for Consumer Server E (Fully Meshed Topology) Figure 6-6 Cascading Replication Configuration Figure 6-7 Server Configuration in Cascading Replication Figure 6-8 Combined Multi-Master and Cascading Replication Figure 6-9 Using Multi-Master Replication for Load Balancing Figure 6-10 New York and Los Angeles Subtrees in Respective Geographical Locations Figure 6-11 Load Balancing Using Multi-Master and Cascading Replication Figure 6-12 Retro Change Log and Multi-Master Replication Figure 6-13 Simplified Topology for Replication of the Retro Change Log Figure 6-14 Failover of the Retro Change Log Figure 7-1 Attribute Encryption Logic Figure 8-1 SNMP Monitoring in Directory Server Figure 9-1 Binary Backup Figure 9-2 Backup Using db2ldif -r Figure 9-3 Binary Restore Figure 9-4 Restore Using ldif2db Figure 9-5 One Data Center - Basic Topology Figure 9-6 One Data Center Scaled For Read Performance Figure 9-7 Single Data Center Recovery Sample Procedure (One Component) Figure 9-8 Two Data Centers Basic Topology Figure 9-9 Two Data Centers Scaled For Read Performance Figure 9-10 Two Data Centers Recovery Replication Agreements Figure 9-11 Three Data Centers Basic Topology Figure 9-12 Three Data Centers Scaled For Read Performance Figure 9-13 Three Data Centers Recovery Replication Agreements Figure 9-14 Five Data Centers Basic Topology Figure 9-15 Five Data Centers Recovery Replication Agreements Figure 9-16 One Data Center Using the Retro Change Log Plug-in Figure 9-17 One Data Center Using the Retro Change Log Plug-in (Scaled) Figure 9-18 One Data Center Using the Retro Change Log Plug-in (Recovery) Previous Contents Index Next Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Copyright 2005 Sun Microsystems, Inc. All rights reserved.