Provisioning Rules Before and After Schema Migration (Sun Java System Communications Services 6 2005Q4 Schema Migration Guide)

Sun Java System Communications Services 6 2005Q4 Schema Migration Guide

Provisioning Rules Before and After Schema Migration

Before and after the directory migration, your installation components can be in a mixed state, as described in Potential Restrictions During Migration. Constraints on provisioning depend on the relationships between the server version and configuration and the current schema level.

Provisioning Rules Before and After Schema Migration shows a matrix of the current directory schema level, the current server version and configuration, the provisioning tool you can use with each combination, and the provisioning constraints.

Table 2–1 Provisioning Constraints in a Mixed Environment


Directory Schema Level	Server 5.x	Server 6 - configured for Schema 1	Server 6 - configured for Schema 2
Schema 1	1 For Messaging Server, use Delegated Administrator. For Calendar Server, use the Calendar Server command-line utilities. Full provisioning available.	2 For Messaging Server, use Delegated Administrator. For Calendar Server, use the Calendar Server command-line utilities. Full provisioning available.	3 Invalid combination for provisioning. *
Schema 2, compatibility mode	4 Use `commadmin`. Full provisioning available.	5 Use `commadmin`. Full provisioning available.	6 Invalid combination for provisioning. *
Schema 2, native mode	7 Invalid combination for provisioning.	8 Use `commadmin`. No domain provisioning. No administrative provisioning.	9 Use `commadmin`. Full provisioning available.
* A Server 6 configured for Schema 2 will not run against a Schema 1 directory or a Schema 2, compatibility mode, directory.

The following characteristics apply to the server-schema configurations shown in Provisioning Rules Before and After Schema Migration. They are numbered 1 - 9 for identification, not to indicate a required sequence of steps:

Configuration 1 is the beginning state of the migration.
Configuration 9 is the target state of the migration.
Configurations 2, 4, 5, and 8: These are interim states that can exist during the migration process (particularly when multiple servers are involved and you migrate one server at a time).
Configurations 3 and 6: You should never configure a server to use Schema 2 when the directory is Schema 1 or Schema 2, compatibility mode. Only configure a server to use Schema 2 after you migrate to Schema 2, native mode.
Configuration 7: Do not provision with this configuration. This state can exist temporarily during an incremental migration of multiple servers and directory domains, when some domains have been migrated to Schema 2 and others are still in Schema 1. However, you cannot use 5.x provisioning tools to provision against the Schema 2 domains.
Configurations 8: This state only works if you do not remove the DC Tree.