Change the HTTP plug-in configuration

 

You can change the HTTP plug-in configuration without having to stop the server and start it again. This file describes--

  1. Change the application.xml file to change the context root of a WAR file
  2. Change the web.xml file to modify a servlet mapping
  3. Change the server.xml file to modify an HTTP transport or changing the virtualhost.xml file to modify a virtual host alias

 

Change the application.xml file to change the context root of a WAR file

  1. Change the application.xml file.

  2. Regenerate the plug-in configuration file using the administrative console or by running the GenPluginCfg.bat/sh script.

Hot deployment Yes
Dynamic reloading No

 

Change the web.xml file to modify a servlet mapping

  1. Change the web.xml file.

  2. Regenerate the plug-in configuration file using the administrative console or by running the GenPluginCfg.bat/sh script.

    If the web application (.war) has file serving enabled or has a servlet mapping of /, you do not have to regenerate the plug-in configuration. In all other cases the regeneration is required.

Hot deployment Yes
Dynamic reloading Yes

 

Change the server.xml file to modify an HTTP transport or changing the virtualhost.xml file to modify a virtual host alias

  1. Change the server.xml file to add, remove, or modify an HTTP transport or change the virtualhost.xml file to add or remove a virtual host or to add, remove, or modify a virtual host alias.

  2. Regenerate the plug-in configuration file using the administrative console, by running the GenPluginCfg.bat/sh script, or by running a wsadmin command.

Hot deployment Yes
Dynamic reloading Yes

 

See Also

Hot deployment and dynamic reloading