This chapter describes the information you need to provide to the Sun JavaTM Enterprise System (Java ES) installer for configuring components during installation.
This chapter contains the following sections:
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.
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 Installation Guide for UNIX for guidance on configuring these product components.
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 Installation Guide for UNIX.
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 and HP-UX: /var/opt/sun/install/logs
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 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:
Locate the section in this chapter that describes that product component.
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.
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.
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.
When you install product components using the Configure Now option, the installer presents pages that allow you to specify how some common settings are to be handled during install-time configuration:
In a state file created for silent install, the variables can specify sensitive data, such as administrator passwords. Make sure to protect the file as appropriate for your deployment.
For a Configure Now installation, the Password Choice page allows you to specify a single administrator account and password for all the product components that use the administrator settings.
Table 3–1 Password Choice
Common server settings are used to provide default values for the product components that use the settings.
On the configuration pages of the installer, the notation “Shared default value” indicates which setting are default values from the Common Server Settings page. You can accept the default value or you can override it by entering a value that is specific to the product component you are configuring.
Table 3–2 Common Server Settings
Label and State File Parameter |
Description |
---|---|
CMN_HOST_NAME |
The host name of the host on which you are installing Java ES components. Output of the hostname command. For example: thishost |
CMN_DOMAIN_NAME |
Domain for the host on which you are installing. Domain name of this computer as registered in the local DNS server. This format should be subdomain.domain.com. Example, example.com. |
Host IP Address |
The IP address of the host on which you are installing, that is, the local host. For example: 127.51.91.192 |
CMN_ADMIN_USER |
Default user ID for the administrator for all components being installed. For example: admin Note: If you chose to use a single administrator account, this field is not present. |
CMN_ADMIN_PASSWORD |
Default password for the administrator for all components being installed. There is no default value. The password must have at least eight character. Note: If you chose to use a single administrator account, this field is not present. Note: In the Java ES installer, white space cannot be used in admin passwords, nor can the following symbols: ; & ( ) ! | < > ' “ $ ^ \ # / , @ % |
CMN_SYSTEM_USER |
User ID (UID) under which component processes run. The default value is root. |
CMN_SYSTEM_GROUP |
Group ID (GID) of the system user. The default value is root. |
The Java ES installer supports the installation of these subcomponents of Access Manager:
Access Manager SDK is automatically installed as part of Identity Management and Policy Services Core, but the SDK can also be installed separately on a remote host. For information about separate installation of Access Manager SDK, refer to Access Manager SDK Configuration Information
The Identity Management and Policy Services Core subcomponent of Access Manager runs in a web container, usually Web Server or Application Server.
Access Manager can also run in a third-party web container, specifically IBM WebSphere Application Server or BEA WebLogic Server. After installing Access Manager with the Configure Later option, you then run the amconfig script to do postinstallation configuration. You must follow the IBM or BEA documentation to install and configure the third-party web container.
The information that the installer needs is different for each web container:
This section describes the information that the installer needs when Application Server is the web container for the Identity Management and Policy Services Core subcomponent of Access Manager.
Table 3–4 Access Manager With Application Server as Web Container
Label and State File Parameter |
Description |
---|---|
Secure Server Instance Port |
Port on which Application Server listens for connections to the instance. The default value is 8080. If you make a selection that does not correspond to the protocol set earlier for Application Server, an error is displayed. You must resolve the situation before continuing. |
Secure Administrator Server Port |
Port on which the administration server for Application Server listens for connections. The default value is 4849. |
Administrator User ID IS_IAS81_ADMIN |
User ID of the Application Server administrator. The default value is the administrator user ID you provided under Common Server settings. Note: If you chose to use a single administrator account, this field is not present. |
Administrator Password IS_IAS81_ADMINPASSWORD |
The default value is the administrator password you provided under Common Server settings. Note: If you chose to use a single administrator account, this field is not present. Note: In the Java ES installer, white space cannot be used in admin passwords, nor can the following symbols: ; & ( ) ! | < > ' “ $ ^ \ # / , @ % |
This section describes the information that the installer needs when Web Server is the web container for the Identity Management and Policy Services Core subcomponent of Access Manager.
Table 3–5 Access Manager With Web Server as Web Container
Label and State File Parameter |
Description |
---|---|
Host Name |
The fully qualified domain name for the host. For example, if this host is siroe.example.com, this value is siroe.example.com. The default value is the fully qualified domain name for the current host. |
IS_WS_ADMIN_ID |
User ID of the Web Server administrator. The default value is the administrator user ID you provided under Common Server settings. Note: If you chose to use a single administrator account, this field is not present. |
IS_WS_ADMIN_PASSWORD |
Password of the Web Server master administrator. The default value is the administrator password you provided under Common Server settings. Note: If you chose to use a single administrator account, this field is not present. Note: In the Java ES installer, white space cannot be used in admin passwords, nor can the following symbols: ; & ( ) ! | < > ' “ $ ^ \ # / , @ % |
IS_WS_DOC_DIR |
Directory where Web Server stores content documents. Solaris OS: /var/opt/SUNWwbsvr7/https-hostname.domain/docs Linux and HP-UX: /var/opt/sun/webserver7/https-hostname.domain/docs |
Web Server Port |
Port on which Web Server administration instance listens for HTTPS connections. If this port is in use, you are presented with a choice of available ports. Default value is 80. |
Web Server Instance Directory |
Path to the directory where an instance of Web Server is installed, using the following syntax: WebServer-base/https-webserver-instancename If you are installing Web Server in this session, the default value for WebServer-base is the Web Server instance directory: Solaris OS: /var/opt/SUNWwbsvr7 Linux and HP-UX: /var/opt/sun/webserver7 |
IS_WS_PROTOCOL |
Protocol specified for Web Server to listen on the Web Server port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default value is HTTP. |
The installer needs different information about Access Manager services for the following Access Manager subcomponents.
This section describes the services information that the installer needs when you are specifying web container details.
Table 3–6 Access Manager Services Information for Specifying Web Container
Label and State File Parameter |
Description |
---|---|
Host Name |
Fully qualified domain name of the host on which you are installing Java ES. The default value is the fully qualified domain name of the local host. |
Services Deployment URI |
Uniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and JAR files associated with the Identity Management and Policy Services Core subcomponent. This URI is used to access the realm (Access Manager 7.x compatible) console. The default value is amserver. Do not enter a leading slash. |
Common Domain Deployment URI |
URI prefix for accessing the common domain services on the web container. The default value is amcommon. Do not enter a leading slash. |
Cookie Domain |
The names of the trusted DNS domains that Access Manager returns to a browser when Access Manager grants a session ID to a user. You can scope this value to a single top-level domain, such as example.com . The session ID will provide authentication for all subdomains of example.com. Alternatively, you can scope the value to a comma-separated list of subdomains, such as .corp.example.com,.sales.example.com. The session ID will provide authentication for all subdomains in the list. A leading dot (.) is required for each domain in the list. The default value is the current domain, prefixed by a dot (.). |
Password Deployment URI |
URI that determines the mapping that the web container running Access Manager will use between a string you specify and a corresponding deployed application. This is the URI for the Access Manager password reset service. The default value is ampassword. Do not enter a leading slash. |
CONSOLE_PROTOCOL |
Protocol specified for Web Server to listen on the Web Server port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default value is HTTP. |
This section describes the services information the installer needs for the Access Manager console.
Table 3–7 Access Manager Services Information for Access Manager Console
This section describes the services information the installer needs when the following are both true:
You are installing only the Access Manager Administration Console subcomponent.
The Identity Management and Policy Services Core subcomponent is already installed on the same host.
You can only install AM Console by itself in Realm mode (Access Manager 7.x compatible). This cannot be done in Legacy mode (6.x compatible).
Label and State File Parameter |
Description |
---|---|
Console Deployment URI |
URI prefix for accessing the HTML pages, classes and JAR files associated with the Access Manager Legacy mode (Access Manager 6.x compatible) console. Only applies to Legacy mode. The default value is amconsole. If AM_REALM is enabled (setting Realm mode 7.x), then CONSOLE_DEPLOY_URI is ignored. |
Password Services Deployment URI |
URI that determines the mapping that the web container running Access Manager will use between a string you specify and a corresponding deployed application. This is the URI for the Access Manager password reset service. The default value is ampassword. Do not enter a leading slash. |
This section describes the services information the installer needs when the following are both true:
You are installing only the Access Manager Administration Console subcomponent.
The Identity Management and Policy Services Core subcomponent is not installed on the same host.
Label and State File Parameter |
Description |
---|---|
Web Container for Access Manager Administration Console |
|
Console Host Name |
Fully qualified domain name for the host on which you are installing. |
Console Deployment URI |
URI prefix for accessing the HTML pages, classes and JAR files associated with the Access Manager Legacy mode (Access Manager 6.x compatible) Console. Only applies to Legacy mode. The default value is amconsole. If AM_REALM is enabled (setting Realm mode 7.x), then CONSOLE_DEPLOY_URI is ignored. |
Password Services Deployment URI |
Deployment URI for the password service. The default value is ampassword. Do not enter a leading slash. |
Web Container for Access Manager Services |
|
Services Host Name |
Fully qualified domain name of the host where the Identity Management and Policy Services Core subcomponent is installed. The default value is the fully qualified domain name of this host. Use the default value as an example of format only, and edit the value to supply the correct remote host name. In a state file, supply the fully qualified domain name of a remote host. |
Port |
Port on which the Identity Management and Policy Services Core subcomponent listens for connections. This port is the HTTP or HTTPS port used by the web container. |
Services Deployment URI |
URI prefix for accessing the HTML pages, classes, and JAR files associated with the Identity Management and Policy Services Core subcomponent. This URI is used to access the realm (Access Manager 7.x compatible) console. The default value is amserver. Do not enter a leading slash. |
Cookie Domain |
The names of the trusted DNS domains that Access Manager returns to a browser when Access Manager grants a session ID to a user. You can scope this value to a single top-level domain, such as example.co m. The session ID will provide authentication for all subdomains of example.com. Alternatively, you can scope the value to a comma-separated list of subdomains, such as .corp.example.com. The session ID will provide authentication for all subdomains in the list. A leading dot (.) is required for each domain. The default value is the current domain, prefixed by a dot (.). |
This section describes the services information the installer needs when you are installing only the Common Domain Services for Federation Management subcomponent.
Table 3–10 Access Manager Services Information for Installing Federation Management (Core Already Installed)
Label and State File Parameter |
Description |
---|---|
Common Domain Deployment URI |
URI prefix for accessing the common domain services on the web container. The default value is amcommon. Do not enter a leading slash. |
The installer needs the following information if you are installing Identity Management and Policy Services Core.
Table 3–11 Directory Server Information for Access Manager
Label and State File Parameter |
Description |
---|---|
Directory Server Host |
A host name or value that resolves to the host on which Directory Server resides. The default value is the fully qualified domain name of the local host. For example, if the local host is siroe.example.com, the default value is siroe.example.com. |
Directory Server Port |
Port on which Directory Server listens for client connections. The default value is 389. |
Access Manager Directory Root Suffix |
Distinguished name (DN) to set as the Access Manager root suffix. The default value is based on the fully qualified domain name for this host, minus the host name. For example, if this host is siroe.subdomain.example.com, the value is dc=subdomain,dc=example,dc=com. |
Directory Manager DN IS_DIRMGRDN |
DN of the user who has unrestricted access to Directory Server. The default value is cn=Directory Manager. |
Directory Manager Password |
Password for the Directory Manager. |
The information needed to configure a provisioned directory depends on whether the installer detects an existing provisioned directory on your host. When the installer is generating a state file, IS_EXISTING_DIT_SCHEMA=y is written to the state file if the installer finds an existing provisioned directory. The installer writes IS_EXISTING_DIT_SCHEMA=n to the state file if the installer does not find an existing provisioned directory.
If the installer finds an existing provisioned directory, you provide the following information.
Table 3–12 Existing Provisioned Directory Information for Access Manager
Label and State File Parameter |
Description |
---|---|
User Naming Attribute IS_USER_NAMING_ATTR |
Naming attribute used for users in the provisioned directory. The default value is uid. |
If the installer does not find an existing provisioned directory, you can choose whether to use an existing provisioned directory. If you answer yes to the first question in this table, you must answer the remaining questions in the table.
Table 3–13 No Existing Provisioned Directory Information for Access Manager
Label and State File Parameter |
Description |
---|---|
Is Directory Server provisioned with user data? |
Specifies whether you want to use an existing provisioned directory. Permitted values are y or n. The default value is n. |
Organization Marker Object Class |
Object class defined for the organization in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is SunISManagedOrganization. |
Organization Naming Attribute |
Naming attribute used to define organizations in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is o. |
User Marker Object Class |
Object class defined for users in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is inetorgperson. |
User Naming Attribute |
Naming attribute used for users in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is uid. |
Access Manager SDK is automatically installed when you install Identity Management and Policy Services Core, a subcomponent of Access Manager. You can also install Access Manager SDK as a discrete product component on a host that is remote from the Access Manager core services.
Before you install Access Manager SDK, the Access Manager core services must be installed and running on a remote host. The web container information and Directory Server configuration information that you provide during this installation must match the web container and Directory Server configuration information that you provided during installation of Access Manager core services.
When the installer asks for information about the remote web container and Directory Server, default values are displayed based on the local host.
Do not accept the default values; use them only as examples of format. Instead, you must supply the correct remote information.
If you are installing Access Manager SDK as a discrete product component, you must provide the following types of information:
The installer needs the following administration information if you are installing only Access Manager SDK.
Table 3–14 Administration Information for Access Manager SDK
The installer needs the following Directory Server information if you are installing Access Manager SDK without other Access Manager subcomponents.
Table 3–15 Directory Server Information for Access Manager SDK
Label and State File Parameter |
Description |
---|---|
Directory Server Host |
A host name or value that resolves to the host on which Directory Server resides. Set this value to the same value used by Access Manager on the remote host. |
Directory Server Port |
Port on which Directory Server listens for client connections. Set this value to the same value used by Access Manager on the remote host. |
Access Manager Directory Root Suffix |
The distinguished name (DN) specified as the Access Manager root suffix when Directory Server was installed. This root suffix indicates the part of the directory that is managed by Access Manager. Set this value to the same value used by Access Manager on the remote host. The default value is based on the fully qualified domain name for this host, without the host name. For example, if this host is siroe.subdomain.example.com , the value is dc=subdomain,dc=example,dc=com. Use this default value as an example of format only. |
Directory Manager DN IS_DIRMGRDN |
DN of the user who has unrestricted access to Directory Server. Set this value to the same value used by Access Manager on the remote host. The default value is cn=Directory Manager. |
Directory Manager Password |
Password for the directory manager. Set this value to the same value used by Access Manager on the remote host. |
The information needed to configure a provisioned directory depends on whether the installer detects an existing provisioned directory on your host.
When the installer is generating a state file, IS_EXISTING_DIT_SCHEMA=y is written to the state file if the installer finds an existing provisioned directory. The installer writes IS_EXISTING_DIT_SCHEMA=n to the state file if the installer does not find an existing provisioned directory.
If the installer finds an existing provisioned directory, you provide the following information.
Table 3–16 Existing Provisioned Directory Information for Access Manager SDK
Label and State File Parameter |
Description |
---|---|
IS_USER_NAMING_ATTR |
Naming attribute used for users in the provisioned directory. The default value is uid. |
If the installer does not find an existing provisioned directory, you can choose whether to use an existing provisioned directory. If you answer yes to the first question in this table, you must answer the remaining questions in the table.
Table 3–17 No Existing Provisioned Directory Information for Access Manager SDK
Label and State File Parameter |
Description |
---|---|
Is Directory Server provisioned with user data? |
Specifies whether you want to use an existing provisioned directory. Permitted values are y or n. The default value is n. |
Organization Marker Object Class |
Object class defined for the organization in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is SunISManagedOrganization. |
Organization Naming Attribute |
Naming attribute used to define organizations in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is o. |
User Marker Object Class |
Object class defined for users in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is inetorgperson. |
User Naming Attribute |
Naming attribute used for users in the existing provisioned directory. This value is used only if the value for the first item in this table is y. The default value is uid. |
The installer needs the following web container information if you are installing only Access Manager SDK.
Table 3–18 Web Container Information for Access Manager SDK
Label and State File Parameter |
Description |
---|---|
IS_WS_HOST_NAME |
Host name of the web container that runs Access Manager core services. Use the value specified during the installation of Access Manager on the remote host. There is no default value. |
Services Deployment URI |
URI prefix for accessing the HTML pages, classes, and JAR files associated with Access Manager. Set this value to the same value used by Access Manager on the remote host. This URI is used to access the realm (Access Manager 7.x compatible) console. The default value is amserver. Do not enter a leading slash. |
Cookie Domain |
The names of the trusted DNS domains that Access Manager returns to a browser when Access Manager grants a session ID to a user. Set this value to the same value used by Access Manager on the remote host. The default value is the current domain, prefixed by a dot (.). |
IS_SERVER_HOST |
Host name where the web container that runs Access Manager core services is located. |
IS_SERVER_PORT |
Port number for the web container that runs Access Manager core services. |
IS_SERVER_PROTOCOL |
Protocol for listening on the Access Manager web container port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default value is HTTP. |
Services Port IS_WS_INSTANCE_PORT IS_IAS81INSTANCE_PORT |
Port number of the web container instance that runs Access Manager core services. Use the port number specified when Access Manager core services were installed. Web Server default value is 80. Application Server default value is 8080. |
The installer needs the following information for Application Server:
Label and State File Parameter |
Description |
---|---|
Admin Host Name |
Host name for domain administration which the node agent can connect to. The default value is the name of local host, including domain. |
Admin User Name |
User ID of the Application Server admin user. The default value is the Administrator User ID you provided under Common Server Settings. Note: If you chose to use a single administrator account, this field is not present. |
Password |
Password for the Application Server admin user. There is no default value. Note: If you chose to use a single administrator account, this field is not present. Note: White space cannot be used in admin passwords, nor can the following symbols: ; & ( ) ! | < > ' “ $ ^ \ # / , @ % |
Master Password |
SSL certificate database password, used for asadmin operations such as Domain Administration Server startup and Node Agent startup. The default value is the admin password you provided under Common Server Settings. |
Admin Port |
Port on which Application Server’s node agent listens for connections. Provides access to the administration tools. The default value is 4849. |
Node Agent Name |
Name of the local node. The default value is the local host name. |
Label and State File Parameter |
Description |
---|---|
Web server that the load balancing plugin will use |
Choice of Sun Java System Web Server or Apache Web Server. Note: HP-UX does not support Apache Web Server. The default value is Sun Java System Web Server. |
Web server installation directory |
Installation directory for Web Server or Apache HTTP Server. The default value is: Solaris OS: /opt/SUNWwbsvr7 Linux and HP-UX: /opt/sun/webserver7 |
CMN_WS_INSTANCE_DIR |
Instance directory for Web Server or Apache HTTP Server. The default value is: Solaris OS: /var/opt/SUNWwbsvr7 Linux and HP-UX: /var/opt/sun/webserver7 |
The installer needs the following information for Directory Server:
This page is displayed when you select Yes on the Directory Server Instance Choice Panel. If you select No, this page is not displayed. If another component requires a Directory Server instance, you will be prompted to either use the instance you can create on this page, or use a previously installed and configured instance of Directory Server.
Table 3–23 Instance Creation Information for Directory Server
Label and State File Parameter |
Description |
---|---|
DSEE_INSTANCE_DIRECTORY |
Location of new instance. The default value is: Solaris OS: /var/opt/SUNWdsee/dsins1 Linux and HP-UX: /var/opt/sun/dsins1 |
DSEE_INSTANCE_PORT |
Unsecure port for the new instance. The default value is 389. |
DSEE_INSTANCE_SSL_PORT |
Secure port for the new instance. The default value is 636. |
DSEE_DN_MANAGER |
Distinguished Name (DN) of the user who has unrestricted access to Directory Server. The default value is cn=Directory Manager. |
DSEE_INSTANCE_USER |
User ID under which the new instance runs. The default value is root. |
DSEE_INSTANCE_GROUP |
Group ID of the new instance. The default value is root. |
DSEE_INSTANCE_PASSWORD |
Password for the Directory Manager. The default value is the Administrator Password you provided under Common Server Settings. Minimum of 8 characters. |
Suffix |
Initial directory suffix managed by this instance. The default value is formed by the segments of the fully qualified domain name for the current host. For example, if you install on siroe.sub1.example.com , the default value is dc=sub1,dc=example,dc=com. |
The installer needs the following information for HADB.
Table 3–25 Port Selection Information for HADB
Label and State File Parameter |
Description |
---|---|
HADB_DEFAULT_ADMINPORT |
Port on which the HADB management listens. The default value is 1862. |
HADB_DEFAULT_RESDIR |
Location where HADB stores resource contents. The default value is /var/opt. |
HADB_DEFAULT_GROUP |
The UNIX group (GID) in which the default instance of HADB runs as a user. The default value is other. |
HADB_AUTO_START |
Choose this option to direct the installer to configure HADB to start automatically when the system restarts. The default value is yes. |
HADB_ALLOW_GROUPMANAGE |
Choose this option when you want HADB to be managed by the HADB Administration Group. If this parameter is set to yes, all members belonging to the group (HADB_DEFAULT_GROUP) can run and manage HADB. The default value is no. |
Portal Server requires a web container. Depending on what web container you choose, the configuration information in the following sections is required by the installer during installation:
This section describes the information that the installer needs when Application Server is the web container for Portal Server.
Table 3–27 Web Container Information for Portal Server with Application Server
Label and State File Parameter |
Description |
---|---|
Installation Directory |
Directory in which Application Server is installed. The default value is: Solaris OS: /opt/SUNWappserver/appserver Linux and HP-UX: /opt/sun/appserver |
Domain Name |
The Application Server domain to which the Portal Server is deployed. The default value is domain1. |
Server Instance Directory |
Path to the Application Server directory for the domain to which you want to deploy this Portal Server instance. The default value is: Solaris OS: /var/opt/SUNWappserver/domains/domain1 Linux and HP-UX: /var/opt/sun/appserver/domains/domain1 |
Server Instance Port |
Port on which Application Server listens for connections to the instance. The default value is 8080. |
Document Root Directory |
Name of the directory where static pages are kept. The default value is: Solaris OS: /var/opt/SUNWappserver/domains/domain1/docroot Linux and HP-UX: /var/opt/sun/appserver/domains/domain1/docroot |
Administration Port |
Port on which the Application Server administration instance is running, for the domain in which Portal Server is being installed. The default value is 4849. |
Administrator User ID |
User ID that Portal Server uses to access the Application Server as administrator. This is the Access Manager user ID and password. The default value is admin. |
Administrator Password |
Password that the Portal Server uses to access the Application Server as administrator. |
Secure Server Instance Protocol |
This protocol specifies whether the value for Server Instance port refers to a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. In a state file, specify https for a secure port or http for a non-secure port. The default value is http. |
Secure Administration Server Port |
This protocol specifies whether the value for Administration port is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. In a state file, specify https for a secure port or http for a non-secure port. The default value is https. |
This section describes the information that the installer needs when Web Server is the web container for Portal Server.
Table 3–28 Web Container Information for Portal Server With Web Server
Label and State File Parameter |
Description |
---|---|
Installation Directory |
Directory in which the Web Server is installed. The default value is: Solaris OS: /opt/SUNWwbsvr7 Linux and HP-UX: /opt/sun/webserver7 |
Administration Domain PS_DEPLOY_DOMAIN |
The Web Server domain to which the Portal Server is deployed. The default value is domain1. |
Instance Directory |
Directory in which the Web Server instance is installed. The default value is: Solaris OS: /var/opt/SUNWwbsvr7-hostname.domainname Linux and HP-UX: /var/opt/sun/webserver7-hostname.domainname |
Server Instance Port |
Port on which Web Server listens for HTTP connections. The default value is 8800. If you are installing Web Server in this installer session, the default value is the Web Server HTTP Port (WS_HTTP_PORT) value. |
Administration Host PS_DEPLOY_ADMIN_HOST |
Administration Server host name. |
Administration Port PS_DEPLOY_ADMIN_PORT |
Port on which the Web Server administration instance is running, for the domain in which Portal Server is being installed. The default value is 8989. |
Secure Server Admin Protocol |
This protocol specifies whether the port for the Web Server instance is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. In a state file, specify https for a secure port or http for a non-secure port. The default value is selected (https). |
This section describes the information the installer needs when BEA WebLogic is the web container for Portal Server.
BEA WebLogic is not supported as a web container on HP-UX.
Label and State File Parameter |
Description |
---|---|
Installation Directory |
Path to the directory where BEA WebLogic is installed. The default value is /usr/local/bea/weblogic81. |
Instance Directory |
Path to the directory where BEA WebLogic stores user projects. The default value is /usr/local/bea/user_projects/domains. |
JDK Home Directory PS_DEPLOY_JDK_DIR |
Path to the directory where the copy of JDK that BEA WebLogic uses is installed. The default value is /usr/local/bea/jdk142_05. |
Server / Cluster Port |
Number of the port where BEA WebLogic is deployed. The default value is 7001. |
Server / Cluster Protocol |
Specify whether the value for Server / Cluster Port is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default value is http. |
Administrator User ID |
User name of the BEA WebLogic administrator (system user). The default value is weblogic. |
Administrator Password |
Password of the BEA WebLogic administrator (system user). |
Administrator Host PS_DEPLOY_ADMIN_HOST |
Administrator server host name. Fully qualified domain name. For example, mycomputer.example.com. |
Administrator Port PS_DEPLOY_ADMIN_PORT |
Default value is 7001. |
Administrator Protocol PS_DEPLOY_ADMIN_PROTOCOL |
Specify whether the Administrator Port is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default value is http. |
Managed Server PS_DEPLOY_NOW |
Indicates if the BEA WebLogic Server is a managed server. In a state file, specify n for a managed server and y for a non-managed server. The default value is n. |
This section describes the information that the installer needs when IBM WebSphere Application Server is the web container for Portal Server.
IBM WebSphere is not supported as a web container on HP-UX.
Label and State File Parameter |
Description |
---|---|
Installation Directory |
Path to the directory where IBM WebSphere Application Server is installed. The default value is /opt/IBM/WebSphere/Express51/AppServer. |
Cell Name |
Name of the IBM WebSphere Application Server cell. The default value is DefaultNode. |
Node Name |
Name of the IBM WebSphere Application Server node. The default value is DefaultNode |
Server Instance |
Name of the IBM WebSphere Application Server instance. The default value is server1. |
Server Instance Port |
Port on which the IBM WebSphere application instance listens for HTTP connections. Typically, these are configured to come from a front end web server. The default value is 7080. |
Server Instance Protocol |
Specify whether the Server Instance Port is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. In a state file, specify https for a secure port or http for a non-secure port. The default value is http. |
Document Root Directory |
Directory where IBM WebSphere Application Server stores content documents. The default value is /opt/IBM/WebsSphere/Express51/Appserver/web/docs If you are using a language other than English, change the final part of the path name. |
JDK Home Directory PS_DEPLOY_JDK_DIR |
Path to the JDK installation that IBM WebSphere Application Server uses. The default value is /opt/IBM/WebsSphere/Express51/Appserver/java. |
Administrator User ID |
User name of the WebSphere administrator (system user). The default value is weblogic. |
Administrator Password |
Password of the WebSphere administrator (system user). |
PS_DEPLOY_ADMIN_HOST |
Administrator server host name. Fully qualified domain name. For example, mycomputer.example.com. |
PS_DEPLOY_ADMIN_PORT |
The default value is 7090. |
PS_DEPLOY_ADMIN_PROTOCOL |
Specify whether the Administrator Port is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default value is http. |
This section describes web container deployment information that the installer needs for Portal Server.
Table 3–31 Portal Server Web Container Deployment
Label and State File Parameter |
Description |
---|---|
PS_PORTALACCESS_URL |
Primary portal instance access URL, using the format http://hostname.domain:port/portal/dt.For example, http://mycomputer.example.com:8080/portal. Can be set to the load balancer URL except for Gateway/Rewriter/Netlet Proxy-only nodes, in which case, the portal access URL should be the primary portal instance URL and not the load balancer URL. |
PS_PORTAL_ID |
Unique identifier for the portal. The default value is portal1. |
PS_SEARCH_ID |
Unique identifier for the search instance within a portal. The default value is search1. |
Deployment URI |
Uniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and JAR files associated with Portal Server. The value must have a leading slash and must contain only one slash. Must be the same as the Portal Access URL, using the format http://hostname.domain:port/portal. The default value is /portal. |
PS_INSTANCE_ID |
Unique identifier for a portal instance within a portal, using format hostname-port. For example, mycomputer-8080. |
SRA_SWITCH_CORE |
If you set this parameter to Enabled, the installer prompts you for the Portal Server Secure Remote Access gateway information. The default value is Disabled. |
PS_DEVELOPER_PORTAL |
Select whether to configure this sample that contains features of interest to developers. The default value is selected. |
PS_ENTERPRISE_PORTAL |
Select whether to configure this sample that contains features within a business portal. The default value is selected. |
PS_COMMUNITY_PORTAL |
Select whether to configure this sample that contains features for collaboration and community. The default value is selected. |
This section first describes the configuration information needed for installing the subcomponents of Portal Server Secure Remote Access.
Portal Server Secure Remote Access Netlet Proxy Configuration
Portal Server Secure Remote Access Rewriter Proxy Configuration
When you install Portal Server, Portal Server Secure Remote Access Core is installed. If you have enabled the Enable Secure Remote Access (default value is Disabled), installer prompts you for the information in the following table.
Table 3–32 Portal Server Secure Remote Access Information
Label and State File Parameter |
Description |
---|---|
SRA_GATEWAY_PROTOCOL |
Protocol that the gateway uses to communicate with Portal Server. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. In a state file, specify https for a secure port or http for a non-secure port. The default value is https. |
SRA_SERVER_DOMAIN |
Name of the domain where Portal Server is installed. The default value is the domain name of the host. For example, if the fully qualified domain name is siroe.subdomain1.example.com, enter subdomain1.example.com. |
SRA_GATEWAY_DOMAIN |
Name of domain where gateway is installed. The default value is the default domain of the host. For example, if the fully qualified domain name of the gateway host is siroe.subdomain1.example.com, enter subdomain1.example.com . |
Gateway Port SRA_GATEWAY_PORT |
Port on which the gateway host listens. The default value is 443. |
Gateway Profile Name |
Profile that contains gateway configuration information, such as listener port, SSL options, and proxy options. The default value is default. |
Log User Password |
Password that allows administrators with non-root access to access gateway log files. |
This section describes the gateway information that the installer needs when you are installing the Gateway subcomponent.
Table 3–33 Gateway Information for Portal Server Secure Remote Access Gateway
Label and State File Parameter |
Description |
---|---|
Protocol |
Protocol (HTTP or HTTPS) the gateway uses to communicate. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. In most cases the gateway should use HTTPS. In a state file, specify https for a secure port or http for a non-secure port. The default value is https. |
Host Name |
Name of the host on which the gateway subcomponent is installed. For example, if the fully qualified domain name is siroe.subdomain1.example.com , the host name is siroe. The default value is the name of the local host. |
Subdomain |
Subdomain name of the gateway host. There is no default value. |
Domain |
Domain name of the gateway host. For example, if the fully qualified domain name is siroe.example.com , this value is example.com. The default value is the domain of the local host. |
Host IP Address |
IP address of the Access Manager host. Specify the IP address of the host on which Access Manager was installed for Portal Server. The default value is the IP address of the local host. |
Access Port |
Port on which the gateway host listens. The default value is 443. |
Gateway Profile Name |
Gateway profile that contains the information related to gateway configuration, such the port on which gateway listens, SSL options, and proxy options. The default value is default. |
This section describes the Netlet Proxy information that the installer needs when you are installing Netlet Proxy.
Table 3–34 Netlet Proxy Information for Portal Server Secure Remote Access Netlet Proxy
Label and State File Parameter |
Description |
---|---|
Host Name |
Name of the host on which the Netlet Proxy subcomponent is installed. For example, if the fully qualified domain name is siroe.subdomain1.example.com , the host name is siroe. The default value is the name of the local host. |
Subdomain |
Name of the subdomain where Netlet Proxy is installed There is no default value. |
Domain |
Name of the domain where Netlet Proxy is installed. The default value is the domain of the local host. |
Host IP Address |
IP address of the host where Netlet Proxy is installed. The default value is the IP address of the local host. |
Access Port |
Port on which Netlet Proxy listens. The default value is 10555. |
Gateway Profile Name |
Profile that contains gateway configuration information, such as listener port, SSL options, and proxy options. The default value is default. |
This section describes the Rewriter Proxy information that the installer needs when you are installing Rewriter Proxy.
Table 3–35 Rewriter Proxy Information for Portal Server Secure Remote Access Rewriter Proxy
Label and State File Parameter |
Description |
---|---|
Host Name |
Name of the host on which the Rewriter Proxy subcomponent is installed. For example, if the fully qualified domain name is siroe.subdomain1.example.com, the host name is siroe. The default value is the name of the local host. |
Subdomain |
Name of the subdomain name where Rewriter Proxy is being installed. There is no default value. |
Domain |
Name of the domain where Rewriter Proxy is being installed. The default value is the domain name of the local host. |
Host IP Address |
IP address of the host on which you are installing Rewriter Proxy. The default value is the IP address of the local host. |
Access Port |
Port on which the Rewriter proxy listens. The default value is 10443. |
Gateway Profile Name |
Profile that contains gateway configuration information, such as listener port, SSL options, and proxy options. The default value is default. |
When you are installing Gateway, Netlet Proxy, or Rewriter Proxy, you can provide information to create a self-signed certificate for use with Portal Server, Secure Remote Access. The installer needs the following information to configure a certificate.
Do not use multibyte characters when providing certificate information.
Label and State File Parameter |
Description |
---|---|
Organization |
Name of your organization or company. |
Division |
Name of your division. |
City/Locality |
Name of your city or locality. |
State/Province |
Name of your state or province. |
Country Code |
Two-letter country code. |
Certificate Database Password |
Password (and confirmation) that applies only to self-signed certificates. |
Label and State File Parameter |
Description |
---|---|
WPS_ADMIN_USER |
User ID of the Web Proxy Server administrator. The default value is admin or the value you provided under Common Server Settings. Note: If you chose to use a single administrator account, this field is not present. |
WPS_ADMIN_PASSWORD |
The password of the Web Proxy Server administrator. The default value is the password you provided under Common Server Settings. Note: If you chose to use a single administrator account, this field is not present. Note: In the Java ES installer, white space cannot be used in admin passwords, nor can the following symbols: ; & ( ) ! | < > ' “ $ ^ \ # / , @ % |
WPS_PROXY_DOMAIN |
A host and domain value that resolves to the local host. The default value is created by joining the values that you provided for Host Name and for DNS Domain Name under Common Server Settings. For example: hostname.domain |
WPS_ADMIN_PORT |
Port on which the Web Proxy Server administration server listens for connections. The default value is 8888. |
WPS_ADMIN_RUNTIME_USER |
The Web Proxy Server administration server runs on the system as this user (UID). Use the name rather than the user ID number. The default value is the value you provided for System Users under Common Server Settings. |
WPS_INSTANCE_RUNTIME_USER |
An existing non–root user. Note: On HP-UX, ensure that nobody is a valid user. The default value is nobody. |
WPS_INSTANCE_PORT |
Port on which Web Proxy Server listens for connections. The default value is 8080. |
WPS_INSTANCE_AUTO_START |
Used to automatically start the Web Proxy Server instance. Choose this parameter when Web Proxy Server needs to be started at a reboot. Values can be y or n. The default value is n. |
The installer needs the following information for Web Server:
The Web Server Admin Server runs on two ports: SSL (default 8989) and non-SSL (default 8800). If you choose HTTP, then the PS_DEPLOY_ADMIN_PORT parameter must be changed to refer to a non-SSL admin port. Default non-SSL admin port is 8800.
Table 3–39 Administration Server Settings for Web Server
Label and State File Parameter |
Description |
---|---|
WS_LOGIN_USER |
User ID of the Web Server administrator. The default value is admin or the value you provided under Common Server Settings. Note: If you chose to use a single administrator account, this field is not present. |
WS_LOGIN_PASSWORD |
The password of the Web Server administrator. The default value is the value you provided under Common Server Settings. Note: If you chose to use a single administrator account, this field is not present. Note: In the Java ES installer, white space cannot be used in admin passwords, nor can the following symbols: ; & ( ) ! | < > ' “ $ ^ \ # / , @ % |
WS_ADMIN_HOST |
A host and domain value that resolves to the local host. This value is used to create a directory under server root for the first Web Server instance. The default value is automatically created by joining the values that you provided for Host Name and DNS Domain Name under Common Server Settings. The value has the format hostname.domainname. |
WS_ADMIN_SSL_PORT |
Port that is used to run the Administration Server in secure mode. Must be a valid SSL port. if this port is selected, you must specify HTTPS when invoking a URL. The default value is 8989. |
WS_ADMIN_HTTP_PORT |
Port on which Web Server listens for HTTP connections. The default value is 8800. |
WS_ADMIN_SERVER_USER |
The default value is root or the value you provided under Common Server Settings. Note: If you chose to use a single administrator account, this field is not present. |
Label and State File Parameter |
Description |
---|---|
WS_SERVER_NAME |
A host and domain value that resolves to the local host. This value is used to create a directory under server root for the first Web Server instance. The default value is automatically created by joining the values that you provided for Host Name and DNS Domain Name under Common Server Settings. The value has the format hostname.domainname. |
WS_HTTP_PORT |
Port on which Web Server instance listens for HTTP connections. The default value is 80. |
Runtime UNIX User ID |
An existing non–root user. If you are installing Access Manager or Portal Server, set this value to root and set the Runtime Group to other (on HP-UX, set to sys). You can change these values after installation. For other servers, the Runtime User ID should be a non-root user. Note: If you are using Web Server as the web container, the Web Server runtime instance value must be set to root. The default value is webservd |
WS_DOCROOT |
Location where Web Server stores content documents. To use a non-default value, ensure that the directory that you specify is already present in the file system. The installer does not create the directory for you. The default value is: Solaris OS: /var/opt/SUNWwbsvr7/https-hostname.domain/docs Linux and HP-UX: /var/opt/sun/webserver7/https-hostname.domain/docs |
The following table contains information on state file parameters that are not associated with product component configuration. Parameter names are listed alphabetically.
Table 3–42 State File Parameters
Parameter Name |
Description |
---|---|
INCOMPATIBLE_JDK |
Specifies whether to upgrade the JDK if it is found on the host and is incompatible with the JDK distributed by Java ES. The value can be yes or no. This parameter is case sensitive. The default value is no. |
Defines the configuration type. Permitted values are Custom, meaning configure during installation (Configure Now), and Skip (meaning configure after installation (Configure Later). The default value is Custom. Important: Do not set this value in the state file. Specify this value only when you are running the installer to generate a state file. Configuration type affects the installer processing logic in many ways, and errors could result if you change the value after the state file is generated. |
|
Specifies the web container type for Access Manager. Permitted values are WebServer and AppServer. The default value is AppServer (Application Server). |
|
Specifies the web container type for Portal Server. Permitted values are IWS, SUNONE8, WEBLOGIC, WEBSPHERE. |
|
Specifies whether or not language packages are to be installed in addition to English. Values are True or False. This option is presented with component selection. If True is indicated, multilingual packages for all selected components will be installed. If False, no locale packages will be installed. The default value is False. |
|
The permitted values are Evaluation and Deployment, but this field is not used. |
|
Instructs the installer to exit if dependencies of the selected product components are not met. Warnings generally identify dependencies that could be met with remote components that can be specified during configuration. Specify Yes to exit the installation on a dependency warning or specify No to proceed despite the warning. The default value is No. This parameter is not case sensitive. |
|
Causes the installer to write a list of currently installed products to the log file. This option is the equivalent of the View Currently Installed button on the Component Selection page of the graphical installer. Permitted values are Yes and No. This parameter is not case sensitive. The default value is Yes. |
|
A comma-separated list of product components and subcomponents you want to install. The default value is All. |