InfoCenter Home >
6: Administer applications >
6.5: Maintaining and updating applications

6.5: Maintaining and updating applications

This section includes information about monitoring daily operations and the health of applications, updating applications, and performing necessary tasks after updating an application (such as stopping a process and starting it again).

What to do if an enterprise bean JAR file changes

After changing the enterprise bean, the developer provides a replacement JAR file to the administrator. The administrator adds the file to the WebSphere administrative domain.

If the administrator treats the JAR file as a new one, the administrator can install the deployed file into a running application server without having to stop the server and start it again.

The administrator should delete the old JAR file from the WebSphere directories so that there is no chance it will be used. If the administrator treats the JAR file as a replacement for an existing one, the administrator must stop the application server on which the bean is running and start it again after installing the replacement JAR file.

Go to previous article: Installing application files Go to next article: Actions that require a restart

 

 
Go to previous article: Installing application files Go to next article: Actions that require a restart