Changing or adding application files

Why and when to perform this task

You can change or add application files on application servers without having to stop the server and start it again. This file describes--

Updating 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

Adding 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

Removing 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 wsadmin stopApplication command and then the uninstall command.

Hot deployment Yes
Dynamic reloading No

Changing or adding files to existing EJB or Web modules

  1. Update the application files in the application_root location.
  2. Restart the application. Use the administrative console to restart the application. Or run the wsadmin stopApplication and startApplication commands.
Hot deployment Yes
Dynamic reloading No

Changing 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 wsadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Changing 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 wsadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Changing 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 wsadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Changing a non-module Jar file contained in the EAR file

  1. Update the non-module Jar file in the application_root location.
  2. If automatic reloading is not enabled, restart the application. Use the administrative console to restart the application. Or run the wsadmin 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



Searchable topic ID:   trun_app_hotupgrade_app
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_app_hotupgrade_app.html

Library | Support | Terms of Use | Feedback