Plugin-cfg.xml file and synchronization
 Technote (troubleshooting)
 
Problem(Abstract)
During synchronization, does the plugin-cfg.xml file get propagated to all the nodes in the cell? How can I ensure that manual edits that I have made to the plugin-cfg.xml are not overwritten during regeneration?
 
Resolving the problem
The plugin-cfg.xml file is only propagated to the nodes from the deployment manager during a full resynchronization. This occurs during startup of the nodeagent by default (it can be disabled) or during a Full Resynchronization. You can initiate a full resynchronization using the Full Resynchronization button on the administrative console.
The plug-in configuration regen is designed so that the plug-in config file can be written to any location. No repository APIs touch the plugin-cfg.xml file. The only information that is propagated during a normal synchronization is the new items that the repository APIs marked since the previous synchronization.

Consider the following scenario:

APAR PQ74656 (defect 154126) ensures that if the plug-in configuration file was edited manually, then those changes will be retained when the plug-in regeneration occurs.
APAR PQ74656 cannot avoid changes getting overwritten when node sync occurs.

The plug-in configuration file is directly read by the HTTP plug-in, so it must identify the exact location for the log file that is specified in the plug-in configuration file.

Typically, the plug-in configuration file is generated by the deployment manager node first. The location of the file is $WAS_HOME\config\cells\plugin-cfg.xml. When node synchronization occurs, this file gets propagated to all the nodes in the cell. If changes are made manually to the plug-in configuration file on the node, they are overwritten.

There are two ways to avoid this:
  1. Make any manual updates to the plug-in configuration file on the deployment manager node. This plug-in file is replicated to the other nodes in the cell during a regen of the plug-in.
  2. Make any manual updates to the plug-in config file on the node, then move the file to a location other than the repository (for example, $WAS_HOME\plugins\plugin-cfg.xml). The new location of the plug-in config file should be reflected in the Web server configuration file. For IBM HTTP Server and Apache, update httpd.conf.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1141952
IBM Group: Software Group
Modified date: Jun 25, 2004