Specifying the LDAP Schema for a Solution

Java ES solutions that use Directory Server can use either of two versions of a standard LDAP schema, which are known as Schema 1 and Schema 2. Your user management specification must specify whether your solution uses Schema 1 or Schema 2.

Schema 2 supports the use of Access Manager, and Access Manager's single sign-on feature. If a solution uses Access Manager, it must use Schema 2.

The installation process configures the directory for the specified schema as follows:

• To establish a Schema 1 directory, simply install Directory Server. Schema 1 is the default schema version.

• To establish a Schema 2 directory, install Directory Server and Access Manager. Installing Access Manager modifies the directory and converts it to a Schema 2 directory.

  ---

  Tip –

  If Directory Server and Access Manager are installed on one computer in one installer session, the directory is configured for Schema 2.

  If your solution is distributed, you install Directory Server first, on one computer. You then install Access Manager on a second computer. When you install Access Manager you specify the existing directory on the remote computer, and the directory's schema is configured for Schema 2.

  ---

Depending on your solution, the following procedures for extending the schema might be necessary:

• If your solution uses components from the Communications Suite (Messaging Server and or Calendar Server), your installation process must apply some additional schema extensions with the Directory Preparation Tool. These extensions are applied before Messaging Server or Calendar Server are installed. They can be applied to either Schema 1 or Schema 2 directories. For an example of an installation plan that includes instructions for the Directory Preparation Tool, see Sun Java Enterprise System 2005Q4 Deployment Example: Telecommunications Provider Scenario

• If your solution uses Schema 2, the installation process must apply some additional schema extensions with Delegated Administrator to support Access Manager authentication and authorization for the messaging and calendar services. For an example of an installation plan that applies these schema extensions, see Sun Java Enterprise System 2005Q4 Deployment Example: Telecommunications Provider Scenario.

Your LDAP schema specification identifies the schema used in your solution and any schema extensions required by your solution.