Configuring the Sun Java System Web Server Plug-in

The Sun Java System Web Server plug-in can be used as a pass-through load balancing mechanism with Application Server. Only the configuration information that is specific to Oracle Solaris Cluster HA for Sun Java System Application Server is included here. The requirement for these configuration instructions is the installation of the Sun Java System Web Server plug-in. See the Application Server documentation for detailed installation instructions, including patch requirements.

If you are configuring Oracle Solaris Cluster HA for Sun Java System Application Server as a failover data service, installation of the front-end Sun Java System Web Server is optional.

To configure the Sun Java System Web Server plug-in, configure the listeners in the loadbalancer.xml file.

• If you are configuring Oracle Solaris Cluster HA for Sun Java System Application Server as a failover data service, specify the Application Server logical hostname as the listeners in the loadbalancer.xml file.

  <instance name="server1" enabled=true disable-timeout-in-minutes="60"
  listeners="http://foo-lh:80/ " />

• If you configuring Oracle Solaris Cluster HA for Sun Java System Application Server as a data service mastered on multiple nodes, and if the web server is running on the same cluster as the application server, specify the cluster private IP addresses as the listeners in the loadbalancer.xml file.

  <instance name="server1" enabled=true disable-timeout-in-minutes="60"
  listeners="http://172.16.193.1:80/ http://172.16.194.5:80/ " />

  ---

  Note - You must use the node transport adapter IP addresses in the plug-in configuration. To find these IP addresses, execute the scconf -p | less command from the primary Oracle Solaris Cluster node. Note that equivalent hostnames such as clusternode1-priv do not work in this configuration, and should not be used.

  ---

• If you are configuring Oracle Solaris Cluster HA for Sun Java System Application Server as a data service mastered on multiple nodes, and if the web server is not running on the same cluster as the application server, specify the physical hostnames as the listeners in the loadbalancer.xml file.

  <instance name="server1" enabled=true disable-timeout-in-minutes="60"
  listeners=http://hosta:80/ http://hostb:80/ " />

  The preceding example assumes that the Application Server instances are configured on port 80 on cluster nodes hosta and hostb.