The sample deployment scenarios include:
■
“Multi-Master Replication Deployment” on page 140
■
“Multi-Host Deployment with Windows NT” on page 141
Multi-Master Replication Deployment
In a multi-master replication (MMR) deployment, two Directory Server instances are installed
on dierent hosts. It is possible to run the hosts on dierent operating systems, but in this
scenario, both hosts are running on the same operating system.
Table 7–1 and Figure 7–2 illustrate how the Identity Synchronization for Windows components
are distributed between the two hosts.
TABLE 7–1 Component Distributionin a Multi-MasterReplication Deployment
Host1 Host2
Directory Server (oneinstance) as the secondary
master for synchronizedusers
Directory Server (oneinstance) as the preferred
master for synchronizedusers
Core (MessageQueue, CentralLogger, System
Manager, andConsole)
Directory Server Plugin
ActiveDirectory Connector
Directory Server Connector
Directory Server Plugin
The migration process keeps on-demand password synchronization running continuously on
the preferred master or on the secondary master.
Note – If both hosts are running on a Solaris operating system, then a third host running
Windows 2000 with Active Directory is required for synchronization purposes only. (No
components would be installed on the third host.)
The following gure illustrates the process for migrating Identity Synchronization for Windows
in a MMR deployment.
Other MigrationScenarios
SunJavaSystemDirectoryServerEnterpriseEdition6.0 MigrationGuide • March2007140
SunCondential:Registered