InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.45: Administering WebSphere plug-ins for Web servers >
6.6.45.6: Regenerating the Web server plug-in configuration

6.6.45.6: Regenerating the Web server plug-in configuration

Sometimes you might want to trigger (manually) the WebSphere plug-in to regenerate its configuration. For example, you might installed or removed an enterprise application, or added or removed servlets and mappings from a particular application. Failure to regenerate the plug-in after introducing a new application will likely result in a "404 File Not Found" error when a user tries to access the new Web application.

  This task can overwrite manual configuration changes that you might want to preserve instead. Before performing this task, understand its implications as described in the article about administering Web server plug-ins.

You can run the following script:

product_installation_root/bin/GenPluginCfg.sh|bat

You can also use the administrative node to manually trigger an update of the configuration for the WebSphere plug-in for the Web server you are using:

  1. Locate the node in the tree view.
  2. Right-click it, then select Regen Webserver Plugin.

To configure automatic regeneration:

  1. Display the application server properties.
  2. Select the Custom tabbed page.
  3. Edit Automatic Generation of Plug-in.
  4. Save your changes.
Go to previous article: Controlling where the WebSphere plug-ins for Web servers are installed Go to next article: What to do after changing Web server ports

 

 
Go to previous article: Controlling where the WebSphere plug-ins for Web servers are installed Go to next article: What to do after changing Web server ports