Updating applications consists of adding a new file or module to
an installed application, or replacing or removing an installed application,
file or module.
About this task
This topic describes how to update deployed applications or modules
using the administrative console.
Procedure
- Back up the installed application.
- Go to the Enterprise
Applications page of the administrative console. Click in the console navigation tree.
- Export
the application to an EAR file. Select the application and
click Export. Exporting preserves the binding information.
Optionally, you can click Export File and
export a file in the application.
- With the application selected on the Enterprise Applications page, click Update.
The Preparing for application update page is displayed.
- Under Specify the EAR, WAR, JAR or
SAR module to upload and install:
- Ensure that Application to be updated refers
to the application to be updated.
- Under Application update options,
select the installed application, module, or file that you want to update.
The online help Preparing
for application update settings provides detailed information on the
options.
- If you selected the Replace the entire application or Replace or add a single module option:
- Click Next to display a wizard for updating
application files.
- Complete the steps in the update wizard.
This
update wizard, which is similar to the installation wizard, provides fields
for specifying or editing application binding information. Refer to information
on installing applications and
on the settings page for
application installation for guidance.
Note that the installation
steps have the merged binding information from the new version and the old
version. If the new version has bindings for application artifacts such as
EJB JNDI names, EJB references or resource references, then those bindings
will be part of the merged binding information. If new bindings are not present,
then bindings are taken from the installed (old) version. If bindings are
not present in the old version and if the default binding generation option
is enabled, then the default bindings will be part of the merged binding information.
You
can select whether to ignore bindings in the old version or ones in the new
version.
- Click Finish.
- If you did not use the Manage modules page
of the update wizard, after updating the application, map the installed application
or module to servers or
clusters.
Use the Manage modules page
accessed from the Enterprise Applications page.
- Go to the Manage modules page.
Click > Manage modules.
- Specify the application server where you want to install modules
contained in your application and click OK.
On
single-server products, you can deploy J2EE 1.4 modules to servers on Version
6.x nodes only.
On
multiple-server products, you can deploy J2EE 1.4 modules to servers on Version
6.x nodes or to clusters that contain cluster members on Version 6.x nodes
only.
Results
After replacement of a full application, the old application is uninstalled.
After replacement of a module, file or partial application, the old installed
module, file or partial application is removed from the installed application.
What to do next
After the application file or module installs successfully, do the
following:
- If a changed
application or module is deployed on a cluster, roll out the changes to all
cluster members of the cluster on which the application or module is deployed.
Click Rollout Update on the Enterprise Applications page to propagate the changed
configuration on all cluster members of the cluster on which the application
or module is deployed. Rollout Update sequentially
updates the configuration on the nodes that contain cluster members.
Tip: At the end of the
Installing messages displayed by the console
during application or module installation, click
Manage applications to
go to the
Enterprise Applications
page. Do not save changes to your configuration until after you roll
out the changes.
- Save the changes to your configuration.
When you update a full application
in a single-server product, after you save the changes, the old version of
the application is uninstalled and the new version is installed into the configuration.
The application binaries for the old version are deleted from the destination
directory and the new binaries are copied to the directory.
In
a multiple-server product, after you click Save the
old application files are deleted and new files are copied when the configuration
on the deployment manager synchronizes with the configuration on the node
where the application is installed.
If
the application is running when you update it, the application stops running
before its files are copied to the destination directory of the node and restarts
after the copy operation completes. Thus, the application is unavailable on
the node during the time the node is synchronizing its configuration with
the deployment manager.
- If needed, restart the
application manually so the changes take effect.
If the application
is updated while it is running, the product automatically stops the application
or only its changed components, updates the application logic, and restarts
the stopped application or its components. 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.
- If the application you are updating is deployed on a
server that has its application class loader
policy set to Single, restart the server.