Deploying Dsfw In A Name-Mapped Setup; Section 4.2, "Deploying Dsfw In A Name-Mapped Setup; Depth And Width; Dc=Example,Dc=Com - Novell OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR WINDOWS Manual

Depth and Width

With this combination you get benefits of a tree that is spread both horizontally and vertically spread
out. This is best suited for organizations that have offices locally as well as globally and there is a
high requirement for load processing.
Deploying DSfW in a Combination Structure
Figure 4-4
Geographic
(Regional)
Geographic
dc=chi
(Location)
Operational

4.2 Deploying DSfW in a Name-Mapped Setup

If you already have an eDirectory setup but want to install DSfW in your environment, it is
recommended you utilise the existing eDirectory setup and install DSfW in a container in the
existing eDirectory tree. This way you can utilise all the user information in the eDirectory
container. This kind of setup is known as a name-mapped setup. Before you start the process of
installation, ensure you have read and understood the details in
Name-Mapped Setup.
In Figure 4-5 DSfW is installed in eDirectory container Asia. The container Asia becomes part of
the DSfW domain. If you have name-mapped an existing partition to a domain, you cannot name-
map the sibling partitions to create a domain. Using the example in
name-mapped the O=Asia partition, you cannot name-map the O=America or O=Europe partitions.
However, it is possible to map the partitions underneath O=Asia to a domain. So you can map the
OU=India partition to create a DSfW domain. But if you have already mapped O=Asia partition and
now want to map the OU=Delhi partition, it cannot be done without mapping the OU=India
partition. The boundaries of a domain are valid till it encounters another partition.
Installing DSfW in a tree root partition is not supported.

dc=example,dc=com

dc=amerc
dc=prv dc=tkyo
dc=hr
dc=pacrim
dc=hnkg
dc=sales
Installation Prerequisites for a
Figure 4-5, if you have already
dc=europe
Deployment Scenarios 27