Sun Java Enterprise System 2005Q1 Installation Guide |
Chapter 4
Configuration InformationThis chapter describes the information you need to provide to the Sun Java Enterprise System (Java ES) installer for configuring components during a Configure Now installation. This information includes common server settings and component-specific information for those components that can be configured during installation.
Use this chapter in conjunction with the worksheets in Chapter 5, "Configuration Worksheets" to prepare for Java ES installation.
This chapter contains the following sections:
How to Use This ChapterFor the Configure Now option, 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 use the Configure Later option, little is required during installation beyond being aware of common server settings and how port settings work. For information on installation directories and port assignments, refer to Appendix B, "Default Installation Directories" or Appendix C, "Default Port Numbers"
The component-specific tables in this chapter are grouped in the same way the configuration pages are grouped in the graphical installer: first by component, and then by type of information. The configuration information tables have two columns: “Label and State File Parameter,” and “Description.” The “Label and State File Parameter” column contains the following information:
- Label. The text that identifies information in the graphical installer. This is usually a label on an input field.
- State File Parameter. The key that identifies the information in a silent installation state file. State file parameters are uppercase and appear in monospace font.
Tip
A good way to see how the parameters are used is to examine the example state file in Appendix E, "Example State File".
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 installer, or from the directory where the file is saved:
Solaris OS: /var/sadm/install/logs
Linux: /var/opt/sun/install/logsDefault Values
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.
Suggested Look-up Strategies
If you are using this chapter to get information to answer configuration questions posed by the installer, do the following:
If you are using this chapter to get information about parameters in a state file, do the following:
Common Server SettingsWhen you install components using the Configure Now option, the installer displays a set of common server settings that is used to provide default values for the components that use the settings.
On the configuration pages of the installer, the notation “*Shared Default Value” indicates which settings 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 component you are configuring.
The following table lists the default values for the common server settings.
Access Manager Configuration InformationThe Java ES installer supports the installation of these subcomponents of Access Manager:
- Identity Management and Policy Services Core
- Access Manager Administration Console
- Common Domain Services for Federation Management
- Access Manager SDK
Note
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 and Access Manager SDK With Container Configuration Example.
The installer needs different information depending on which subcomponents you are installing, as the following table indicates. The table also refers you to the tables where the relevant information is described.
Table 4-2 Information Needed to Install Subcomponents of Access Manager
When You Are Installing...
The Installer Needs...
Refer to...
Identity Management and Policy Services Core
Web container information
Directory Server information
Provisioned directory information
Table 4-11
and Table 4-12Common Domain Services for Federation Management
Services information
Installing Access Manager Federation Management (Core Already Installed)
Access Manager Administration Console
Administration information
Services information
Access Manager: Administration Information
The installer needs the following information if you are installing Access Manager Administration Console.
Table 4-3 Administration Information for Access Manager
Label and State File Parameter
Description
Administrator User ID
IS_ADMIN_USER_IDAccess Manager top-level administrator. This user has unlimited access to all entries managed by Access Manager.
The default name, amadmin, cannot be changed. This ensures that the Access Manager administrator role and its privileges are created and mapped properly in Directory Server, allowing you to log onto Access Manager immediately after installation.
Administrator Password
IS_ADMINPASSWDPassword of the amadmin user. The value must have at least eight characters.
The default value is the Administrator Password (CMN_ADMIN_PASSWORD) you provided under Common Server Settings. Refer to Table 4-1.
LDAP User ID
IS_LDAP_USERBind DN user for LDAP, Membership, and Policy services. This user has read and search access to all Directory Server entries.
The default user name, amldapuser, cannot be changed.
LDAP Password
IS_LDAPUSERPASSWDPassword of the amldapuser user. This password must be different from the password of the amadmin user. It can be any valid Directory Service password.
Password Encryption Key
AM_ENC_PWDA string that Access Manager uses to encrypt user passwords.
The interactive installer generates a default password encryption key. You can accept the default value or specify any key produced by a J2EE random number generator. During Access Manager installation, its property file is updated and the property am.encryption.pwd is set to this value. The property file is AMConfig.properties. Location is:
Solaris OS: /etc/opt/SUNWam/config
Linux: /etc/opt/sun/identity/configAll Access Manager subcomponents must use the same encryption key that the Identity Management and Policy Services Core uses. If you are distributing Access Manager subcomponents across hosts and installing Administration Console or Common Domain Services for Federation Management, copy the value for am.encryption.pwd as generated by the installation of the core, and paste the value into this field.
In a state file, the default is LOCK. Any character combination is permitted.
Access Manager: Web Container Information
The Identity Management and Policy Services Core subcomponent of Access Manager runs in Web Server or Application Server. The information that the installer needs is different for each web container:
- For Web Server, see Web Container Information: Access Manager with Web Server
- For Application Server, see Web Container Information: Access Manager with Application Server
Web Container Information: Access Manager with Web Server
Table 4-4 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 4-4 Web Container Information for Access Manager with Web Server
Label and State File Parameter
Description
Host Name
IS_WS_HOST_NAMEThe 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.
Web Server Port
IS_WS_INSTANCE_PORTPort on which Web Server listens for HTTP connections.
The default value is 80.
If you are installing Web Server in this installer session, the default value is the Web Server HTTP Port (WS_ADMIN_PORT) value. Refer to Table 4-57.
Web Server Instance Directory
IS_WS_INSTANCE_DIRPath to the directory where an instance of Web Server is installed. The path must have the following syntax:
WebServer-base/https-web-server-instance-name
If you are installing Web Server in this session, the default value for WebServer-base is the Web Server installation directory:
Solaris OS: /opt/SUNWwbsvr
Linux: /opt/sun/webserverDocument Root Directory
IS_WS_DOC_DIRDirectory where Web Server stores content documents.
If you are installing Web Server in this installer session, the default value is the Web Server value Document Root Directory (WS_INSTANCE_CONTENT_ROOT). Refer to Table 4-57.
If you are not installing Web Server, the default location is WebServer-base/docs.
The default value for WebServer-base is the Web Server installation directory:
Solaris OS: /opt/SUNWwbsvr
Linux: /opt/sun/webserverSecure Server Instance Port
IS_SERVER_PROTOCOLSpecify 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 http.
Web Container Information: Access Manager with Application Server
Table 4-5 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 4-5 Web Container Information for Access Manager with Application Server
Label and State File Parameter
Description
Installation Directory
IS_APPSERVERBASEDIRPath to the directory where Application Server is installed.
If you are installing Application Server, this value defaults to the value you specified for the Application Server installation directory. The default value is:
Solaris OS: /opt/SUNWappserver/appserver
Linux: /opt/sun/appserverAccess Manager Runtime Instance
IS_IAS81INSTANCEName of the Application Server instance that will run Access Manager.
The default value is server.
Instance Directory
IS_IAS81INSTANCEDIRPath to the directory where Application Server stores files for the instance. Default value:
Solaris OS: /var/opt/SUNWappserver/domains
Linux: /var/opt/sun/appserver/domainsAccess Manager Instance Port
IS_IAS81INSTANCE_PORTPort on which Application Server listens for connections to the instance.
The default value is 8080.
Document Root
IS_SUNAPPSERVER_DOCS_DIRDirectory where Application Server stores content documents.
The default document root is the instance directory specified by IS_IAS81INSTANCEDIR, with domainname/docroot appended at the end. For example: IS_IAS81INSTANCEDIR/domainname/docroot
Administrator User ID
IS_IAS81_ADMINUser ID of the Application Server administrator.
The default value is the Administrator User ID you provided under Common Server Settings. Refer to Table 4-1.
Administrator Password
IS_IAS81_ADMINPASSWDPassword of the Application Server administrator.
The default value is the Administrator User password you provided under Common Server Settings. Refer to Table 4-1.
Administrator Port
IS_IAS81_ADMINPORTPort on which the Administration Server for Application Server listens for connections.
The default value is 4849.
Secure Server Instance Port
IS_SERVER_PROTOCOLSpecify whether the value for Instance Port (IS_IAS81INSTANCE_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
ASADMIN_PROTOCOLSpecify whether the value for Administrator Port (IS_IAS81_ADMINPORT) 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.
Access Manager: Services Information
The installer needs different information about Access Manager services for different Access Manager subcomponents.
Installing Access Manager Core and Console
Table 4-6 describes the services information that the installer needs when you are installing the Identity Management and Policy Services Core and the Access Manager Administration Console subcomponents.
In this scenario, you can deploy a new console or use a previously deployed console. If you deploy a new console, some information in Table 4-6 is not needed, as the Description column indicates.
Table 4-6 Access Manager Services Information for Installing Core and Console
Label and State File Parameter
Description
Host Name
IS_SERVER_HOSTFully qualified domain name of the host on which you are installing.
The default value is the fully qualified domain name of the local host.
Services Deployment URI
SERVER_DEPLOY_URIUniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and JAR files associated with the Identity Management and Policy Services Core subcomponent.
The default value is amserver. Do not enter a leading slash.
Common Domain Deployment URI
CDS_DEPLOY_URIURI prefix for accessing the common domain services on the web container.
The default value is amcommon. Do not enter a leading slash.
Cookie Domain
COOKIE_DOMAIN_LISTThe 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 (.).
Administration Console:
Deploy new console and
Use existing console
USE_DSAME_SERVICES_WEB
_CONTAINERChoose Deploy new console to deploy the console into the web container of the host on which Access Manager is being installed. Choose Use existing console to use an existing console that is deployed on another host.
In both cases, you specify the Console Deployment URI and Password Deployment URI. If you choose to use an existing console, you must also specify the Console Host Name and Console Port.
In a state file, specify true to deploy a new console or false to use an existing console.
Console Deployment URI
CONSOLE_DEPLOY_URIURI prefix for accessing the HTML pages, classes and JAR files associated with the Access Manager Administration Console subcomponent.
The default value is amconsole. Do not enter a leading slash.
Password Deployment URI
PASSWORD_SERVICE_DEPLOY_URIURI that determines the mapping that the web container running Access Manager will use between a string you specify and a corresponding deployed application.
The default value is ampassword. Do not enter a leading slash.
Console Host Name
CONSOLE_HOSTFully qualified domain name for the server hosting the existing console.
This value is not needed if you are deploying a new console. In graphical installation mode, you can edit the field only if you are using an existing console.
The default value contains the value that you provided for Host (IS_SERVER_HOST), a dot, and then the value that you provided for DNS Name in the Common Server Settings. Refer to Table 4-1.
As an example, if the host is siroe and the domain is example.com, the default value is siroe.example.com.
Console Port
CONSOLE_PORTPort on which the existing console listens for connections. Permitted values are any valid and unused port number, in the range 0 (zero) through 65535.
This value is not needed if you are deploying a new console. In graphical installation mode, you can edit the field only if you are using an existing console.
The default value is the value you provided for one of the following web container ports:
Installing Access Manager Console (Core Already Installed)
Table 4-7 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.
Installing Access Manager Console (Core Not Already Installed)
Table 4-8 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.
Installing Access Manager Federation Management (Core Already Installed)
Table 4-9 describes the services information the installer needs when you are installing only the Common Domain Services for Federation Management subcomponent.
Access Manager: Directory Server Information
The installer needs the following information if you are installing Identity Management and Policy Services Core.
Access Manager: Provisioned Directory Information
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.
Existing Provisioned Directory Found
If the installer finds an existing provisioned directory, you provide the following information.
No Existing Provisioned Directory Found
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.
Access Manager SDK Configuration InformationAccess 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 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.
If you are installing Access Manager SDK as a discrete component, you must provide the following types of information:
Access Manager SDK: Administration Information
The installer needs the following administration information if you are installing only Access Manager SDK.
Table 4-13 Administration Information for Access Manager SDK
Label and State File Parameter
Description
Administrator User ID
IS_ADMIN_USER_IDAccess Manager top-level administrator. This user has unlimited access to all entries managed by Access Manager.
The default name, amadmin, cannot be changed. This ensures that the Access Manager administrator role and its privileges are created and mapped properly in Directory Server, allowing you to log onto Access Manager immediately after installation.
Administrator Password
IS_ADMINPASSWDPassword of the amadmin user. The value must have at least eight characters.
Set this value to the same value used by Access Manager on the remote host.
The default value is the Administrator Password (CMN_ADMIN_PASSWORD) you provided under Common Server Settings. Refer to Table 4-1.
LDAP User ID
IS_LDAP_USERBind DN user for LDAP, Membership, and Policy services. This user has read and search access to all Directory Server entries.
The default user name, amldapuser, cannot be changed.
LDAP Password
IS_LDAPUSERPASSWDPassword of the amldapuser user. This password must be different from the password of the amadmin user. It can be any valid Directory Service password.
Set this value to the same value used by Access Manager on the remote host.
Password Encryption Key
AM_ENC_PWDA string that Access Manager uses to encrypt user passwords.
All Access Manager subcomponents must use the same encryption key that the Identity Management and Policy Services Core uses. To specify the encryption key for Access Manager SDK, do the following:
In a state file, the default is LOCK. Any character combination is permitted.
Access Manager SDK: Directory Server Information
The installer needs the following Directory Server information if you are installing Access Manager SDK without other Access Manager subcomponents.
Access Manager SDK: Provisioned Directory Information
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.
Existing Provisioned Directory Found
If the installer finds an existing provisioned directory, you provide the following information.
No Existing Provisioned Directory Found
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.
Access Manager SDK: Web Container Information
The installer needs the following web container information if you are installing only Access Manager SDK.
Administration Server Configuration InformationThe installer needs the following information for Administration Server.
Administration Server: Administration Information
Table 4-18 Administration Information for Administration Server
Label and State File Parameter
Description
Server Root
ADMINSERV_ROOTBase pathname under which the components managed by Administration Server are installed.
The default value is:
Solaris OS: /var/opt/mps/serverroot
Linux: /var/opt/sun/directory-serverAdministration Port
ADMINSERV_PORTPort to use when connecting to this Administration Server through Administration Console over HTTP.
The default value is 390. Any available port number is permitted.
Administration Domain
ADMINSERV_DOMAINA name for a collection of servers that will share a directory service.
The suggested default value is the host domain name that you set under Common Server Settings. Refer to Table 4-1. However, administrative domain does not have to match or be associated with a network domain.
System User
ADMINSERV_SYSTEM_USERUser ID under which Administration Server processes run. Any valid system user is permitted.
The default value is the system user you provided under Common Server Settings. Refer to Table 4-1.
Note: This value must be the same as the value for the associated Directory Server.
System Group
ADMINSERV_SYSTEM_GROUPAny valid system group is permitted.
The default value is the system group you provided under Common Server Settings. Refer to Table 4-1.
Note: This value must be the same as the value for the associated Directory Server.
Administration Server: Configuration Directory Settings Information
Table 4-19 Configuration Directory Settings Information for Administration Server
Label and State File Parameter
Description
Administration User ID
ADMINSERV_CONFIG_ADMIN_USERUser ID of the configuration directory administrator. Administration Server uses this identity when managing configuration directory data.
The default value is the Administrator User ID you provided under Common Server Settings. Refer to Table 4-1.
If you are installing Directory Server in this session, the default value is the Directory Server Administrator User ID. Refer to Table 4-23.
Administrator Password
ADMINSERV_CONFIG_ADMIN_PASSWORDPassword for the configuration directory administrator.
The default value is the Administrator User Password you provided under Common Server Settings. Refer to Table 4-1.
If you are installing Directory Server in this session, the default value is the Directory Server Administrator User Password. Refer to Table 4-23.
Directory Server Host
ADMINSERV_CONFIG_DIR_HOSTSpecifies a host name or value that resolves to the host on which the configuration directory resides. The configuration directory stores configuration data for all servers belonging to the Administration Domain.
If you are installing Directory Server in this session, the default value is the Host Name (CMN_HOST_NAME) that you provided under Common Server Settings. Refer to Table 4-1
If you are not installing Directory Server in this session, there is no default value.
Directory Server Port
ADMINSERV_CONFIG_DIR_PORTPort to use when binding to the configuration directory for LDAP operations.
Any valid port number that is not in use is permitted. Default is 389
If you are installing Directory Server in this session, the default value is the value of the Directory Server Port. Refer to Table 4-24.
If you are not installing Directory Server in this session, there is no default value.
Application Server Configuration InformationThe installer needs the following information for Application Server:
Application Server: Administration Information
Table 4-20 Administration Information for Application Server
Label and State File Parameter
Description
Admin User Name
AS_ADMIN_USERUser ID of the Application Server administrator.
The default value is the Administrator User ID you provided under Common Server Settings. Refer to Table 4-1.
Password
AS_PASSWORDPassword for the Application Server administrator.
The default value is the Administrator Password you provided under Common Server Settings. Minimum of 8 characters. Refer to Table 4-1.
Admin Port
AS_ADMIN_PORTPort on which Application Server’s administrative server listens for connections. Provides access to the administration tools.
The default value is 4849.
JMX Port
AS_JMX_PORTPort on which Application Server listens for JMX connections.
The default value is 8686.
HTTP Server Port
AS_HTTP_PORTPort on which Application Server listens for HTTP connections.
The default value is 8080. If the installer detects that the default port is used, an alternative value is suggested.
HTTPS Port
AS_HTTPS_PORTPort on which Application Server listens for HTTPS connections.
The default value is 8181.
Master Password
AS_MASTER_PASSWORDSSL certificate database password, used for asadmin operations such as Domain Administration Server startup and Node Agent startup.
The default value is the Administrator Password you provided under Common Server Settings. Minimum of 8 characters.
Application Server: Node Agent Information
The installer needs the following information for Application Server node administration.
Application Server: Load Balancing Plugin Information
Directory Server Configuration InformationThe installer needs the following information for Directory Server:
Directory Server: Administration Information
Table 4-23 Administration Information for Directory Server
Label and State File Parameter
Description
Administrator User ID
DS_ADMIN_USERUser with administrator privileges for the configuration directory.
This user can modify Directory Server configuration, including creating and removing suffixes, but access control restrictions apply.
The default value is the Administrator User ID you provided under Common Server Settings. Refer to Table 4-1.
Administrator Password
DS_ADMIN_PASSWORDPassword for the Administrator.
The default value is the Administrator Password you provided under Common Server Settings. Refer to Table 4-1.
Directory Manager DN
DS_DIR_MGR_USERDistinguished Name (DN) of the user who has unrestricted access to Directory Server.
The default value is cn=Directory Manager.
Directory Manager Password
DS_DIR_MGR_PASSWORDPassword for the directory manager.
There is no default value.
Directory Server: Server Settings Information
Table 4-24 Server Settings Information for Directory Server
Label and State File Parameter
Description
Server Identifier
DS_SERVER_IDENTIFIERName that identifies a Directory Server instance in the Administration Console.
The name must conform to operating system file naming conventions. Periods and spaces are not allowed.
The default value is the Host Name (CMN_HOST_NAME) that you provided under Common Server Settings. Refer to Table 4-1.
Server Port
DS_SERVER_PORTPort on which Directory Server listens for client connections.
The default value is 389.
Suffix
DS_SUFFIXInitial 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.
Administration Domain
DS_ADM_DOMAINGroup of server products that share a user directory for data management and authentication.
The default value is the value that you specified for DNS Domain Name (CMN_DOMAIN_NAME) under Common Server Settings. Refer to Table 4-1.
System User
DS_SYSTEM_USERUser name (UID) that Directory Server uses to run on the host. Use the name, not the ID number.
The default value is the System User you provided under Common Server Settings. Refer to Table 4-1.
Note: This value must be the same as the value for the associated Administration Server.
System Group
DS_SYSTEM_GROUPGroup name (GID) in which the Directory Server runs as a user. Use the name, not the ID number.
The default value is the System Group you provided under Common Server Settings. Refer to Table 4-1.
Note: This value must be the same as the value for the associated Administration Server.
Directory Server: Configuration Directory Server Information
Configuration data for this Directory Server instance can be stored in this Directory Server instance, or in an existing Directory Server instance on another host. If you store configuration data in this instance, you respond only to the first question in this table. If you store configuration data in another instance, you provide all information listed in this table.
Directory Server: Data Storage Location Information
User data and group data can be stored in this instance of Directory Server or in an existing instance. The configuration information listed in the following table is needed only if you are storing user data and group data from this instance of Directory Server in the user directory of another instance.
Directory Server: Populate Data Information
You can populate the user directory of Directory Server during the installation and configuration process, rather than as a separate subsequent step.
Directory Proxy Server Configuration InformationIf Administration Server is installed at the same time as Directory Proxy Server, Administration Server must also be configured.
If you are installing Directory Proxy Server onto a host that has a previously installed version of Administration Server, the installer also needs server root information.
Directory Proxy Server: Port Selection Information
The installer needs port selection information for Directory Proxy Server.
Directory Proxy Server: Server Root Information
The installer needs the values in the following table only if a previous installation of Administration Server is present.
Table 4-29 Server Root Information for Directory Proxy Server
Label and State File Parameter
Description
Administration Server Root Directory
DPS_SERVERROOTThe file system directory where Administration Server configuration data for this instance of Directory Proxy Server is stored.
This directory is associated with the Server Root (ADMINSERV_ROOT) in the Administration Server configuration. See Table 4-18.
The format for this value is a fully qualified path name on the local file system.
There is no default value.
Portal Server Configuration InformationThe installer needs the following information for Portal Server:
Portal Server: Web Container Information
Portal Server runs in one of four web containers. The information that the installer needs is different for each web container. The following table lists the four web containers and the tables that describe the information required for each web container.
Table 4-30 Web Container Information for Portal Server
Web Container
See...
Web Server
Application Server
Web Container Information: Portal Server with Application Server
BEA WebLogic
IBM WebSphere Application Server
Web Container Information: Portal Server with Web Server
Table 4-31 describes the information that the installer needs when Web Server is the web container for Portal Server.
Table 4-31 Web Container Information for Portal Server with Web Server
Label and State File Parameter
Description
Installation Directory
PS_DEPLOY_DIRDirectory in which the Web Server is installed. The default value is:
Solaris OS: /opt/SUNWwbsvr
Linux: /opt/sun/webserverServer Instance
PS_DEPLOY_INSTANCEWeb Server instance you want the Portal Server to use.
Server Instance Port
PS_DEPLOY_PORTPort on which Web Server listens for HTTP connections.
The default value is 80.
If you are installing Web Server in this installer session, the default value is the Web Server HTTP Port (WS_ADMIN_PORT) value. Refer to Table 4-57.
Server Document Root
PS_DEPLOY_DOCROOTDirectory where static pages are kept. The default value is:
Solaris OS: /opt/SUNWwbsvr/docs
Linux: /opt/sun/webserver/docsSecure Server Instance Port
PS_DEPLOY_PROTOCOLSpecify 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 http.
Web Container Information: Portal Server with Application Server
Table 4-32 describes the information that the installer needs when Application Server is the web container for Portal Server.
Web Container Information: Portal Server with BEA WebLogic
Table 4-33 describes the information that the installer needs when BEA WebLogic is the web container for Portal Server.
Web Container Information: Portal Server with IBM WebSphere
Table 4-34 describes the information that the installer needs when IBM WebSphere Application Server is the web container for Portal Server.
Portal Server: Web Container Deployment
Table 4-35 describes web container deployment information that the installer needs for Portal Server.
Portal Server Secure Remote Access Configuration InformationThis section first describes installation of Secure Remote Access Core, and then describes installation of the Gateway, Netlet Proxy, and Rewriter Proxy subcomponents of Portal Server Secure Remote Access.
Secure Remote Access Core Configuration
Table 4-36 lists the types of information that the installer needs when installing Portal Server Secure Remote Access Core. The information that you must supply differs according to which of the following scenarios applies:
- Single-session installation. You are installing Portal Server and Portal Server Secure Remote Access together.
- Multiple Session installation. You install Portal Server in one session, and then install Portal Server Secure Remote Access in a later session.
Table 4-36 Information Needed for Installation of Portal Server Secure Remote Access Core
Portal Server Situation
Requirements
Location of Information
Portal Server is being installed in this session.
Gateway information
Portal Server Is already installed and using Web Server or IBM WebSphere Application Server.
Web Container Deployment information
Gateway information
Access Manager information
Multiple Session Installation with Sun Java System Web Server or IBM WebSphere Application Server
Portal Server Is already installed and using Application Server.
Web Container Deployment information
Access Manager information
Gateway information
Sun Java System Application Server information
Multiple Session Installation with Sun Java System Application Server or BEA WebLogic
Portal Server Is already installed and using BEA WebLogic.
Web Container Deployment information
Gateway information
Access Manager information
BEA WebLogic information
Multiple Session Installation with Sun Java System Application Server or BEA WebLogic
Single-Session Installation
When you install Portal Server Secure Remote Access Core and Portal Server in a single session, you provide information about Portal Server Secure Remote Access Gateway. The installer obtains other Portal Server Secure Remote Access configuration information from the Portal Server configuration.
Table 4-37 describes the gateway information that the installer needs when you are installing Portal Server Secure Remote Access Core.
Multiple Session Installation with Sun Java System Web Server or IBM WebSphere Application Server
This section lists the information you must provide when you install Portal Server Secure Remote Access on a host where the following is true:
In this scenario, you must provide the following types of information:
The following table lists the information that you specify about the web container.
The following table lists the information that you specify about Access Manager.
Multiple Session Installation with Sun Java System Application Server or BEA WebLogic
This section lists the information you must provide when you install Portal Server Secure Remote Access on a host where the following is true:
In this scenario, you must provide the following types of information:
The following table lists the information that you specify about the web container.
The following table lists the information that you specify about Access Manager.
The following table lists the information that you specify about Sun Java System Application Server or BEA WebLogic Server
Gateway Configuration
This section lists the information you must provide when you install the Gateway subcomponent. In this scenario, you must provide the following types of information:
Web Container Deployment Information
The following table lists the information that you specify about the web container.
Access Manager Information
The following table lists the information that you must specify about Access Manager.
Gateway Information
Table 4-45 describes the gateway information that the installer needs when you are installing the Gateway subcomponent.
Certificate Information
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.
Netlet Proxy Configuration
This section lists the information you must provide when you install the Netlet Proxy subcomponent. In this scenario, you must provide the following types of information:
Web Container Deployment Information
The following table lists the information that you specify about the web container.
Access Manager Information
The following table lists the information that you must specify about Access Manager.
Netlet Proxy Information
Table 4-49 describes the Netlet Proxy information that the installer needs when you are installing Netlet Proxy.
Proxy Information
The following table describes information that you must enter if you are installing the proxy subcomponents on a host on which there is an existing installation of Portal Server Secure Remote Access.
Certificate Information
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.
Rewriter Proxy Configuration
This section lists the information you must provide when you install the Rewriter Proxy subcomponent. In this scenario, you must provide the following types of information:
The following sections provide details on the information you must provide.
Web Container Deployment Information
The following table lists the information that you specify about the web container.
Rewriter Proxy Information
Table 4-53 describes the Rewriter Proxy information that the installer needs when you are installing Rewriter Proxy.
Proxy Information
The following table describes information that you must enter if you are installing the proxy subcomponents on a host on which there is an existing installation of Portal Server Secure Remote Access.
Certificate Information
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.
Web Server Configuration InformationThe installer needs the following information for Web Server:
Web Server: Administration Information
Table 4-56 Administration Information for Web Server
Label and State File Parameter
Description
Administrator User ID
WS_ADMIN_USERUser ID of the Web Server administrator.
The default value is the Administrator User ID you provided under Common Server Settings. Refer to Table 4-1.
Administrator Password
WS_ADMIN_PASSWORDPassword for the Web Server administrator.
The default value is the Administrator Password you provided under Common Server Settings. Refer to Table 4-1.
Web Server Host
WS_INSTANCE_HOSTA 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 host-name.domain-name.
Administration Port
WS_ADMIN_PORTPort on which Web Server’s Administration Server listens for connections.
The default value is 8888.
Administration Runtime User ID
WS_ADMIN_SYSTEM_USERUser ID under which Web Server Administration Server runs.
The default value is root.
Web Server: Default Web Server Instance Information
Parameters Used Only in State FilesThe following table contains information on state file parameters that are not associated with component configuration. Parameter names are listed alphabetically.