Change or add application files
We can change or add application files on application servers without having to stop the server and start it again.
Overview
There are several changes that one can make to deployed application files without stopping the server and starting it again. We can use the update wizard of the administrative console to make the changes without having to stop and restart the server. This article describes how to make the following changes by manipulating an application file on the server where the application is deployed:
- Update an existing application on a running server, providing a new enterprise application (EAR file)
- Add a new application to a running server
- Remove an existing application from a running server
- Change or add files to existing enterprise bean (EJB) or Web modules
- Change the application.xml file for an application
- Change the ibm-app-ext.xmi file for an application
- Change the ibm-app-bnd.xmi file for an application
- Change a non-module Jar file contained in the EAR file
Update an existing application on a running server (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.
Hot deployment Yes Dynamic reloading Yes
Add a new application to a running server
Install an application using the administrative console or the wsadmin install command.
Hot deployment Yes Dynamic reloading No
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.
Hot deployment Yes Dynamic reloading No
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.
Hot deployment Yes Dynamic reloading No
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.
Hot deployment Not applicable Dynamic reloading Yes
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.
Hot deployment Not applicable Dynamic reloading Yes
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.
Hot deployment Not applicable Dynamic reloading Yes
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.
Hot deployment Yes Dynamic reloading Yes
Related Tasks
Hot deployment and dynamic reloading