How to Use This Chapter

This chapter provides configuration information for the product components that can be configured during installation (Configure Now). Use this chapter in conjunction with the worksheets in Chapter 4, Configuration Worksheets.

For a Configure Later Installation

If you select the Configure Later installation type, little is required during installation.

The following components cannot be configured by the Java ES installer and, therefore, must be configured after installation: Directory Proxy Server, Java DB, Monitoring Console, Service Registry, and Sun Cluster components.

After installation, refer to Chapter 6, Completing Postinstallation Configuration, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX for guidance on configuring these product components.

For a Configure Now Installation

In a Configure Now installation, the Java ES installer displays configuration pages for the selected components that are configurable during installation. You can accept default information or enter alternate information. If you specify alternates, you are responsible for consistently pointing components to that directory or port during configuration. The default common server settings for a Configure Now installation are contained in Common Settings. You can also use individual component configurators to make additional changes.

To complete the postinstallation configuration for components that can be configured during installation, you will most likely use the tables and worksheets in this manual in addition to the instructions in Chapter 6, Completing Postinstallation Configuration, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Configuration Information Provided by the Installer

At the end of an installation session, a summary file contains the configuration values that are set during installation. You can view this file from the final page of the installer, or from the directory where the file is saved:

Solaris OS: /var/sadm/install/logsLinux: /var/opt/sun/install/logs

Using the Configure Now Configuration Tables

The tables in this chapter have two columns: Label and State File Parameter, and Description. The Label and State File Parameter column contains the following information:

• Label. This is the text that identifies information in the pages of the interactive graphical installer, usually a label on an input field. The text-based installer uses similar terminology.

• State File Parameter. A state file parameter is the key that identifies the information in a silent installation state file. State file parameters are uppercase and appear in monospace font. For example, AS_ADMIN_USER_NAME.

A good way to see how the parameters are used is to examine the example state file in Appendix C, Example State File, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

The Description column describes the parameter listed in the Label and State File Parameter column. If a default applies to the parameter, the default value is listed. Default values apply to all installer modes, unless the description provides a separate value for a silent mode state file. State file values are case sensitive except where noted. Other information is provided as it applies to that parameter, such as examples, paths, or notes explaining anything you need to be aware of about that parameter.

If you are using this chapter as an aid for answering configuration questions posed by the installer during a Configure Now installation, do the following:

1. Locate the section in this chapter that describes that product component.

2. Find the table whose content matches the installer page being displayed. A table contains all the fields and questions contained on a single page of the installer.

3. If you are using this chapter to get information about parameters in a state file, do the following:

   • If you are using the guide online, use the HTML or PDF search feature to find the parameter string.

   • If you are using a printed book, refer to the index. The index contains an entry for each parameter name, either under the parameter name itself, or under the State File Parameters entry.

Configuration Terminology

During installation and configuration, you are prompted for values relating to various types of domains, organizations, and related configuration information.

• Domain Name System (DNS). The Domain Name System (DNS) is a distributed internet directory service. DNS is used mostly to translate between domain names and IP addresses, and to control email delivery.

• DNS Domain Name. A DNS domain name identifies a group of servers on a network. Examples of domain names: example.com, red.example.com

• Fully Qualified Domain Name (FQDN). An FQDN is the human-readable name corresponding to the TCP/IP address of a network interface, as found on a server, router, or other networked device. An FQDN for a server includes both its host name and its domain name. Example of a FQDN for a server: myComputer.example.com

• Host Name. The host name is a unique name by which a server is known on a network. A host name can be represented as the combination of a server's local name with its organization's domain name. This representation is also the FQDN for the server. Within the context of a domain, a host name can be represented solely by its local name. This is because the local name must be unique within the domain. Examples of host names:

  • FQDN representation: myComputer.red.example.com

  • Local name representation which is unique within red.example.com domain: myComputer

• Configuration Directory. An instance of Directory Server that stores configuration information for various administration domains. The administration server accesses the configuration directory when administering these domains. The base suffix of the subtree that holds configuration information is always o=NetscapeRoot.

• User/Group Directory. An instance of Directory Server that stores information about organizations in an LDAP hierarchy. Typically, organizations are represented by their DNS domain names in the LDAP hierarchy. Each organization in the hierarchy might contain entries representing people, organizational units, printers, documents, and so on.

• Administration Domain. A set of servers represented in a Directory Server configuration directory server and administered through the Sun Java System Server Console. Typically, an administration domain is represented in the LDAP hierarchy with its DNS domain name, but you can use any name to represent the group of servers that make up the administration domain.

• Email Domain. A unique domain in DNS that is used for routing email. An email domain for an organization can be its DNS domain name, but can also be another domain used to route email. For example: DNS Domain: example.com Email Domain: sfbay.example.com (In Sun's LDAP Schema 2, the email domain is represented in the User/Group directory as an attribute of an organization.)

• Authentication Domain. In Access Manager, circle of trust is implemented as an authentication domain. An authentication domain is not a DNS domain. In Access Manager, an authentication domain describes entities that are grouped together for the purposes of identity federation.

• Organization DN. The unique name of an organization in the LDAP hierarchy of a User/Group directory. Typically, organizations are represented by their DNS domain names in the LDAP hierarchy by using the o, ou, or dc LDAP attributes. An organization can contain sub-organizations.

• Directory Manager. The privileged Directory Server administrator, comparable to the root user in UNIX. The default Directory Manager DN is cn=Directory Manager but can be changed. During installation and configuration, you must supply the Directory Manager DN and password to make changes to the LDAP configuration.