Deciding Which Schema to Use for Messaging Server

Are you integrating Messaging Server with other Java Enterprise System component
products, such as Portal Server or Access Manager, which provide single
sign-on capabilities?

If you answer Yes, then you must use Schema
2.

Are you installing Messaging Server for the first time or
are you upgrading from an older version?

If you are installing
Messaging Server for the first time, use Schema 2.

If you are
upgrading from an older version of Messaging Server, you can either use Schema
1 or Schema 2.

LDAP Schema 1 and Messaging Server

LDAP Schema 1 is a provisioning schema that consists of both an Organization Tree and a DC Tree. This set of schema (at the time,
it was simply called “schema”) was supported in previous Messaging
Server 5.x versions.

In Schema 1, when Messaging Server searches for user or group entries,
it looks at the user's or group’s domain node in the DC Tree and extracts
the value of the inetDomainBaseDN attribute. This attribute
holds a DN reference to the organization subtree containing the actual user
or group entry.

Only sites that have installed previous versions of Messaging Server
should use Schema 1.

Note –

Migrating to Schema 2 is imperative if you plan to install Messaging
Server with other Sun Java System products in the future.

LDAP Schema 1 and Messaging Server Supported Provisioning
Tools

Schema 1 supports Sun ONE Delegated Administrator for Messaging
(formerly called iPlanet Delegated Administrator) as well as LDAP provisioning
tools. For more information, see Understanding Provisioning Tools.

LDAP Schema 2 (Native Mode) and Messaging Server

LDAP Schema 2 is a set of provisioning definitions that describes
the types of information that can be stored as entries by using the Directory
Server LDAP.

The native mode uses search templates to search the LDAP directory server.
Once the domain is found by using the domain search template, the user or
group search templates are used to find a specific user or group.

You should use native mode if you are installing Communications Suite for the
first time and you do not have other applications on your machine that are
dependent on a two-tree provisioning model. You should also use this mode
if you want to install other products in the Java Enterprise System product suite.

If you have an existing Communications Suite 5.x installation that uses Schema
1, and you want to integrate Communications Suite with other Java Enterprise Server
products, you should migrate your directory to Schema 2 after you upgrade
to Communications Suite 6. Refer to the Sun Java System Communications Services 6 2005Q4 Schema Migration Guide for information
on how to migrate from LDAP Schema version 1 to LDAP Schema version 2.

Note –

Schema 2 Native Mode is the recommended provisioning model for
all Sun Java System products in the Java Enterprise System product suite.

Use Schema 2 Compatibility if you have existing applications that require
Schema 1, but you also need functionality that requires Schema 2, for example,
Access Manager, single sign-on, and so forth.

Note –

Schema 2 compatibility mode is provided as a convenience in migrating
to the Schema 2 Native mode. Do not use Schema 2 compatibility mode as your
final schema choice. The migration process from Schema 1 to Schema 2 compatibility
mode and then finally to Schema 2 native mode is more complex that simply
migrating from Schema 1 to Schema 2 native mode. See the Sun Java System Communications Services 6 2005Q4 Schema Migration Guide for
more information.

Understanding Calendar Server Schema Choices

Two schema options are available and supported with Calendar Server:
Sun Java System LDAP Schema version 1 and Sun Java System LDAP Schema version
2.

Deciding Which Schema to Use for Calendar Server

Are you integrating Calendar Server with other Java Enterprise System component
products, such as Portal Server or Access Manager, which provide single sign-on
capabilities?

If you answer Yes, then you must use Schema
2 Native Mode.

Are you installing Calendar Server for the first time or are
you upgrading from an older version?

If you are installing Calendar
Server for the first time, use Schema 2 Native Mode.

If you are
upgrading from an older version of Calendar Server, you can either use Schema
1 or Schema 2 Native or Compatibility Mode.

Do you plan to use either Access Manager
CLI utilities for provisioning or single sign-on?

If you answer
Yes, use Schema 2 Native or Compatibility Mode.

Do you want to use the Calendar Server csdomain utility
for provisioning domains?

If you answer Yes, use Schema 2 Native
or Compatibility Mode. If you don’t plan to use the csdomain utility,
and you have an existing Calendar Server installation, use Schema 1.

If you don’t want to use either Access Manager or Calendar Server CLI utilities for provisioning, use can use either
Schema 2 Native Mode for new installations, or Schema 1 or Schema 2 Compatibility
Mode for existing Calendar Server installations.

LDAP Schema 1 and Calendar Server

LDAP Schema 1 is a provisioning schema that consists of both an Organization Tree and a DC Tree. This set of schema (at the time,
it was simply called “schema”) was supported in previous Calendar
Server 5.x versions.

When Calendar Server searches for user or group entries, it looks at
the user's or group’s domain node in the DC Tree and extracts the value
of the inetDomainBaseDN attribute. This attribute holds
a DN reference to the organization subtree containing the actual user or group
entry.

Only sites that have installed previous versions of Calendar Server
should use Schema 1.

Note –

Migrating to Schema 2 is imperative if you plan to install Calendar
Server with other Sun Java System products in the future.

LDAP Schema 1 and Calendar Server Supported Provisioning
Tools

LDAP Schema 2 (Native Mode) and Calendar Server

Schema 2 is a set of provisioning definitions that describes the types
of information that can be stored as entries by using the Directory Server
LDAP.

The native mode uses search templates to search the LDAP directory server.
Once the domain is found by using the domain search template, the user or
group search templates are used to find a specific user or group.

You should use native mode if you are installing Communications Suite for the
first time and you do not have other applications on your machine that are
dependent on a two-tree provisioning model. You should also use this mode
if you want to install other products in the Java Enterprise System product suite.

If you have an existing Communications Suite 5.x installation that uses Schema
1, and you want to integrate Communications Suite with other Java Enterprise Server
products, you should migrate your directory to Schema 2 after you upgrade
to Communications Suite 6. Refer to the Sun Java System Communications Services 6 2005Q4 Schema Migration Guide for information
on how to migrate from LDAP Schema version 1 to LDAP Schema version 2.

Note –

Schema 2 Native Mode is the recommended provisioning model for
all Sun Java System products in the Java Enterprise System product suite.

Use Schema 2 Compatibility if you have existing applications that require
Schema 1, but you also need functionality that requires Schema 2, for example,
Access Manager, single sign-on, and so forth.

Note –

Schema 2 compatibility mode is provided as a convenience in migrating
to the Schema 2 Native mode. Do not use Schema 2 compatibility mode as your
final schema choice. The migration process from Schema 1 to Schema 2 compatibility
mode and then finally to Schema 2 native mode is more complex that simply
migrating from Schema 1 to Schema 2 native mode. See the Sun Java System Communications Services 6 2005Q4 Schema Migration Guide for
more information.