Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual page 154

Chapter 9. Directory Design Examples
work in the countries where the Example Corp. offices are located. Example Corp. decides to launch
a company-wide LDAP directory to improve internal communication, to make it easier to develop and
deploy web applications, and to increase security and privacy.
Designing a directory tree for an international corporation involves determining how to collect directory
entries logically, how to support data management, and how to support replication on a global scale.
In addition, Example Corp. wants to create an extranet for use by its parts suppliers and trading
partners. An extranet is an extension of an enterprise's intranet to external clients.
The following sections describe the steps in the process of deploying a multinational directory service
and extranet for Example Corp. International.
9.2.1. Multinational Enterprise Data Design
Example Corp. International creates a deployment team to perform a site survey. The deployment
team determines the following from the site survey:
• A messaging server is used to provide email routing, delivery, and reading services for most of
Example Corp.'s sites. An enterprise server provides document publishing services. All servers run
on Red Hat Enterprise Linux 5 (32-bit).
• Example Corp. needs to allow data to be managed locally. For example, the European site will be
responsible for managing the Europe branch of the directory. This also means that Europe will be
responsible for the master copy of its data.
• Because of the geographic distribution of Example Corp.'s offices, the directory needs to be
available to users and applications 24 hours a day.
• Many of the data elements need to accommodate data values of several different languages.
NOTE
All data use the UTF-8 characterset; any other characterset violates LDAP standards.
The deployment team also determines the following about the data design of the extranet:
• Parts suppliers need to log in to Example Corp.'s directory to manage their contracts with Example
Corp. Parts suppliers depend on data elements used for authentication, such as name and user
password.
• Example Corp.'s partners will use the directory to look up contact details of people in the partner
network, such as email addresses and phone numbers.
9.2.2. Multinational Enterprise Schema Design
Example Corp. builds upon its original schema design by adding schema elements to support
the extranet. Example Corp. adds two new objects, the exampleSupplier object class and the
examplePartner object class.
The exampleSupplier object class allows one attribute, the exampleSupplierID attribute. This
attribute contains the unique ID assigned by Example Corp. International to each automobile parts
supplier with which it works.
144