PQ68756, 4.0.4, 4.0.5: Add a tag to the
server-cfg.xml file to location
Downloadable files
Abstract
WebSphere AEs does not allow a user to define the filename
or location for the plugin-cfg.xml when generated from the console.
Download Description
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>
Prerequisites
None
Installation instructions
Please refer to the readme for detailed installation
instructions.