Novell EDIRECTORY 8.8 - GUIDE, Manual, Page: 81 / 574

Designing Your Novell eDirectory Network 81
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
2.5.2 Creating Accessibility Guidelines
After you have gathered information about user needs, you should determine the eDirectory objects
that you will use to create the users' environments. For example, if you create policy packages or
Application objects, you should determine how many you will create and where you will allow them
to be placed in the tree.
You should also determine how you will implement security to restrict user access. You should
identify any security precautions related to specific security practices. For example, you could warn
network administrators to avoid granting the eDirectory Supervisor right to Server objects because
this right is inherited by the file system.
2.6 Designing eDirectory for e-Business
If you use eDirectory for e-Business, whether you are providing a portal for services or sharing data
with another business, the recommendations already mentioned in this chapter might not apply to
you.
You might want to follow these suggested eDirectory e-business design guidelines instead:
• Create a tree with a limited number of containers.
This guideline depends on the applications you use and your implementation of eDirectory. For
example, a global deployment of a messaging server might require the more traditional
eDirectory design guidelines discussed earlier in this chapter. Or, if you are going to distribute
administration of users, you might create a separate Organizational Unit (OU) for each area of
administrative responsibility.
• Maintain at least two partitions.
Maintain the default partition at the Tree level, and create a partition for the rest of the tree. If
you have created separate OUs for administrative purposes, create partitions for each of the
OUs.
If you are splitting the load over multiple servers, consider limiting the number of partitions,
but still maintain at least two for backup or disaster recovery.
• Create at least three replicas of your tree for fault tolerance and load balancing.
Keep in mind that LDAP does not load balance itself. To balance the load on LDAP, consider
using Layer 4 switches.
• Create a separate tree for e-Business. Limit the network resources, such as servers and printers,
included in the tree. Consider creating a tree that contains only User objects.
You can use Novell Nsure Identity Manager to link this user tree to your other trees that contain
network information. For more information, see the
Novell Nsure Identity Manager
Administration Guide (http://www.novell.com/documentation/dirxml20/index.html) .
• Use auxiliary classes to customize your schema.
If a customer or application requires a User object that is different from the standard
inetOrgPerson, use auxiliary classes to customize your schema. Using auxiliary classes allows
application designers to change the attributes used in the class without needing to re-create the
tree.
• Increase LDIF-import performance.