Generate the plugin-cfg.xml file

IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Prepare your dashboard environment > Configure an HTTP Server to load balance multiple Tivoli Enterprise Portal Servers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Generate the plugin-cfg.xml file

Generate the plugin-cfg.xml file for each Tivoli Enterprise Portal Server and then configure the load balancing HTTP server to use the plugin information. The plugin-cfg.xml file specifies the URIs that must be redirected and which servers to redirect requests to.

Procedure

On each Tivoli Enterprise Portal Server, run:
install_dir\CNPSJ\bin\GenPluginCfg.bat
install_dir/interp/iw/bin/GenPluginCfg.sh This command generated a file called plugin-cfg.xml and saves it to the install_dir\CNPSJ\profiles\ITMProfile\config\cells directory on Windows and the install_dir/interp/iw/profiles/ITMProfile/config/cells directory on Linux and UNIX.

On the computer where the load balancing HTTP Server is installed, replace the existing plugin-cfg.xml with the plugin-cfg.xml file generated for one of the portal servers. You will copy a subset of the information from the plugin-cfg.xml files for the other portal servers into the plugin-cfg.xml file that is used by the HTTP server.

Customize the plugin-cfg.xml file for your load balancing HTTP Server environment and each of the Tivoli Enterprise Portal Server instances:

On the computer where the IBM HTTP Server is installed, change to the directory where the plugin-cfg.xml is located (such as cd c:\Program Files(x86)\IBM\WebSphere\Plugins_1\config\webserver1 on Windows or /opt/IBM/WebSphere/Plugins/config/webserver1 on Linux and UNIX).

Open the plugin-cfg.xml file in a text editor and edit the file to provide details for the IBM HTTP Server and all portal server instances. Use the example provided at the end of this topic for reference. The example file includes the following variables which must be replaced with values specific to your environment:

PLUGIN_PATH is the directory path where the WebSphere plugin is installed.

On Linux and UNIX the default is /opt/IBM/WebSphere/Plugins

On Windows the default is C:\Program Files(x86)\IBM\WebSphere\Plugins_1
If your portal servers are installed on different operating system types than the HTTP server, you might need to change the directory path and also make sure you use the correct directory separator character for the system where the HTTP server is installed (for example, on Windows use \ and on Linux or UNIX use /).
HTTP_SERVER_PORT is the port number for the HTTP server.
SERVER1_NAME is a name that identifies the server definition for the first portal server. For example, ITMNODE_ITMSERVER1.
SERVER1 is the fully qualified hostname of the computer where the first portal server is installed and started.
SERVER2_NAME is a name that identifies the server definition for the second portal server. For example, ITMNODE_ITMSERVER2.
SERVER2 is the fully qualified hostname of the computer where the second portal server is installed and started.
CLONE_ID is the unique clone ID assigned to a particular portal server.

The HTTP and HTTPS port values for all portal servers must be the same so check the plugin-cfg.xml file for each portal server to ensure they are using the same port numbers.

Add the following line to the end of the UriGroup section to handle requests for launching the Tivoli Enterprise Portal from Dashboard Application Services Hub:
<Uri Name="/*"/>

In the Log section, ensure the path for the Name attribute and PluginInstallRoot property match your load balancing HTTP server environment. The following values are typical:
The typical value for Name attribute is PLUGIN_PATH/logs/webserver1/http_plugin.log.
The typical value for the PluginInstallRoot property is PLUGIN_PATH/.

In the ServerCluster section, ensure the paths for the keyring and stashfile properties match your load balancing HTTP server environment. The following values are typical:
The typical keyring property value is PLUGIN_PATH/config/webserver1/plugin-key.kdb.
The stashfile properties is PLUGIN_PATH/config/webserver1/plugin-key.sth.

For each additional portal server:

Add a Server entry which specifies its clone ID, name, and fully qualified hostname. You can obtain the clone ID from the portal server's plugin-cfg.xml file. Assign each portal server a unique server name.
Ensure you specify ports 15200 (for HTTP), and 15201 (for HTTPS) instead of ports 15210 and 15211. Ports 15200 and 15201 are the ports for the local HTTP server for each portal server, and these ports must be used to support launching the portal client from Dashboard Application Services Hub.
Follow the same pattern shown in the example at the end of this topic.

Specify the server name in the PrimaryServers section.

Add the CloneID and LoadBalanceWeight attributes for every Server entry.
For more information on web server plug-in workload management policies and to help you determine the appropriate values for the elements LoadBalance and LoadBalanceWeight, refer to the following articles:

http://www.redbooks.ibm.com/abstracts/TIPS0235.html

http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21219567

