You can change or add application files on application servers without having to stop the server and start it again.
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.
sptcfgThere are several changes that you can make to deployed application files without stopping the server and starting it again.
The following table lists the changes that you can make by manipulating an application file on the server where the application is deployed. The table also states whether you use hot deployment or dynamic reloading to make the changes.
Change | Hot deployment | Dynamic reloading |
---|---|---|
Update an existing application on a running server by providing a new EAR file. | Yes | Yes |
Add a new application to a running server. | Yes | No |
Remove an existing application from a running server. | Yes | No |
Change or add files to existing EJB or web modules. | Yes | No |
Change the application.xml file for an application. | Not applicable | Yes |
Change the ibm-app-ext.xmi file for an application. | Not applicable | Yes |
Change the ibm-app-bnd.xmi file for an application. | Not applicable | Yes |
Change a non-module Jar file contained in the EAR file. | Yes | Yes |
In this information ... | IBM Redbooks, demos, education, and more(Index) |