Migrating User Plug-Ins Manually; Tasks To Be Performed After Manual Migration - Sun Microsystems Sun Java SystemDirectory Server Migration Giude

Migrating User Plug-Ins Manually

Note –
30 levels. Deep nesting can signify a circular group definition, where a nested group contains a
group that is also its parent. When a group with more than 30 nesting levels is encountered,
Directory Server stops calculating the isMemberOf attributes for additional levels.
Each time this happens, Directory Server logs an error. You safely ignore these errors, although
you should examine the definition of the group mentioned in the error message for potential
circular definitions.
Migrating User Plug-Ins Manually
User plug-ins cannot be migrated. If you have custom user plug-ins, recompile them and add
them to the Directory Server 6.0 instance manually. For a detailed list of plug-in API changes,
see Chapter 2, "Changes to the Plug-In API Since Directory Server 5.2, " in Sun Java System
Directory Server Enterprise Edition 6.0 Developer's Guide.

Tasks to be Performed After Manual Migration

If you have migrated your server manually, the following post-migration tasks are required
before you can run the new server.
If you have customized user plug-ins, these need to be recompiled and added to the new
■
server manually.
If the migrated server was part of a replicated topology, see
■
If you have customized backup, recovery, and installation scripts, you need to rewrite these
■
scripts to comply with the new version.
50 Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide • March 2007
During data migration, Directory Server checks whether nested group definitions exceed
Sun Confidential: Registered
Chapter 4.