Example
The following plugin-cfg.xml example for Windows includes values in bold that must be customized for your load balancing HTTP server environment.
<?xml version="1.0" encoding="ISO-8859-1"?>
<Config ASDisableNagle="false" IISDisableNagle="false" 
        IgnoreDNSFailures="false" RefreshInterval="60" 
        ResponseChunkSize="64" AcceptAllContent="false" 
        IISPluginPriority="High"  FIPSEnable="false" 
        AppServerPortPreference="HostHeader" VHostMatchingCompat="false" 
        ChunkedResponse="false">
   <Log LogLevel="Trace" Name="PLUGIN_PATH\logs\webserver1\
        http_plugin.log"/>
    <Property Name="ESIEnable" Value="true"/>
    <Property Name="ESIMaxCacheSize" Value="1024"/>
    <Property Name="ESIInvalidationMonitor" Value="false"/>
    <Property Name="PluginInstallRoot"  Value="PLUGIN_PATH\"/>
   <VirtualHostGroup Name="default_host">
      <VirtualHost Name="*:9080"/>
      <VirtualHost Name="*:80"/>
      <VirtualHost Name="*:9443"/>
      <VirtualHost Name="*:5060"/>
      <VirtualHost Name="*:5061"/>
      <VirtualHost Name="*:443"/>
      <VirtualHost Name="*:15200"/>
      <VirtualHost Name="*:15201"/>
      <VirtualHost Name="*:HTTP_SERVER_PORT"/>
   </VirtualHostGroup>
   <ServerCluster Name="ITMServer_ITMNode_Cluster" CloneSeparatorChange="false" 
    LoadBalance="Round Robin" PostBufferSize="64" IgnoreAffinityRequests="true" 
    PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
      <Server CloneID="CLONE_ID" ConnectTimeout="0" ExtendedHandshake="false" 
          MaxConnections="-1" Name="SERVER1_NAME" ServerIOTimeout="0" 
          WaitForContinue="false">
         <Transport Hostname="SERVER1" Port="15200" Protocol="http"/>
         <Transport Hostname="SERVER1" Port="15201" Protocol="https">
            <Property Name="keyring" Value="PLUGIN_PATH\config\
                  webserver1\plugin-key.kdb"/>
            <Property Name="stashfile" Value="PLUGIN_PATH\config\
                  webserver1\plugin-key.sth"/>
         </Transport>
      </Server>
     <Server CloneID="CLONE_ID" ConnectTimeout="0" ExtendedHandshake="false" 
        MaxConnections="-1" Name="SERVER2_NAME" ServerIOTimeout="0" 
        WaitForContinue="false">
         <Transport Hostname="SERVER2" Port="15200" Protocol="http"/>
         <Transport Hostname="SERVER2" Port="15201" Protocol="https">
            <Property Name="keyring" Value="PLUGIN_PATH\config\
                  webserver1\plugin-key.kdb"/>
            <Property Name="stashfile" Value="PLUGIN_PATH\config\
                  webserver1\plugin-key.sth"/>
         </Transport>
      </Server>
      <PrimaryServers>
        <Server Name="SERVER1_NAME/>
        <Server Name="SERVER2_NAME"/>
      </PrimaryServers>
   </ServerCluster>
   <UriGroup Name="default_host_ITMServer_ITMNode_Cluster_URIs">
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/ivt/*"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/IBM_WS_SYS_RESPONSESERVLET/*"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/IBM_WS_SYS_RESPONSESERVLET/*.jsp"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/IBM_WS_SYS_RESPONSESERVLET/*.jsv"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/IBM_WS_SYS_RESPONSESERVLET/*.jsw"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/IBM_WS_SYS_RESPONSESERVLET/j_security_check"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/IBM_WS_SYS_RESPONSESERVLET/ibm_security_logout"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/RedirectServletWeb/*"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/LICServletWeb/*"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/TEPSREST/*"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/ITMRESTProvider/*"/>
      <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" 
          Name="/ibm/tivoli/*"/>
      <Uri Name="/*"/>
   </UriGroup>
   <Route ServerCluster="ITMServer_ITMNode_Cluster" 
      UriGroup="default_host_ITMServer_ITMNode_Cluster_URIs" 
      VirtualHostGroup="default_host"/>
   <RequestMetrics armEnabled="false" newBehavior="false"
        rmEnabled="false" traceLevel="HOPS">
        <filters enable="false" type="URI">
            <filterValues enable="false" value="/servlet/snoop"/>
            <filterValues enable="false" value="/webapp/examples/HitCount"/>
        </filters>
        <filters enable="false" type="SOURCE_IP">
            <filterValues enable="false" value="255.255.255.255"/>
            <filterValues enable="false" value="254.254.254.254"/>
        </filters>
      </RequestMetrics>
</Config>
Parent topic:
Configure an HTTP Server to load balance multiple Tivoli Enterprise Portal Servers

+
Search Tips | Advanced Search