Sun Microsystems 8190994 manual Plug-in Configuration Data, Chained Suffix Configuration Data

Using dsmig to Migrate Configuration Data

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 specific configuration attributes that are migrated, see “Migration of Specific Configuration Attributes” on page 38.

Plug-in Configuration Data

dsmig migrates configuration data for certain Directory Server plug-ins only. For most system plug-ins, configuration data is not migrated automatically.

dsmig migrates all configuration 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 configuration in verbose mode, dsmig issues a warning indicating which system plug-in configurations are not migrated.

Plug-ins that you have created are not migrated. However, during the migration process user plug-in configuration data is dumped in the file new-instance-path/migration/old_userplugins_conf.ldif. These plug-ins must be recompiled when the migration is complete.

Chained Suffix Configuration Data

Configuration data for chained suffixes is not migrated. By default, the configuration data is dumped in the filenew-instance-path/migration/old_chaining_conf.ldif. You can import the chaining configuration data from this file after migration, if required.

32 Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide • March 2007

Sun Confidential: Registered