This section goes through a number of real-world examples and explains how views can be harnessed to meet these requirements.
Views can be useful if your directory contains highly repetitive information. For example, each user entry contains office location and contact details which are identical for many users. This uses a lot of space for caching and backups and is complex to update.
To solve this, use views in the following way:
If your directory has one-to-many subordinate entries that each contains various preference information, you could use a view to perform a single search returning the entry you are interested in, and all its subordinates.
To do this, create a view that retrieves a target entry.
The result of this search (base-object of entry returned) can then be used to perform a one-level/subtree search to return the entry's subordinates.
A view can remove values before it returns the result. This can be useful for restricting access.
For example, a pay TV customer that has subscribed to a package that includes adult content, wishes to have adult content disallowed as they have small children.
A view can be created to retrieve the services for a particular package a user has subscribed to.
The next phase of the view can retrieve restricted items that can then be pruned from the values/objects retrieved above.
An overlay directory lets you augment entries in a another directory with extra attributes. This lets you use CA Directory to extend the schema of an existing less-flexible directory.
Views can be used to achieve this by storing entries in another directory instance that share unique values with the other directory. A view can be created to retrieve the two linked entries and merge the result into a single entry.
Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |