Regenerate the Web server plugin configuration
External Web servers use the Web server configuration file (plugin-cfg.xml) to determine whether or not to route particular URL requests to WebSphere Application Server. When changes are made to WAS configurations, the plugin configuration file may need to be regenerated. If the plugin-cfg.xml file is out of sync with the WebSphere configuration, URL requests may be improperly routed.
Examples of configuration changes that will require regeneration include:
- Installing or removing a web application
- Modifying servlet mappings or the context root in an application
- Altering virtual host aliases
- Changing an application server's transport attribute
Use either of these methods to regenerate the plugin configuration:
Use the administrative console to regenerate the plugin configuration. This method is recommended, but not required, for base application server instances that do not use remote HTTP or Network Deployment.
Use the GenPluginCfg script to regenerate the plugin configuration. This method is recommended, but not required, if you are using remote HTTP or Network Deployment.
The plugin-cfg.xml file contains several optional elements and attributes that are not generated by the GenPluginCfg script or the administrative console. To make changes to these attributes, you can manually edit the plugin-cfg.xml file. See plugin-cfg.xml file for a complete description of the XML elements and attributes of the plugin-cfg.xml file.
See also