Example: Updating the Web server plug-in configuration files using wsadmin
This examples regenerates the web serer plugin configuration file.
- Identify the web server plugin configuraiton file generator MBean and assign it to the pluginGen variable.
set pluginGen [$AdminControl completeObjectName type=PluginCfgGenerator,*]Example output:
WebSphere:cell=pongoNetwork,name=PluginCfgGenerator,mbeanIdentifier=PluginCfgGenerator,type=PluginCfgGenerator,node=pongoManager,process=dmgr- Generate the updated plugin configuration file.
$AdminControl invoke $pluginGen generate "c:/WebSphere/DeploymentManager c:/WebSphere/DeploymentManager/config mycell null null plugin-cfg.xml"This example command assumes a Windows system install. It invokes the generate operation on the MBean, passing in the install root directory, configuration root directory, cell name, node name, server name, and output file name. To pass in null as the value of an argument, enter null as given in the example. This is provided for operation that allows null as the value of its argument and processes null differently from an empty string. In this example, both node and server are set to null. The generate operation generates plugin configuration for all the nodes and servers resided in the cell. The output file plugin-cfg.xml is created in the config root directory.You can modify this example command to generate plugin configuration for a particular node or server by specifying the node and server names.