Change the HTTP plug-in configuration

 

+

Search Tips   |   Advanced Search

 

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

See Ways to update enterprise application files and determine whether hot deployment is the appropriate way for you to update the HTTP plug-in configuration.

The following table lists the changes that we can make to the HTTP plug-in configuration.

Change	Hot deployment	Dynamic reloading
Change the context root of a WAR file.	Yes	No
Change servlet mappings.	Yes	Yes
Change HTTP transports and virtual hosts	Yes	Yes

 

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.

   We can also run GenPluginCfg.sh or issue a wsadmin command to regenerate the plug-in configuration file.

 

Change servlet mappings.

1. Change web.xml.

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

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

   If the Web app 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 HTTP transports and virtual hosts

1. Change server.xml or virtualhost.xml.

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.

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

 

Related tasks

Hot deployment and dynamic reloading
Getting started with scripting

 

Related

Web server plug-in properties