Sun Java System Directory Server Enterprise Edition 6.3 Migration Guide

Multi-Host Deployment with Windows NT

Three hosts are used in this deployment scenario:

Table 7–2 and Figure 7–3 illustrate how the Identity Synchronization for Windows components are distributed between the three hosts.

Table 7–2 Multi-Host Deployment

Host 1 

Host 2 

Host 3 

Directory Server with configuration repository 

Directory Server for synchronized users 

Windows NT Connector 

Core (Message Queue, Central Logger, System Manager, and Console)

Directory Server Connector 

Windows NT Subcomponents (Password Filter DLL and Change Detector Service)

Active Directory Connector

Directory Server Plugin 


In the previous scenario, hosts 1 and 2 are running on the same operating system.

Note –

Directory Server at host1 contains the configuration registry and the Admin Server console. Ensure you migrate to Directory Server 6.0 using the -N option to keep the Admin Server intact. For more information on migrating configuration data and user data, see Using dsmig to Migrate Configuration Data and Using dsmig to Migrate User Data respectively.

Directory Server at host2 contains the data and the Directory Server plugin. When you migrate Directory Server to 6.0, the plugin configuration is lost. But it does not cause any problem as Identity Synchronization for Windows migration requires the connectors to be reinstalled and plugin to be reconfigured. Therefore, Directory Server at host2 should be migrated after Identity Synchronization for Windows uninstallation.

If both hosts are running a Solaris operating system, then a fourth host running Windows 2000 with Active Directory is required for synchronization purposes only. (No components would be installed on the fourth host.)

Figure 7–3 illustrates the process for migrating Identity Synchronization for Windows for a multi-host deployment

Figure 7–3 Migrating a Multi-Host Deployment with Windows NT

Flow diagram showing steps for upgrading a multi-host
deployment with Windows NT.