GenPluginCfg command
The GenPluginCfg command is used to regenerate the WebSphere Web server plug-in configuration file, plugin-cfg.xml.
understand its implications.
Syntax
To regenerate the plug-in configuration perform one of the following:
- Click on Servers > Web Servers in the admin console, select a Web server and then click Generate Plug-in.
- Issue the following command:
APP_ROOT/bin/GenPluginCfg.sh|batBoth methods for regenerating the plug-in configuration create a plugin-cfg.xml file in ASCII format, which is the proper format for execution in a distributed environment.
Use the -profileName option to define the profile of the appserver process in a multi-profile installation. The -profileName option is not required for running in a single profile environment. The default for this option is the default profile.
When the GenPluginCfg command is issued with the option -webserver.name webservrName, wsadmin generates a plug-in configuration file for the Web server. The settings in the generated configuration file are based on the list of applications that are deployed on the Web server. When this command is issued without the option -webserver.name webservrName, the plug-in configuration file is generated based on topology.
Parameters
The following options are available for the GenPluginCfg command:
- -config.root configroot_dir
- Defaults to CONFIG_ROOT. The setupCmdLine command is invoked to get this environment variable.
- -profileName
- Defines the profile of the appserver process in a multi-profile installation. The -profileName option is not required for running in a single profile environment. The default for this option is the default profile.
- -cell.name cell
- Defaults to WAS_CELL. The setupCmdLine command is invoked to get this environment variable.
- -node.name node
- Defaults to WAS_NODE. The setupCmdLine command is invoked to get this environment variable.
- -webserver.name webserver1
- Required for creating plug-in configuration file for a given Web server.
- -propagate yes/no
- Applicable only when the webserver.name option is specified and the Web server is local. Otherwise, manually copy the plugin-cfg.xml file from APP_ROOT/profiles/profile_name/config\cells\cell_name\nodes\node_name\servers\web_server_name to PLUGINS_ROOT/config/web_server_name in the remote Web server plugins directory. The default value is no.
- -propagateKeyring yes/no
- Applicable only when the option webserver.name is specified and the Web server is local. Defaults to no.
- -cluster.name cluster1,cluster2 | ALL
- Optional list of clusters. Ignored when the option webserver.name is specified.
- -server.name server1,server2
- Optional list of servers. Required for single server plug-in generation. Ignored when the option webserver.name is specified.
- -output.file.name file_name
- Defaults to the configroot_dir/plugin-cfg.xml file. Ignored when the option webserver.name is specified.
- -destination.root root
- Installation root of the machine configuration is used on. Ignored when the option webserver.name is specified.
- -destination.operating.system windows/unix
- Operating system of the machine configuration is used on. Ignored when the option webserver.name is specified.
- -debug yes/no
- Defaults to no.
- -help
- Prints a usage statement.
- -?
- Prints a usage statement.
Usage scenario
To generate a plug-in configuration for all of the clusters in a cell:
GenPluginCfg -cell.name NetworkDeploymentCellTo generate a plug-in configuration for a single server:
GenPluginCfg -cell.name BaseApplicationServerCell -node.name appServerNode -server.name appServerNameTo generate a plug-in configuration file for a Web server:
GenPluginCfg -cell.name BaseApplicationServerCell -node.name webserverNode -webserver.name webserverName
Related tasks
Use command line tools