+

Search Tips   |   Advanced Search

Set up the HTTP server plug-in on a portal farm


We can use a Web server to handle load balancing across the portal farm. This documentation is specific to the HTTP server but we can use any supported Web server.

Your Web server must already be configured to use the IBM WebSphere Application Server plug-in for load balancing.


Set up the HTTP server plug-in on the portal farm

  1. Generate the plug-in configuration from one of the appservers in the farm using...

      WP_PROFILE/bin/GenPluginCfg

  2. Modify plugin-cfg.xml generated in the previous step, to have a server entry for every server in the farm:

    For the purposes of this example, it is assumed every server in the farm uses the same set of ports.

    Add the CloneID attribute to each Server element with a value that uniquely identifies this server instance. This value should coincide with the value set for the Web Container custom property...

      HttpSessionCloneId

    ...on each farm server instance.

    Locate the CloneID in the file..

      variable_map.properties

    ...located in the directory specified when you ran...

      enable-farm-mode

    In the following example, replace s1.myco.com and s2.myco.com with the CloneID values for each server in the farm. 

     
<ServerCluster CloneSeparatorChange="false" 
               GetDWLMTable="false" 
               IgnoreAffinityRequests="true" 
               Name="PortalCluster" 
               PostBufferSize="64" 
               PostSizeLimit="-1" 
               RemoveSpecialHeaders="true"    
               RetryInterval="60">

      <Server CloneID="s1.myco.com" 
              ConnectTimeout="5" 
              ExtendedHandshake="false"                         
              LoadBalanceWeight="2" 
              MaxConnections="-1" 
              Name="svtvm2_WebSphere_Portal"                         
              ServerIOTimeout="60" 
              WaitForContinue="false">

         <Transport Hostname="s1.myco.com" Port="10039" Protocol="http"/>
         <Transport Hostname="s1.myco.com" Port="10029" Protocol="https">

            <Property Name="keyring" Value="/usr/IBM/IHS/Plugins/config/webserver1/plugin-key.kdb"/>
            <Property Name="stashfile" Value="/usr/IBM/IHS/Plugins/config/webserver1/plugin-key.sth"/>

         </Transport>

      </Server>

      <Server CloneID="s2.myco.com" 
              ConnectTimeout="5" 
              ExtendedHandshake="false"                         
              LoadBalanceWeight="2" 
              MaxConnections="-1" 
              Name="svtvm3_WebSphere_Portal"                         
              ServerIOTimeout="60" 
              WaitForContinue="false">

         <Transport Hostname="s2.myco.com" Port="10039" Protocol="http"/>
         <Transport Hostname="s2.myco.com" Port="10029" Protocol="https">

            <Property Name="keyring" Value="/usr/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.kdb"/>
            <Property Name="stashfile" Value="/usr/IBM/HTTPServer/Plugins/config/webserver1/plugin-key.sth"/>
         </Transport>

      </Server>

  </ServerCluster>

  3. Replace plugin-cfg.xml currently used by the HTTP Server plugin with this newly edited version.

  4. Restart the HTTP Server to ensure the changes are picked up, and watch for any startup errors that might indicate a syntax issue within plugin-cfg.xml.

  5. Stop and restart all the WebSphere_Portal servers on the portal farm


Parent: Set up a portal farm
Related:

Configure HTTP session manager with WebSphere Portal
Start and stop servers, dmgrs, and node agents