Generating the plug-in configuration in a high availability environment

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 Configure communication between core groups that are in the same cell for more information.
Generating the plugin-cfg.xml file in a high availability environment does not replace configuring an on demand router (ODR) to generate the plugin-cfg.xml file. If you previously configured an ODR to generate the file, and then enable the high availability generation service, both processes run until you turn off the ODR generation service. See Configure 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 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

In the administrative console, click System administration > Cell > Custom Properties > New.
Define the following custom properties:

ODCPluginCfgOdrList_<configName>=cell1:node1:odr1,cell2:node2:*

This property specifies the ODRs 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, define the output path 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 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.

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

Configure an on demand router to dynamically update the Web server plug-in configuration Configure communication between core groups that are in the same cell