Why and when to perform this task
You can change the HTTP plug-in configuration without having to stop
the server and start it again. This file describes--
- Changing the application.xml file to change the context root
of a WAR file
- Changing the web.xml file to add, remove, or modify a servlet
mapping
- Changing the server.xml file to add, remove, or modify an HTTP
transport or changing the virtualhost.xml file to add or remove a
virtual host or to add, remove, or modify a virtual host alias
Changing the application.xml file to change the context root of
a WAR file
- Change the application.xml file.
- Regenerate the plug-in configuration
file using the administrative console or by running the GenPluginCfg.bat/sh script.
Hot deployment |
Yes |
Dynamic reloading |
No |
Changing the web.xml file to add, remove, or modify a
servlet mapping
- Change the web.xml file.
- Regenerate the plug-in configuration
file using the administrative console or by running the GenPluginCfg.bat/sh script.
If the Web application 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 |
Changing the server.xml file to add, remove, or modify
an HTTP transport or changing the virtualhost.xml file to add or remove a
virtual host or to add, remove, or modify a virtual host alias
- 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.
- 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 |