Add application files

We can change or add application files on appservers without having to stop the server and start it again.

There are several changes that we can make to deployed application 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 the application files. Other ways are easier and hot deployment is appropriate only for experienced users. You can use the update wizard of the admin 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 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.

Table 1. Available changes to deployed application files

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

 

• Update an existing application on a running server by providing a new EAR file.

  Reinstall an updated application using the admin 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 the application and prompt you for additional binding data that might be needed to install the application. The reinstallation process automatically stops and restarts the application on the appropriate servers.

• Add a new application to a running server.

  Install an application using the admin 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 admin console to stop the application and then uninstall it. Or use the stopApplication attribute of the AdminControl object with wsadmin and then run the uninstall command.

• Change or add files to existing EJB or Web modules.

  1. Update the application files in the APP_ROOT location.

  2. Restart the application.

     Use the admin console to restart the application. Or use the startApplication and stopApplication attributes of the AdminControl object with wsadmin.

• Change the application.xml file for an application.

  Restart the application. Automatic reloading will not detect the change. Use the admin console to restart the application. Or use the startApplication and stopApplication attributes of the AdminControl object with wsadmin.

• Change the ibm-app-ext.xmi file for an application.

  Restart the application. Automatic reloading will not detect the change. Use the admin console to restart the application. Or use the startApplication and stopApplication attributes of the AdminControl object with wsadmin.

• Change the ibm-app-bnd.xmi file for an application.

  Restart the application. Automatic reloading will not detect the change. Use the admin console to restart the application. Or use the startApplication and stopApplication attributes of the AdminControl object with wsadmin.

• Change a non-module Jar file contained in the EAR file.

  1. Update the non-module Jar file in the APP_ROOT location.

  2. If automatic reloading is not enabled, restart the application. Use the admin console to restart the application. Or use the startApplication and stopApplication attributes of the AdminControl object with wsadmin.

     If automatic reloading is enabled, you do not need to take further action. Automatic reloading will detect the change.

 

Related tasks

Hot deployment and dynamic reloading
Install enterprise apps using scripting
Starting applications with scripting
Stopping applications with scripting
Uninstall enterprise apps with wsadmin