Portal Interface

Modify the global.properties.xml file on each portal instance if you installed Portal Interface on each EAServer.

You can use synchronization to deploy the portal Web application along with the configuration changes.

Table 3-1shows the global.properties.xml properties that refer to host names, port numbers, and domain settings and how those properties should be set for distributed portal installations.

For example, in a configuration with at least three machines, one machine is the load-balancer. This machine has a publicly accessible DNS address that is visible to all the users of the portal. In this example, the load balancer is named “www” and is in the domain “publicsybase.com.”In addition, there are two or more computers hosting the Web container that contains the Onepage portal application. These computers may be behind a firewall and may have DNS names that are not visible to the portal users at all. In this example there are two computers behind the firewall named “EAS1” and “EAS2” respectively. Both are in the “privatesybase.com” domain.

**Table 3-1: Global properties**
Property	Standalone	Distributed	Description
portal.host	standalone	www	This is the hostname (without domain) that you enter into the URL of your browser to launch Portal Interface or Portal Studio. In a standalone configuration this is the name of the machine where the portal Web-container is running. In a distributed configuration this is the name of the load-balancing machine.
tile.host			Same as portal.host
secure.tile.host			Same as portal.host
domain	.sybase.com	.publicsybase.com	This is the externally visible domain name that goes into the URL users enter to start a Portal Interface or Portal Studio session. In a standalone configuration this is the domain name of the host where the Web-container is running. In a distributed configuration it is the externally visible domain name of the load-balancer machine.
javascript.domain	sybase.com	publicsybase.com	Same as domain, but without the leading dot.
catalog_cache_ refresh_list	127.0.0.1:80 /onepage	eas1.privatesybase.com/onepage, eas2.privatesybase.com/onepage	This is a list of all the Web-containers that are hosting the portal application. When a Studio user make changes on one of the Web-containers and those changes need to be propagated out to the rest, it looks at this list to contact all the other containers. This list should contain the internally visible addresses of each of the Web-container hosts. In a standalone installation, localhost or 127.0.0.1 works. In a distributed installation you should replace the localhost listener with the list of Web-container hosts.
mail.host	10.22.97.100	mailhost.sybase. com	Name of a machine running a SMTP mail service. Contact your network administrator to find the right machine name for your network.
SecureHostname	standalone. sybase.com	www.publicsybase.com	Same as portal.host, concatenated with domain.
SOAPServer	127.0.0.1	127.0.0.1
ThisMachineName	127.0.0.1	127.0.0.1
UWPCacheServer	127.0.0.1	127.0.0.1	Not functional. Each portal instance manages its own cache.
UWPWebServiceHost	standalone. sybase.com
UWPIntegrationHost	standalone. sybase.com
CacheRefreshList	127.0.0.1	eas1.privatesybase.com,eas2.privatesybase.com	A list of all the servers with a UWP cache. Same as catalog_cache_refresh_list except there is not a trailing /onepage on each entry.
DeployHost	standalone. sybase.com	www.publicsybase.com	Concatenation of portal.host and domain.
CacheRefreshList	127.0.0.1	eas1.privatesybase.com,eas2.privatesybase.com	A list of all the servers with a UWP cache. Same as catalog_cache_refresh_list except there is not a trailing /onepage on each entry.
EPSecurityHost	standalone. sybase.com	loadBalancerHost .domanin.com	Unused.
EPSecurityHost PortNumber	9000		Unused.
PSHost	standalone. sybase.com	eas1.privatesybase.com	Internally visible name of the Agent Server. If you are using the Automation agents, you typically choose one portal instance to run them in. This property is used to choose which instance it is.
PSPort	80	80	Same as http_default_port
use_SW_Switch	off		Leave the use_SW_Switch set to off.
nav.host	http://standalone	http://www	Same as portal.host, but with http:// in front.
nav.general.host	http://standalone	http://www	Same as nav.host
nav.secure.host	https://standalone	https://www	Same as portal.host, but with https:// in front.
nav.general.secure.host	https://standalone	https://www	Same as nave.secure.host
acx.host	http://windowsmachine.sybase.com	http://windowsmachine.privatesybase.com	Not used unless you set acx.remote to true. If you do set it to true, this property should have the internally visible DNS name of a windows operating system machine hosting the ACX servlet.

Configuring Portal Interface

Open global.properties.xml on the EAServer machines in Microsoft WordPad on Windows and in any text editor on UNIX.
Search the file and replace all instances of the EAServer host name with the load balancer host name, which is the machine hosting the Web server with the EAServer redirector plug-in. See Table 3-1.
Locate the default_http_port property and change it to the HTTP port running on the Web server running the EAServer redirector plug-in (this should be the same port as the one on EAServer).
Locate the default_https_port property and change it to the HTTPS port running on the Web server running the EAServer redirector plug-in (this should be the same port as the one on EAServer).
Set the portal.epSecurity property to “true.”
In the op_portal_ase DataPool section, set the URL to connect to the database running portaldatabase. All portal instances must connect to the same database server.
(Optional) Use EAServer synchronization to propagate the global.properties.xml file and its changes to other EAServers in the cluster. See the EAServer System Administration Guide for more information on clustering.