(6891038) LoadBalancer plugin installer does not update virtual host obj.conf file during installation

• Description

  In some circumstances, when the LoadBalancer plugin is properly installed on Web Server 7 and the loadbalancer.xml file generated, the LoadBalancer still does not initialize properly.

  For example, consider the following scenario:

  • A user performs a specific configuration on a Web Server virtual host (for example, Web Server virtual server Log preferences) before installing the LoadBalancer plugin In this example, Web Server generates a new obj.conf file with a virtual host name: <ws-virtual-host-name>-obj.conf.

  • During LoadBalancer plugin installation, the process automatically updates various Web Server configuration files (server.xml, magnus.conf, obj.conf), but does not update <ws-virtual-host-name>-obj.conf.

  The problem in this scenario is that the <ws-virtual-host-name>-obj.conf file takes precedence over the other configuration files in the Web Server startup sequence, and when the required lbplugin entries are missing, the LoadBalancer does not fully initialize even though no error message is displayed.

• Solution

  Manually add the following entries to the <ws-virtual-host-name>-obj.conf file:

  1. Under the <Object name="default"> tag add the following on a single line:

     NameTrans fn="name-trans-passthrough" name="lbplugin" \ config-file="/opt/SUNWwbsvr7/https-<ws_config_name>/config/loadbalancer.xml"

  2. At the bottom of the file, append the following:

     <Object name="lbplugin"> PathCheck fn="deny-existence" path="*/WEB-INF/*" ObjectType fn="force-type" type="magnus-internal/lbplugin" Service type="magnus-internal/lbplugin" fn="service-passthrough" Error reason="Bad Gateway" fn="send-error" uri="$docroot/badgateway.html" </Object> <Object ppath="*lbconfigupdate*"> PathCheck fn="get-client-cert" dorequest="1" require="1" </Object> <Object ppath="*lbgetmonitordata*"> PathCheck fn="get-client-cert" dorequest="1" require="1" </Object>

  After making these changes, restart the LoadBalancer.