Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual page 59

About Virtual DIT Views
Create a virtual DIT view hierarchy in the same way as a normal DIT hierarchy. Create the same
entries (for example, organizational unit entries) but with an additional object class (nsview) and
a filter attribute (nsviewfilter) that describes the view. After adding the additional attribute, the
entries that match the view filter instantly populate the view. The target entries only appear to exist in
the view; their true location never changes. Virtual DIT views behave like normal DITs in that a subtree
or a one-level search can be performed with the expected results being returned.
For information about adding and modifying entries, refer to "Creating Directory Entries" in the Red
Hat Directory Server Administrator's Guide
Figure 4.11. A Combined DIT Using Views
Figure 4.11, "A Combined DIT Using Views"
The DIT in illustrates what happens when the two DITs
Figure 4.10, "Examples of a Flat and an Organizationally-Based DIT"
shown in are combined using
views. Because views inherently allow entries to appear in more than one place in a view hierarchy,
this feature has been used to expand the ou=Sales entry to enable viewing the Sales entries either
by location or by product.
Given a set of virtual DIT view hierarchies, a directory user can use the view that makes the most
sense to navigate to the required entries. For example, if the target entries were those who live
in Mountain View, a view which begins by navigating using location-based information is most
appropriate. If it were an organizational question, the organization view would be a better choice. Both
of these views exist in the Directory Server at the same time and operate on the same entries; the
different views just have different objectives when displaying their version of the directory structure.
Figure 4.11, "A Combined DIT Using Views"
The entries in the views-enabled directory in are
contained in a flat namespace just below the parent of the top-most view in the hierarchy. This is not
required. The entries can exist in a hierarchy of their own. The only concern that a view has about the
placement of an entry is that it must be a descendant of the parent of the view hierarchy.
49