Sun Microsystems 8190994 Server User Manual


  Open as PDF
of 148
 
Note – By default, StartTLS is not enabled on Windows. If you are running dsmig on Windows,
use the -e or -–unsecured option to specify an unsecure connection. Alternatively, use the -Z
or --use-secure-port option to specify a secure connection over SSL. If you do not use either
of these options on Windows, dsmig issues a warning and the migration process terminates
with an error.
For more information see dsmig(1M). For details of the specic conguration attributes that are
migrated, see
“Migration of Specic Conguration Attributes” on page 38.
Plug-in Conguration Data
dsmig migrates conguration data for certain Directory Server plug-ins only. For most system
plug-ins, conguration data is not migrated automatically.
dsmig migrates all conguration data for the CoS plug-in. In addition, dsmig migrates the
enabled or disabled state for the following system plug-ins:
■
7–bit Check
■
DSML Frontend
■
Pass-Through Authentication
■
Referential Integrity
■
Retro Change Log
■
UID Uniqueness
When you migrate the conguration in verbose mode, dsmig issues a warning indicating which
system plug-in congurations are not migrated.
Plug-ins that you have created are not migrated. However, during the migration process user
plug-in conguration data is dumped in the le
new-instance-path/migration/old_userplugins_conf.ldif. These plug-ins must be
recompiled when the migration is complete.
Chained Sux Conguration Data
Conguration data for chained suxes is not migrated. By default, the conguration data is
dumped in the le new-instance-path/migration/old_chaining_conf.ldif. You can import
the chaining conguration data from this le after migration, if required.
Usingdsmigto MigrateCongurationData
SunJavaSystemDirectoryServerEnterpriseEdition6.0 MigrationGuide • March200732
SunCondential:Registered
 previous next