Changing the HTTP plug-in configuration
You can change the HTTP plug-in configuration without having to stop the server and start it again.
About this task
Restriction: The hot deployment and dynamic reloading function
is not supported when the product is running on these operating systems. The Java archive (JAR)
files within the associated Java Development Kit (JDK) are memory mapped. If these JAR files are
updated by the hot deployment and dynamic reloading functionality when they are being used by the
Java virtual machine (JVM), the files become inconsistent, which results in an application server
crash. When you make changes to an application on these operating systems, do not use the hot
deployment and dynamic reloading functionality. Instead, restart the application to reflect the
changes.
There are several change that you can make to the HTTP plug-in configuration without stopping the server and starting it again.
Important: See Ways to update enterprise 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.
Change | Hot deployment | Dynamic reloading |
---|---|---|
Change the application.xml file to change the context root of a web application archive (WAR file). | Yes | No |
Change the web.xml file to add, remove, or modify a servlet mapping. | Yes | Yes |
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. | Yes | Yes |
Avoid trouble: The following steps reference the
GenPluginCfg.bat/sh script. You must delete the plugin-cfg.xml file in
the profile_root/config/cells directory before you use
the GenPluginCfg.bat/sh script. Otherwise, configuration changes do not persist to the
plugin-cfg.xml file.