Sun Java Enterprise System 2005Q4 Installation Reference

Portal Server Configuration Information

The 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 1–31 Web Container Information for Portal Server


Web Container	Refer to the Following
Web Server	Web Container Information: Portal Server with Web Server
Application Server	Web Container Information: Portal Server with Application Server
BEA WebLogic	Web Container Information: Portal Server with BEA WebLogic
IBM WebSphere Application Server	Web Container Information: Portal Server with IBM WebSphere

Web Container Information: Portal Server with Web Server

This section describes the information that the installer needs when Web Server is the web container for Portal Server.

Table 1–32 Web Container Information for Portal Server with Web Server


Label and State File Parameter	Description
Installation Directory `PS_DEPLOY_DIR`	Directory in which the Web Server is installed. The default value is: Solaris OS: `/opt/SUNWwbsvr` Linux: `/opt/sun/webserver`
Server Instance `PS_DEPLOY_INSTANCE`	Web Server instance you want the Portal Server to use.
Server Instance Port `PS_DEPLOY_PORT`	Port 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 Web Server: Default Web Server Instance Information
Server Document Root `PS_DEPLOY_DOCROOT`	Directory where static pages are kept. The default value is: Solaris OS: `/opt/SUNWwbsvr/docs` Linux: `/opt/sun/webserver/docs`
Secure Server Instance Port `PS_DEPLOY_PROTOCOL`	Specify 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

This section describes the information that the installer needs when Application Server is the web container for Portal Server.

Table 1–33 Web Container Information for Portal Server with Application Server


Label and State File Parameter	Description
Installation Directory `PS_DEPLOY_DIR`	Directory in which Application Server is installed. The default value is: Solaris OS: `/opt/SUNWappserver/appserver` Linux: `/opt/sun/appserver`
Domain Name `PS_DEPLOY_DOMAIN`	Name of the Application Server instance to which the Portal Server will be deployed. This name is also the name of the Application Server instance directory. The default value is `domain1`.
Server Instance Directory `PS_DEPLOY_INSTANCE_DIR`	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: `/var/opt/sun/appserver/domains/domain1`
Server Instance Port `PS_DEPLOY_PORT`	Port on which Application Server listens for connections to the instance. The default value is `8080`.
Document Root Directory `PS_DEPLOY_DOCROOT`	Name of the directory where static pages are kept. The default value is: Solaris OS: `/var/opt/SUNWappserver/domains/domain1/docroot` Linux: `/var/opt/sun/appserver/domains/domain1/docroot`
Administration Port `PS_DEPLOY_ADMIN_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 `PS_DEPLOY_ADMIN`	User ID that Portal Server uses to access the Application Server as administrator. The default value is `admin`.
Administrator Password `PS_DEPLOY_ADMIN_PASSWORD`	Password that the Portal Server uses to access the Application Server as administrator.
Secure Server Instance Port `PS_DEPLOY_PROTOCOL`	Specify 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 `PS_DEPLOY_ADMIN_PROTOCOL`	Specify 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 `http`.

Web Container Information: Portal Server with BEA WebLogic

This section describes the information the installer needs when BEA WebLogic is the web container for Portal Server.

Table 1–34 Web Container Information for Portal Server with BEA WebLogic


Label and State File Parameter	Description
Home Directory `PS_DEPLOY_DIR`	Path to the BEA WebLogic home directory. The default value is `/usr/local/bea`.
Product Installation Directory `PS_DEPLOY_PRODUCT_DIR`	Path to the directory where BEA WebLogic is installed. The default is `/usr/local/bea/weblogic81`.
User Project’s Directory `PS_DEPLOY_PROJECT_DIR`	Path to the directory where BEA WebLogic stores user projects. The default is `user_projects`.
Product JDK Directory `PS_DEPLOY_JDK_DIR`	Path to the directory where the copy of JDK that BEA WebLogic uses is installed. The default is `/usr/local/bea/jdk141_05`.
Server / Cluster Domain `PS_DEPLOY_DOMAIN`	Name of the BEA WebLogic domain in which BEA WebLogic is deployed. The default is `mydomain`.
Server / Cluster Instance `PS_DEPLOY_INSTANCE`	Name of the BEA WebLogic instance that will run Portal Server. The default is `myserver`.
Server / Cluster Port `PS_DEPLOY_PORT`	Port on which BEA WebLogic listens for administrative connections. The default is `7001`.
Server / Cluster Protocol `PS_DEPLOY_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 is `http`.
Document Root Directory `PS_DEPLOY_DOCROOT`	Path to the directory where BEA WebLogic stores content documents.
Administrator User ID `PS_DEPLOY_ADMIN`	User name of the BEA WebLogic administrator (system user). The default is `weblogic`.
Administrator Password `PS_DEPLOY_ADMIN_PASSWORD`	Password of the BEA WebLogic administrator (system user).
Managed Server `PS_DEPLOY_NOW`	Enables you to indicate that the BEA WebLogic Server is a managed server. If the BEA WebLogic Server is a managed server, the Portal Server web applications should not be deployed to the specified WebLogic Server Instance. In a state file, specify `n` for a managed server or `y` for a non-managed server. The default value is `y`.

