WAS v8.5 > Administer applications and their environment > Deploy enterprise applications > Update enterprise application files > Hot deployment and dynamic reloading

Change or adding WAR files

We can change web application archives (WAR files) on application servers without having to stop the server and start it again.

The following note applies to the file references with a .xmi extension in this topic:

For IBM extension and binding files, the .xmi or .xml file name extension is different depending on whether you are using a pre-Java EE 5 application or module or a Java EE 5 or later application or module. An IBM extension or binding file is named ibm-*-ext.xmi or ibm-*-bnd.xmi where * is the type of extension or binding file such as app, application, ejb-jar, or web. The following conditions apply:

However, a Java EE 5 or later module can exist within an application that includes pre-Java EE 5 files and uses the .xmi file name extension.

The ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, and ibm-portlet-ext.xmi files continue to use the .xmi file extensions. sptcfg

Restriction: The hot deployment and dynamic reloading function is not supported when the product is running on these operating systems. The 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 changes that we can make to WAR files without stopping the server and starting it again.

See Ways to update enterprise application files and determine whether hot deployment is the appropriate way for you to update your WAR files. Other ways are easier and hot deployment is appropriate only for experienced users. We can use the update wizard of the dmgr console to make the changes without having to stop and restart the server.

The following table lists the changes that we can make by manipulating a WAR file on the server where the application is deployed. The table also states whether we use hot deployment or dynamic reloading to make the changes.

Available changes to deployed WAR files. Available changes using hot deployment or dynamic reloading.

Change Hot deployment Dynamic reloading
Change an existing JSP file. Not applicable Yes
Add a new JSP file to an existing application. Yes Yes
Change an existing servlet class by editing and recompiling. Not applicable Yes
Change a dependent class of an existing servlet class. Not applicable Yes
Add a new servlet using the Invoker (Serve Servlets by class name) facility or add a dependent class to an existing application. Yes Not applicable
Add a new servlet, including a new definition of the servlet in the web.xml deployment descriptor for the application. Yes Not applicable
Change the web.xml file of a WAR file. Yes Yes
Change the ibm-web-ext.xmi file of a WAR file. Not applicable Yes
Change the ibm-web-bnd.xmi file of a WAR file. Not applicable Yes


Related


Hot deployment and dynamic reloading
Start applications using wsadmin.sh
Stopping applications using wsadmin.sh


+

Search Tips   |   Advanced Search