This chapter provides general instructions for setting up Enterprise Portal 6.0 to run in a distributed environment.
In this chapter, “load balancer” refers to the EAServer redirector Web plug-in running on a an Apache Web server. You can configure EP for a distributed environment using one of three configurations for load balancing:
Install Portal Interface with the Apache Web Server configured with the EAServer redirector for load balancing
Use a hardware load balancer in place of the Apache Web Server
Use a third-party software redirector
If you use a hardware or third-party load balancer,
it must support sticky session. A sticky session is a session in
which each user’s request is directed to the server on which
the user’s session exists.
The main host is where you have a single point of failure. If a firewall is introduced, clients cannot see the hosts inside the firewall. Be sure that the port used by the portal is open.
The redirector for the HTTP load balancing cannot be
on the same machine as EAServer because they use the same port.
The Universal Portlet Playback (UPP) engine and some Model View Controller (MVC) applications make local requests using localhost.domain:port to retrieve HTML, XML, and other documents. If you set the default_http_port to 80, the port on which the redirector is listening (specified in global.properties.xml) you must add a localhost.domain:80 listener in EAServer. Most Web servers already listen on localhost, which creates a listener conflict.
All Portal Interface instances must be connected to the same portal database. All EAServers using Enterprise Security must be connected to the same ACDB. The servlet-persistent connection cache must also be connected to the same database with the ps_HttpSession table.
