You can update application files deployed on a server or cluster in several ways.
| Option | Method | Comments | Starting after update |
|---|---|---|---|
| Administrative console update wizard | Briefly, do the following:
1. Go to the Enterprise Applications page. Click Applications > Enterprise Applications in the console navigation tree. 2. Select the application to update and click Update. 3. On the Preparing for application update page, identify the application, module or files to update and click Next. 4. Complete steps in the update wizard and click Finish. | On the Preparing
for application update page:
• Use Full application to update an .ear file. • Use Single module to update a .war, .sar, enterprise bean .jar, or connector .rar file. • Use Single file to update a file other than an .ear, .war, .sar, EJB .jar, or .rar file. • Use Partial application to update or remove multiple files. | On the Enterprise Applications page, select the updated application and click Start. |
| wsadmin scripts | Use the update command or the updateInteractive command in a script or at a command prompt. For more information on the update and updateInteractive commands, see the Commands for the AdminApp object topic. | Getting started with scripting provides an overview of wsadmin. | Start the application using the invoke command and the startApplication attribute. For more information about the invoke command, see the Commands for the AdminControl object topic. |
| Java application programming interfaces
See Using administrative programs (JMX). | Update deployed applications by completing the steps in Managing applications through programming. | Update an application in the following ways:
• Update the entire application • Add to, replace or delete multiple files in an application • Add a module to an application • Update a module in an application • Delete a module in an application • Add a file to an application • Update a file in an application • Delete a file in an application |
• Invoke the AdminApp startApplication command. • Invoke the startApplication method on an ApplicationManager MBean using AdminControl. |
| WebSphere rapid deployment
See topics under Rapid deployment of J2EE applications in this information center. | Briefly, do the following:
1. Update your J2EE application files. 2. Set up the rapid deployment environment. 3. Create a free-form project. 4. Launch a rapid deployment session. 5. Drop your updated application files into the free-form project. | WebSphere rapid deployment offers the following
advantages:
• You do not need to assemble your J2EE application files prior to deployment. • You do not need to use other installation tools mentioned in this table to deploy the files. | Use any of the above options to start the application. Clicking Start on the Enterprise Applications page is the easiest option. |
| Hot deployment and dynamic reloading | Briefly, do the following:
1. Update your application (.ear), Web module (.war), enterprise bean .jar or HTTP plug-in configuration file. 2. Follow instructions in Hot deployment and dynamic reloading to update your file. | If you are new to WebSphere Application Server,
use the administrative
console to update applications. That option is easier.
Hot deployment and dynamic reloading is more difficult to complete. You must directly manipulate the application or module file on the server where the application is deployed. | Use any of the above options to start the application. Clicking Start on the Enterprise Applications page is the easiest option. |
You can update .ear, enterprise bean .jar, Web module .war, Session Initiation Protocol (SIP) module (.sar), connector .rar, application client .jar, and any other files used by an installed application.
If the application is updated while it is running, WebSphere Application Server automatically
stops the application, updates the application logic and restarts the application.
If the application does not start automatically, start it manually using one
of the Starting options. For more information on the restarting of
updated applications, refer to Fine-grained recycle behavior in IBM
WebSphere Developer Technical Journal: System management for WebSphere Application
Server V6 -- Part 5 Flexible options for updating deployed applications.