test

Sun Java Enterprise System 2005Q4 Installation Planning Guide

Directory Server

Directory Server provides LDAP directory services for other components. The directory can be used for data about the configuration of other components, data about users and groups of users, or both.

Examine your deployment architecture. Locate any instances of Directory Server. Directory Server has no dependencies on other components, and you can install Directory Server first, on the specified computer systems.

Tip –

For information on setting up Directory Server replication, see Sun Java System Directory Server 5 2005Q1 Administration Guide.

Tip –

If your solution runs a 32-bit Directory Server on a 64-bit Solaris SPARC Platform, some special considerations apply. For more information, see Directory Server Postinstallation Configuration in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

Basic Installation Procedures for Directory Server

The basic procedures for installing and configuring Directory Server are as follows:

A

  1. Install and configure Directory Server on the computer systems specified in your deployment architecture. When you install Directory Server, you specify the base, or root, DN for the directory tree and the administrator accounts.

  2. Start and verify all of the Directory Server instances.

  3. If your solution uses load balancing, verify that the load balancing is routing requests among the Directory Server instances.

  4. If your solution uses Directory Server multi-mastering replication, shut down all but one of the Directory Server instances.

  5. Install and configure the other Java Enterprise System components in your solution. Depending on what other components are used in your solution, installing and configuring the other component instances can add configuration data to the directory, update the LDAP schema, or modify the LDAP directory tree. The effects of installing and configuring other components are described in the following sections, component by components.

B

If your solution uses multi-mastering replication, you complete the configuration of Directory Server after all other components are installed and configured. The basic steps for this are as follows:

  1. After all other components are installed and configure, restart the Directory Server instances that you shut down in A.

  2. Configure multi-master replication. This will synchronize the contents of the directories (copies the data from the one instance that ran throughout the installation and configuration process to all of the newly started instances).

Choosing Configuration Values for Directory Server

For each Directory Server instance in your solution, you must input values that configure the instance to interoperate with the other components in the solution. For example, if your solution has multiple Directory Server instance, the configuration values must configure the Directory ServerDirectory Server instances to interoperate with each other. Use Table 3–5 to help you choose configuration values.

Table 3–5 Key Configuration Values for Directory Server Instances

Input Field 

Choosing a Value for Your Solution 

Administrator User ID and password 

You assign the ID and password for administrator account for the Directory Server instance. See Developing Your User Management Specifications

Directory Manager ID and Password 

You assign the password for the Directory Manager account. See Developing Your User Management Specifications

Server Identifier 

You assign the label that identifies the Directory Server instance in the Administration Server console. The default is the computer's hostname. The default value is usually the best choice. 

Server Port 

The port on which the Directory Server instance accepts connections from other components. Specified in your network connectivity diagram. For more information see Developing a Network Connectivity Specification.

Suffix 

The value you supply in this field 

establishes the base suffix, or root DN of the LDAP directory tree. This value is specified in the directory tree specification. See Specifying the Directory Tree Structure for a Solution

. 

Administration Domain 

The value you supply is used in the Administration Server console to group the components installed on the computer. The default value is the DNS domain of the computer on which you are installing. 

System User and System Group 

The Directory Server instance will run under this user ID and group. The default values are root and other.

Store User Data and Group Data on This Server, etc. 

Use these fields to define the function of the Directory Server instance. The default is for the Directory Server instance to serve as the directory for both user and group and configuration data, with the same URL for client connections. 

If your solution calls for separate directories for user and group data and configuration data, you can use these fields to indicate the function of the instance. 

  • To install an instance for configuration data only, select Store User and Group Data in the Following Instance, and specify another Directory Server instance. On the next page, select Store Configuration Data on This Server. Use the remaining fields to specify the URL the instances uses for client connections.

  • To install an instance for user and group data only, select Store User and Group Data on This Server. On the next page, select Store Configuration Data in the Following Instance, and supply the URL for the configuration data instance of Directory Server Use the remaining fields to specify the URL the instances uses for client connections.

Note –

The names used in this table for the configuration values are the names used in the Java ES installer. These are the names you see if you install Directory Server in configure now mode. If you install Directory Server in configure later or silent mode, you may need to use different names for these key configuration values.

Adding Installation Procedures for Directory Server to Your Installation Plan

To begin your installation plan, add installation and configuration instructions for Directory Server, as follows:

  1. If theDirectory Server instances are load balanced, the first step in your installation plan is confirming that the load balancer is functioning before anyJava ES software is installed.

  2. Next, in your plan, list all of the computers with Directory Server instances.

    1. For each computer, add an instruction to run the Java ES installer and select Directory Server.

    2. If other components are installed on the same computer system, you can add instructions to select all of the components at the same time, but your plan must put the instructions for configuring, starting, and verifying the Directory Server instances before the instructions for configuring or starting any instance of any other component. For example,

    3. If your solution uses multi-mastering replication, you must choose one of the Directory Server instances to be the master that runs while other components are installed and configured. List the computer with this instance first.

    4. If your deployment architecture has separate configuration—only Directory Server instances, list these first. Configuration-only instances must be installed and running before user and group instances are installed.

  3. Underneath each Directory Server instance in your plan, list the key values for configuring the instance.

  4. If the solution uses multi-mastering replication, add an instruction to shut down all but one of the Directory Server instances.