Table of Contents
Advertisement
A Multinational Enterprise and its Extranet
•
Many of the data elements need to accommodate data values of several
different languages and characters sets.
The deployment team also determines the following about the data design of the
extranet:
•
Suppliers will need to log in to
contracts with
for authentication, such as name and user password.
•
example.com
addresses and phone number of people in the partner network.
Schema Design
example.com
to support the extranet.
object class and the
The
exampleSupplier
attribute. This attribute contains the unique ID assigned by
International to each auto part supplier it works with.
The
examplePartner
attribute. This attribute contains the unique ID assigned by
International to each trade partner.
For information about customizing the default directory schema, refer to
"Customizing the Schema," on page 46.
Directory Tree Design
example.com
•
The directory tree is rooted in the suffix
example.com
contains data internal to
dc=exampleNet,dc=com
•
The directory tree for the intranet (under
main branches, each corresponding to one of the regions where
has offices. These branches are identified using the
156
Netscape Directory Server Deployment Guide • January 2002
. Suppliers will depend upon data elements used
example.com
's partners will use the directory as a way to look up the email
builds upon its original schema design by adding schema elements
example.com
examplePartner
object class allows one attribute, the
object class allows one attribute, the
creates a directory tree as follows:
creates two branch. One branch,
example.com
, contains data for the extranet.
's directory to manage their
example.com
adds two new objects, the
object class.
. Under this suffix,
dc=com
dc=exampleCorp,dc=com
International. The other branch,
dc=exampleCorp,dc=com)
l(locality)
exampleSupplier
exampleSupplierID
example.com
examplePartnerID
example.com
,
has three
example.com
attribute.
Advertisement
Table of Contents