Web Container Information: Portal Server with IBM WebSphere

This section describes the information that the installer needs when IBM WebSphere Application Server is the web container for Portal Server.

Table 1–35 Web Container Information for Portal Server with IBM WebSphere


Label and State File Parameter	Description
Installation Directory `PS_DEPLOY_DIR`	Path to the directory where IBM WebSphere Application Server is installed. The default value is `/opt/IBM/WebSphere/Express51/AppServer`.
Virtual Host `PS_DEPLOY_VIRTUAL_HOST`	Name of the virtual host alias for the IBM WebSphere Application Server instance. The default value is `default_host`.
Cell `PS_DEPLOY_CELL`	Name of the IBM WebSphere Application Server cell. The default value is `DefaultNode`.
Node `PS_DEPLOY_NODE`	Name of the IBM WebSphere Application Server node. The default value is `DefaultNode`
Server Instance `PS_DEPLOY_INSTANCE`	Name of the IBM WebSphere Application Server instance. The default value is `server1`.
Server Instance Port `PS_DEPLOY_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 `9080`.
Document Root Directory `PS_DEPLOY_DOCROOT`	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.
Java Home Directory `PS_DEPLOY_JDK_DIR`	Path to the Java installation that IBM WebSphere Application Server uses. The default is `/opt/IBM/WebsSphere/Express51/Appserver/java`.
Secure server instance `PS_DEPLOY_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`.

Portal Server: Web Container Deployment

This section describes web container deployment information that the installer needs for Portal Server.

Table 1–36 Portal Information for Portal Server, All Scenarios


Label and State File Parameter	Description
Load Balancer Protocol	Specifies whether the load balancer uses HTTP or HTTPS protocol. This option is enabled only if you specify the “Load Balancer controlling multiple Portal Servers” option. Used to construct the `PS_LOAD_BALANCER_URL` parameter.
Load Balancer Host	The fully qualified name of the load balancer host. This option is enabled only if you specify the “Load Balancer controlling multiple Portal Servers” option. Used to construct the `PS_LOAD_BALANCER_URL` parameter.
Load Balancer Port	The port on which the load balancer listens for connections. This option is enabled only if you specify the “Load Balancer controlling multiple Portal Servers” option. Used to construct the `PS_LOAD_BALANCER_URL` parameter.
Deployment URI `PS_DEPLOY_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. The default value is `/portal`.
Load Balancer controlling multiple Portal Servers	Specify whether the Portal Server you are installing is accessed through a load balancer that is controlling multiple Portal Servers.
Install Sample Portal `PS_SAMPLE_PORTAL`	Specify whether to install a sample portal. In a state file, the value can be `y` or `n`. The default value is `y`.