Change the HTTP plug-in configuration

 

+

Search Tips   |   Advanced Search

 

Overview

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

There are several change that you can make to the HTTP plug-in configuration without stopping the server and starting it again.

See Ways to update application files and determine whether hot deployment is the appropriate way for you to update your HTTP plug-in configuration. Other ways are easier and hot deployment is appropriate only for experienced users.

The following table lists the changes that you can make to the HTTP plug-in configuration. The table also states whether you use hot deployment or dynamic reloading to make the changes.

File Change Hot deployment Dynamic reloading
application.xml Context root of a WAR file Yes No
web.xml Servlet mapping Yes Yes
server.xml file HTTP transport Yes Yes
virtualhost.xml Virtual host or virtual host alias Yes Yes

 

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

  1. Change the application.xml file.

  2. If the plug-in configuration property...

    Automatically propagate plug-in configuration file

    ...is selected for this plug-in, it is automatically regenerated whenever the application.xml file changes.

    You can also run the GenPluginCfg.bat/sh script, or issue a wsadmin command to regenerate the plug-in configuration file.

 

Change the web.xml file to add, remove, or modify a servlet mapping

  1. Change the web.xml file.

  2. If the plug-in configuration property Automatically propagate plug-in configuration file is selected for this plug-in, it is automatically regenerated whenever the web.xml file changes.

    See Web server plug-in properties for information on how to set this property. You can also run the GenPluginCfg.bat/sh script, or issue a wsadmin command to regenerate the plug-in configuration file.

    If the Web application has file serving enabled or has a servlet mapping of /, the plug-in configuration does not have to be regenerated. In all other cases a regeneration is required.

 

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.

  1. Change the server.xml file or the virtualhost.xml file.

  2. If the plug-in configuration property Automatically propagate plug-in configuration file is selected for this plug-in, it is automatically regenerated whenever the server.xml file changes.

    See Web server plug-in properties for information on how to set the this property. You can also run the GenPluginCfg.bat/sh script, or issue a wsadmin command to regenerate the plug-in configuration file.


Hot deployment and dynamic reloading
Getting started with scripting

 

Related Reference

Web server plug-in properties