Figure J-1 Example 1
The WIDGETS_INC tree has the following configuration:
o=widget, ou=blr,o=widget, and ou=sales,ou=blr,o=widget are eDir partitions as well as name mapped domains.
ou=prv, o=widget, ou=wal,o=widget, ou=hr,ou=prv,o=widget are partitions (but not domains)
ou=end,ou=prv,o=widget refers to the top of a subtree but not a partition. It is a container under the ou=prv,o=widget partition.
S1-S6 and S9 are OES servers
S7 and S8 are NetWare servers
S1, S2, S3, and S4 are DSfW servers and serve volumes over Samba and NCP
S5 serves its volumes over AFP and NCP
S6 serves its volumes over CIFS and NCP
S7 serves its volumes over AFP, CIFS, and NCP
S8 serves its volumes over NetWare CIFS, NetWare AFP, and NCP
S9 serves its volumes over AFP, Samba, and NCP
NOTE:Although Novell CIFS and Samba can both be installed on the same machine, they cannot run together because of a port conflict. The administrator can configure either Samba or Novell CIFS on a single machine, but not both.
Users from all over the tree can access services running on S1-S9. In order for users to be able to access AFP/CIFS services, the search contexts (eDirectory contexts) for these services should be configured to the subtrees under which those users can be found.
Installation and configuration in iManager must be done by an OES administrator. This is typically a container administrator in eDirectory who has supervisory privileges over the container where the server is being installed. This need not be the tree administrator.
In this scenario, the setup of the tree and file services is similar to that in Example 1, but the users are local to the context where a particular service is installed.
Figure J-2 Example 2
S1, S2, S3, and S4 are DSfW servers and serve their volumes over Samba and NCP
S5, S6, and S7 serve their volumes over AFP and NCP
S8 and S9 serves their volumes over CIFS and NCP
For example, u1 is a user under the container ou=prv,o=widget and is expected to access AFP services on S5, S6, and S7. Similarly, u2 is a user under the container ou=wal,o=widget and is expected to access CIFS services on S8 and S9.