Sun Java Enterprise System 2005Q4 Installation Planning Guide

Administration Server

Administration Server provides administrative support for Directory Server, Directory Proxy Server, and Messaging Server.

Administration Server has a solution-level dependency on Directory Server. Administration Server stores configuration data in the LDAP directory. If your solution uses separate Directory Server instances for user and group data and configuration data, you specify the Directory Server instance designated for configuration data. Therefore, it is logical to install and configureAdministration Server immediately after Directory Server.

Note –

If your solution uses Directory Server Console, you must plan to install Administration Server when Directory Server is installed.

Basic Installation Procedures for Administration Server

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

  1. Install and configure Administration Server on the computer systems specified in your deployment architecture. When you install Administration Server, you specify the Directory Server instance where Administration Server configuration data will be stored.

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

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

Choosing Configuration Values for Administration Server

For each Administration Server instance in your solution, you must input values that configure the instance to interoperate with the other components in the solution. Specifically, you identify the Directory Server instance where Administration Server stores its configuration data. UseTable 3–6 to help you choose configuration values.

Table 3–6 Key Configuration Values for Administration Server

Input Field 

Choosing a Value for Your Solution 

Server Root 

The pathname under which Administration Server is installed. 

Administration Port 

The port at which the Administration Server accepts connections. 

Administration Domain 

The label used in the administration console to group the component instances administered by the Administration Server instance. 

System User and System Group 

The user ID and group under which the Administration Server instance runs. This user ID and group you specify here must match the user ID and group for the component instances administered by Administration Server. For example, if you are installing Administration Server to mange a specific Directory Server instance, the Administration Server user and group must match the Directory Server user and group. 

Administration User ID and Password 

Establishes the administrator account and password used to log in to the administration console. 

Directory Server Host and Directory Server Port 

Specifies the Directory Server instance where Administration Server stores configuration data for the component instances in the administration domain. 

Adding Procedures for Administration Server to Your Installation Plan

To add installation and configuration instructions for Administration Server, do the following:

  1. If theAdministration Server instances are load balanced, the first instruction 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 Administration Server instances. For each computer, write Administration Server. Underneath Administration Server, add an instruction to run the Java ES installer and select Administration Server.

  3. Underneath each heading for an Administration Server instance, list the key values for configuring the instance. Use Table 3–6 to help you select configuration values.

  4. Following the configuration values, add an instruction to start and verify the Administration Server instance.

  5. If the Administration Server instances are load balanced, add an instruction to verify operation of the load balancer.