Sun Microsystems 8190994 - Manual (Page 114)

EXAMPLE 7–1 Sample Export Configuration File (Continued)
name="uid"
syntax="1.3.6.1.4.1.1466.115.121.1.15"/>
parent.attr="CreationAttribute"
name="sn"
syntax="1.3.6.1.4.1.1466.115.121.1.15"/>
parent.attr="SignificantAttribute"
name="sn"
syntax="1.3.6.1.4.1.1466.115.121.1.15"/>
After the completion of configuration export, export11cnf reports the result of the operation.
If the operation fails, an appropriate error message is displayed with an error identifier.
Checking for Undelivered Messages
The migration process minimizes system downtime by preserving the connectors’ states in the
existing deployment. However, these states reflect only the last change received and
acknowledged by the Message Queue. Therefore, you do not know whether the message was
actually delivered and applied to the destination connector.
This behavior does not cause problems as long as the Message Queue remains the same.
However, you will lose any messages on the Message Queue during the migration process when
you install Message Queue 3.6.
You must verify that the synchronization topics on the existing Message Queue do not have any
undelivered messages before you proceed with the migration. The Identity Synchronization for
Windows checktopics utility enables you to verify that all the synchronization topics are
empty and the system is not causing any problem.
▼
Using the checktopics Utility
The checktopics utility is delivered in the migration directory of the Solaris/SPARC and the
Windows Identity Synchronization for Windows 6.0 package.
Note – The prerequisite to run checktopics is a Java Virtual Machine.
When you run the checktopics utility, it connects to the configuration directory, which
contains information about Synchronization User Lists (SULs) and current synchronization
Preparing for Identity Synchronization for Windows Migration
Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide • March 2007 114
Sun Confidential: Registered