Change or add application files

You can change or add application files on an application server without stopping and restarting the server. You can perform any of these updates while the application server is running:

• Update an application on a running server (provide a new EAR file)

• Add a new application to a running server

• Remove an application from a running server

• Add a new Web module to an existing, running application

• 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

The variable application_root represents the directory that contains the expanded application files. See step 1 on Use hot deployment and dynamic reloading for information about the location of the metadata files.

Update an application on a running server (provide a new EAR file)

Use the administrative console or wsadmin to install an updated version of an application.

• Hot deployment: Yes

• Dynamic reloading: Yes

• Restart the application: Not applicable

Add a new application to a running server

Use the administrative console or wsadmin to install a new application.

• Hot deployment: Yes

• Dynamic reloading: No

• Restart the application: Not applicable

Remove an application from a running server

Use the administrative console or wsadmin to stop the application and uninstall it from the server.

• Hot deployment: Yes

• Dynamic reloading: No

• Restart the application: Not applicable

Add a new Web module to an existing, running application

1. Update the application files in the application_root location.

2. Use the administrative console or wsadmin to stop and restart the application.

• Hot deployment: Yes

• Dynamic reloading: No

• Restart the application: Yes

Change the application.xml file for an application

1. Update the application.xml file.

2. Use the administrative console or wsadmin to stop and restart the application. Automatic reloading does not detect changes to this file.

• Hot deployment: Not applicable

• Dynamic reloading: Yes

• Restart the application: Yes

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

1. Update the ibm-app-ext.xmi file.

2. Use the administrative console or wsadmin to stop and restart the application. Automatic reloading does not detect changes to this file.

• Hot deployment: Not applicable

• Dynamic reloading: Yes

• Restart the application: Yes

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

1. Update the ibm-app-bnd.xmi file.

2. Use the administrative console or wsadmin to stop and restart the application. Automatic reloading does not detect changes to this file.

• Hot deployment: Not applicable

• Dynamic reloading: Yes

• Restart the application: Yes

Change a non-module JAR file that is contained in the EAR file

1. Update the JAR file in the application_root location.

2. Update the application.

   • If automatic reloading is not enabled, use the administrative console or wsadmin to stop and restart the application.

   • If automatic reloading is enabled, you do not need to restart the application. Automatic reloading detects the change and updates the application.

• Hot deployment: Yes

• Dynamic reloading: Yes

• Restart the application: If automatic reloading is not enabled