PQ60077: REGEN OF PLUGIN OVERWRITES MANUAL EDITS OF PLUGIN-CFG.XML ATTRIBUTES. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description If plugin-cfg.xml attributes such as RefreshInterval and RetryInterval are modified then the regeneration of the plug-in will overwritethe manual modifications. Regeneration of the plug-in should behave in the following manner: 1. If the existing plugin-cfg.xml does not have any parameters such as RefreshInterval explicitly set then the regenerated config file does not need them either. 2. If the existing config file does have global parameters such as RefreshInterval then the regenerated config should preserve them. 3. If the existing config files does have app. server specific parameters such as RetryInterval or LoadBalance set, the regenerated config should preserve them. 4. If a new app server (or clone) has been added to the domain, then the regenerated config should use the settings of the previously added server for App Server attributes such as RetryInterval or LoadBalance. (Most likely all previous servers will have the same settings.) In this way one can be sure they will not loose attributes when someone regens the plugin (whether it was needed or not).Local fix none given.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server administrators * * manually modifying the plugin configuration * * xml file. * **************************************************************** * PROBLEM DESCRIPTION: Manual changes to the plugin-cfg.xml * * file are discarded after plugin * * regeneration. * **************************************************************** * RECOMMENDATION: * **************************************************************** After manually modifying the plugin-cfg.xml file and regenerating the webserver plugins, all manual modifications are discarded. This is causing customers to have to reapply manual changes made to the configuration file after each regeneration of the plugins. Since some entries inside plugin-cfg.xml file can only be made manually, the regeneration of the plugins cannot repopulate those updated fields.Problem conclusion Added the ability to restore key fields that may be updated manually after the regeneration of plugins have occured. Please note that this code change does not allow all fields to be manually updated. Future goal is to move all plugin configuration data into the repository or other configuration files so that manual updates should not be required.Temporary fix temporary fix is in wasdoc0Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ60077
IBM Group: Software Group
Modified date: Jul 26, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.