You can change or add application files on application servers
without having to stop the server and start it again.
About this task
There are several changes that you can make to deployed application
files without stopping the server and starting it again.
Important: See
Ways to update application files
and determine
whether hot deployment is the appropriate way for you to update your application
files. Other ways are easier and hot deployment is appropriate only for experienced
users. You can
use
the update wizard of the administrative console to make the changes
without having to stop and restart the server.
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.
- Update an existing application on a running server by
providing a new EAR file.
Reinstall an updated application using
the administrative console or
the wsadmin $AdminApp install command with the -update option.
Both
reinstallation methods enable you to update an existing application using
any of the other steps listed in this file, including changing classes, adding
modules, removing modules, changing modules, or changing metadata files. The
application reinstallation methods detect the changes in your application
and prompt you for additional binding data that might be needed to install
the application. The reinstallation process automatically stops and restarts
your application on the appropriate servers.
- Add a new application to a running server.
Install
an application using the administrative
console or the wsadmin install command.
- Remove an existing application from a running server.
Stop the application and then uninstall it from the server. Use the
administrative console to stop
the application and then uninstall
it. Or run the wasadmin stopApplication command and then the uninstall command.
- Change or add files to existing EJB or Web modules.
- Update the application files in the application_root location.
- Restart the application.
Use the administrative
console to restart the application.
Or run the wasadmin stopApplication and startApplication commands.
- Change the application.xml file for an application.
Restart the application. Automatic reloading will not detect the
change. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.
- Change the ibm-app-ext.xmi file for an application.
Restart the application. Automatic reloading will not detect the
change. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.
- Change the ibm-app-bnd.xmi file for an application.
Restart the application. Automatic reloading will not detect the
change. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.
- Change a non-module Jar file contained in the EAR file.
- Update the non-module Jar file in the application_root location.
- If automatic reloading is not enabled, restart the application.
Use the administrative console to restart
the application. Or run the wasadmin stopApplication and startApplication commands.
If automatic reloading is enabled, you do not need to take further
action. Automatic reloading will detect the change.