WebSphere Virtual Enterprise, Version 6.1.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Generating the plug-in configuration in a high availability environment

You can configure the Web server plug-in configuration to generate in a high availability environment to ensure that the configuration is always generated by one process in the cell regardless of other processes that might not be available.

Before you begin

Establish your high availability environment. See Setting up a high availability environment for more information.

Configure core groups that are in the same cell need to share workload management (WLM) information. See Configuring communication between core groups that are in the same cell for more information.

Using the high availability plugin-cfg generation service does not automatically disable the on demand router (ODR) plugin-cfg generation if it is enabled. The two services are independent. It is redundant to enable both services, so any ODR plugin-cfg generation that was configured should be disabled when enabling the high availability plugin-cfg generation service. See Configuring an on demand router to dynamically update the Web server plug-in configuration for more information.

About this task

Define a set of custom properties at the cell level for each plugin-cfg.xml file that you want to generate. The custom properties are formatted as ODCPluginCfg<property>_<config>=value, where <property> is one of the following elements:
  • OdrList
  • OutputPath
  • UpdateScript
  • OdrClusterList
  • Disabled
The <config> variable is the name of the configuration that you choose. As a result, the properties end in the same <config> variable to define a single configuration for the generation of the high availability plugin-cfg.xml file.

Procedure

  1. In the administrative console, click System administration > Cell > Custom Properties > New.
  2. Define the following custom properties:
    ODCPluginCfgOdrList_<configName>=cell1:node1:odr1,cell2:node2:*
    This property specifies the ODRs that you want to include in the plugin-cfg.xml file. Use the * symbol as a valid wildcard for each path segment.
    ODCPluginCfgOutputPath_<configName>=/path/file_name.txt
    This property specifies the location in which the plugin-cfg.xml file is placed after the file is generated. Because you can generate the plug-in configuration on any node in the cell, you must ensure the output directory exists on each node.
    ODCPluginCfgUpdateScript_<configName>=/path/script <parameter1> <parameter2>
    This property runs a script to update the configuration each time the plugin-cfg.xml file changes. Because you can generate the plug-in configuration on any node in the cell, the script must exist in this path on all nodes.
    ODCPluginCfgOdrClusterList_<configName>=cell1:cluster1
    This property specifies a cluster of ODRs that you want to include in the plugin-cfg.xml file.
    ODCPluginCfgDisable_<configName>=true
    This optional property disables the generation of a particular configuration without undefining all of the properties for that configuration.
    ODCPluginCfgOdrSessionIdCookie _XYZ
    Defines the name of the cookie used to maintain IBM HTTP server/ODR affinity when using ODR cell affinity.
    ODCPluginCfgIHSConfigProperties_XYZ
    This property is used instead of configuring JVM properties (as is done during non-HA plugin-cfg generation) to set IBM HTTP server specific configuration properties. The format is PROPERTY_NAME1=value1,PROPERTY_NAME2=value2
    ODCPluginCfgTrustedProxyList_<configName>=trustedproxy1,trustedproxy2
    This property is used to specify the trusted proxies that you want to include in the plugin-cfg.xml file.
    See Controlling the generation of the plugin-cfg.xml file for the list of valid property names and values.

Example

The following cell custom properties demonstrate how to configure the plugin config generation service for a collection of ODRs that are not in an ODR cluster. Note that all properties end with "_1", which ties them together into a single configuration.
Table 1. Custom properties
Property name Property value Description

ODCPluginCfgOdrList_1

myCell:*:*

Generate a plugin that will route to all ODRs in cell 'myCell'.

ODCPluginCfgOutputPath_1

/tmp/plugin-cfg1.xml

Write the generated plugin to the file '/tmp/plugin-cfg1.xml'.

ODCPluginCfgUpdateScript_1

/root/bin/pluginCfgUpdate1

Path to the script which is executed each time '/tmp/plugin-cfg1.xml' is updated.

ODCPluginCfgDisable_1

true

Enable/disable generation of /tmp/plugin-cfg1.xml and execution of /root/bin/pluginCfgUpdate1. The default value is 'true' if this property is not set.

Table 2. Custom properties.

The following cell custom properties demonstrate how to configure the plugin config generation service for a cluster of ODRs named 'myCell/myOdrCluster'. Note that all properties end with "_2" which ties them together into a single configuration.

Property name Property value Description

ODCPluginCfgOdrClusterList_2

myCell:myOdrCluster

Generate a plugin that will route to all ODRs in the 'myOdrCluster' cluster in the 'myCell' cell.

ODCPluginCfgOutputPath_2

/tmp/plugin-cfg2.xml

Write the generated plugin to the file '/tmp/plugin-cfg2.xml'.

ODCPluginCfgUpdateScript_2

/root/bin/pluginCfgUpdate2

Path to the script which is executed each time '/tmp/plugin-cfg2.xml' is updated.

ODCPluginCfgDisable_2

true

Enable/disable generation of /tmp/plugin-cfg2.xml and execution of /root/bin/pluginCfgUpdate2. The default value is 'true' if this property is not set.

ODCPluginCfgODRIncludeStopped_2

true

or

false

Specify to allow the inclusion of stopped ODRs.

What to do next

Because the generation of the plugin-cfg.xml file can occur on any node in the cell, you can determine the specific location in which the generation service is running in one of two ways:

  • In the administrative console, click Runtime Operations > Extended Deployment > Core components. Verify that HAPluginCfgGenerator is displayed in the table.
  • Run the following script:

    wsadmin.sh -f checkODCPluginGenLocation.jacl




Related concepts
Overview of request flow prioritization
Related tasks
Configuring an on demand router to dynamically update the Web server plug-in configuration
Configuring communication between core groups that are in the same cell
Task topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 1:32:42 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1m1/index.jsp?topic=/com.ibm.websphere.ops.doc/info/odoe_task/thaplugincfg.html