PQ68756: WEBSPHERE AES DOES NOT ALLOW A USER TO DEFINE THE FILENAME OR LOCATION FOR THE PLUGIN-CFG.XML WHEN GENERATED FROM THE CONSOLE. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer is using several server-cfg.xml files for development and each developer is deploying applications. When they use the regenerate plugin option from the console, it always writes to the default plugin-cfg.xml file. The customer has used the command line option GenPluginCfg.bat -outputFile, but does not see this as a solution, since they are encouraging their developers to use the admin console.Local fix Using the command line option: GenPluginCfg -configFile server-cfg.xml -outputFile c:\temp . This will write the plugin-cfg.xml file to the c:\temp directoryProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Single Server * * installations with multiple instances * * of WebSphere installed. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere's web-based adminstrative * * console does not provide the * * option to write the plugin-cfg.xml * * file to an alternate directory similar * * to the command line program * * GenPluginCfg. bat/sh . * **************************************************************** * RECOMMENDATION: * **************************************************************** Customer is requesting the same config option in the admin console as what exists via the command line program GenPluginCfg. sh/bat to change the default location for writing the plugin-cfg.xml file (-outputFile). Since customer has configured mulitple instances for one installation of WebSphere, they are unable to regenerate the plugin-cfg.xml file for each node without overwritting the prior nodes file.Problem conclusion To allow the web-based administrative console to also write to a configurable directory, WebSphere has added a new pathMap configuration parameter inside of server-cfg.xml to duplicate the behavior permitted by the command line utility for regenerating the plugin. symbolicName = "PLUGIN_CFG_ROOT" path = " DIRECTORY_TO_WRITE_FILE " Sample server-cfg.xml file... <pathMap xmi:id='PathMap_1'> <entries xmi:id='PathMapEntry_1' symbolicName='APP_INSTALL_ROOT' path='${WAS_ROOT}/installedApps' description='The filesystem path to the directory which will contain installed enterprise applications.'/> <!-- removed extra entries for this sample--> <entries xmi:id='PathMapEntry_7' symbolicName='PLUGIN_CFG_ROOT' path='C:\temp' description='The filesystem path to write the plugin-cfg.xml'/> </pathMap>Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ68756
IBM Group: Software Group
Modified date: Dec 16, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.