Work with the plug-in configuration file

Work with the plug-in configuration file

+
Search Tips | Advanced Search

The plug-in configuration file, plugin-cfg.xml, contains routing information for all applications mapped to the Web server. This file is read by a binary plug-in module loaded in the Web server.
An example of a binary plug-in module is the file...
mod_ibm_app_server_http.dll

...for IBM HTTP Server on the Windows platform.
The binary plug-in module does not change. However, the plug-in configuration file for the binary module needs to be regenerated and propagated to the Web server whenever a change is made to the configuration of applications mapped to the Web server. The binary module reads the XML file to adjust settings and to locate deployed applications for the Web server.
Example 7-2 shows an excerpt from a generated plug-in configuration file.
<?xml version="1.0" encoding="ISO-8859-1"?>


<Config ASDisableNagle="false" 
        AcceptAllContent="false" 
        AppServerPortPreference="HostHeader" 
        ChunkedResponse="false" 
        IISDisableNagle="false" 
        IISPluginPriority="High" 
        IgnoreDNSFailures="false" 
        RefreshInterval="60" 
        ResponseChunkSize="64" 
        VHostMatchingCompat="false">

   <Log LogLevel="Error" Name="c:\opt\WebSphere\Plugins\logs\webserver1\http_plugin.log"/>
   <Property Name="ESIEnable" Value="true"/>
   <Property Name="ESIMaxCacheSize" Value="1024"/>
   <Property Name="ESIInvalidationMonitor" Value="false"/>

<VirtualHostGroup Name="default_host">
      <VirtualHost Name="*:9080"/>
      <VirtualHost Name="*:80"/>
      <VirtualHost Name="*:9443"/>
   </VirtualHostGroup>

<ServerCluster CloneSeparatorChange="false" 
               LoadBalance="Round Robin" 
               Name="server1_NodeA_Cluster" 
               PostSizeLimit="-1" 
               RemoveSpecialHeaders="true" 
               RetryInterval="60">

      <Server ConnectTimeout="0" 
              ExtendedHandshake="false" 
              MaxConnections="-1" 
              Name="NodeA_server1" 
              WaitForContinue="false">

         <Transport Hostname="wan" Port="9080" Protocol="http"/>

         <Transport Hostname="wan" Port="9443" Protocol="https">

            <Property Name="keyring" 
                      Value="c:\opt\WebSphere\Plugins\etc\plugin-key.kdb"/>
            <Property Name="stashfile" 
                      Value="c:\opt\WebSphere\Plugins\etc\plugin-key.sth"/>

         </Transport>

      </Server>

   </ServerCluster>

<UriGroup Name="default_host_server1_NodeA_Cluster_URIs">
      <Uri AffinityCookie="JSESSIONID" 
           AffinityURLIdentifier="jsessionid" 
           Name="/snoop/*"/>
      <Uri AffinityCookie="JSESSIONID" 
           AffinityURLIdentifier="jsessionid" 
           Name="/hello"/>

   <Route ServerCluster="server1_NodeA_Cluster" 
          UriGroup="default_host_server1_NodeA_Cluster_URIs" 
          VirtualHostGroup="default_host"/>
</Config>
The specific values for the UriGroup Name and AffinityCookie attributes depend on how you have assembled your application. When you assemble your application:

If you specify File Serving Enabled, then only a wildcard URI is generated, regardless of any explicit servlet mappings.
If you specify Serve servlets by class name, then a URI of the form URI name = <web_app_uri>/servlet/ is generated.

Both these options apply for both the UriGroup Name and AffinityCookie attributes.
When the plug-in configuration file is generated, it does not include admin_host in the list of virtual hosts. See Allowing Web servers to access the console in the Information Center for information about how to add it to the list.
Next