Oracle Audio Technologies 9i ユーザーズマニュアル

Configuring the Personalization Portal for Load-Balancing

Multiple JVM Support and Load Balancing

When multiple instances are running, load balancing can be performed by a 
separate machine. For example, there could be several Oracle HTTP Server 
instances, each with a set of JServ instances balanced on a one-to-many basis by this 
machine. The Oracle HTTP Server instances can perform load balancing by using a 
hardware load balancer in front of the Oracle HTTP Server instances.

The main purpose of multiple JVM support in Wireless Edition is to provide 
scalability through load-balancing. There are three implementations when setting 
up load-balancing.

■

Load-balancing among Oracle HTTP servers through hardware load-balancing.

■

Load-balancing among Jserv instances with cookies.

■

Load-balancing among Jserv instances with URL rewriting.

When intermediate gateways or proxies and the clients support cookies, load 
balancing can be achieved using cookies:

Set the enable.http.session.binding parameter in all of the System.properties 
files (on all machines, if more than one machine is involved) to true.

In the ORACLE_HOME\Apache\JServ\conf\zone.properties file set the 
session.useCookies parameter to true.

When intermediate gateways or proxies do not support cookies, load balancing can 
be achieved through URL rewriting:

Set the enable.http.session.binding parameter in all of the System.properties 
files (on all machines, if more than one machine is involved) to true.

In the ORACLE_HOME\Apache\JServ\conf\zone.properties file set the 
session.useCookies parameter to false.

This section describes the configuration of the Personalization Portal in two 
environments: