HP-UX Directory Server 8.1 administrator guide

2.4.8 Configuring cascading chaining
The database link can be configured to point to another database link, creating a cascading
chaining operation. A cascading chain occurs any time more than one hop is required to access
all the data in a directory tree.
• “Overview of cascading chaining”
• “Configuring cascading chaining using the console”
• “Configuring cascading chaining from the command line”
• “Detecting loops”
• “Summary of cascading chaining configuration attributes”
• “Cascading chaining configuration example”
2.4.8.1 Overview of cascading chaining
Cascading chaining occurs when more than one hop is required for the directory to process a
client application's request.
The client application sends a modify request to Server 1. Server one contains a database link
that forwards the operation to Server 2, which contains another database link. The database link
on Server 2 forwards the operations to server three, which contains the data the clients wants to
modify in a database. Two hops are required to access the piece of data the client want to modify.
During a normal operation request, a client binds to the server, then any ACIs applying to that
client are evaluated. With cascading chaining, the client bind request is evaluated on Server 1,
but the ACIs applying to the client are evaluated only after the request has been chained to the
destination server, in the above example Server 2.
For example, on Server A, a directory tree is split:
2.4 Creating and maintaining database links 79