Supplier Architecture - Netscape DIRECTORY SERVER 6.2 - DEPLOYMENT Deployment Manual

Table of Contents

Advertisement

A Multinational Enterprise and its Extranet
Hub servers that contain read-only copies of the data will be used to replicate
data to consumer servers.
The hub servers are located near important directory-enable applications such
as a mail server or a web server.
Hub servers remove the burden of replication from the supplier servers, so
the suppliers can concentrate on doing write operations. In the future, as
example.com
additional consumers do not affect the performance of the suppliers.
For more information about hub servers, refer to "Cascading Replication," on
page 117.

Supplier Architecture

For the
and uses database links to chain to the data of other localities. For the master
copy of its data, each locality uses a multi-master replication architecture. For
example, the supplier architecture for Europe, which includes the
dc=exampleCorp,dc=com
184
Netscape Directory Server Deployment Guide • December 2003
expands and needs to add more consumer servers, the
intranet, each locality keeps the master copy of its data
example.com
and
information, appears as follows:
dc=com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NETSCAPE DIRECTORY SERVER 6.2 - DEPLOYMENT and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

This manual is also suitable for:

Directory server 6.2

Table of Contents