By Joesciallo-Oracle on Mar 25, 2007
Short description of this doc:
This article compares the Sun Java System LDAP schema modes used by the Sun Java Communications Suite products. It includes an overview and history of both modes, an example of domain and user LDAP entries for both schema modes, and a discussion on how to decide which mode is appropriate for you.
Shorter article, for those who don't have the time to digest it all:
- You should use the same schema version for all Communications Suite products sharing the same LDAP directory.
- If you require Sun Java System Access Manager to share the same LDAP user directory with Communications Suite products, use one of the Schema version 2 modes.
You should not use Schema version 1 mode unless you satisfy all of the following criteria.
- You have an earlier version of one of the Communications Suite products already installed using Schema version 1.
- And, you don't want to use Access Manager.
- And, you don't want to migrate your LDAP database to either mode of Schema version 2.
- If Sun Java Communications Suite Delegated Administrator does not have the features you require, but iPlanet Delegated Administrator does, use Schema version 1 mode.
- If you are installing Communications Suite products for the first time, choose the Schema version 2 mode that integrates most easily with your current DIT structure. You can choose between Schema version 2 native mode or compatibility mode. The two modes are defined in Schema Version 2 Background Information.
As one astute commentator noted to me offline, once you are convinced that you ought to migrate your deployment from V.1 to V.2, what next? Apologies, we neglected to include a pointer in this article to the Schema Migration Guide, which "describes how to migrate Sun Java System LDAP Directory data from LDAP Schema 1 to LDAP Schema 2 for Sun Java Communications Suite, specifically Sun Java System Messaging Server and Sun Java System Calendar Server."