Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Deploy and administering enterprise applications > Update enterprise application files


Update enterprise applications with the console


Updating enterprise applications consists of adding a new file or module to an installed Java EE application, or replacing or removing an installed application, file or module.

  1. Back up the installed application or module.

    1. Go to...

        Applications | Application Types | WebSphere enterprise applications |

      Export the application to an EAR file or export a file in the application.

      Select the application you want to export and click Export or Export File. Exporting preserves the binding information.

  2. With the application selected on the Enterprise applications page, click Update.

  3. Specify the EAR, WAR, SAR or JAR module to upload and install:

  4. Under Application update options, select the installed application, module, or file to update.

    We cannot add, remove, or modify a Java API for JAX-WS annotation using the "Replace or add a single file" or "Replace, add, or delete multiple files" update options. These options change a single file or a partial application. If you change a JAX-WS annotation using either of these options, the product does not return an error. However, you might encounter problems deploying annotated web services.

  5. If you selected the "Replace the entire application" or "Replace or add a single module" option:

    1. Click Next to display a wizard for updating application files.

    2. 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.

      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.

      We can select whether to ignore bindings in the old version or ones in the new version.

  6. Click Finish.

  7. 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 page accessed from the Enterprise applications page.

    1. Go to...

        Applications | Application Types | WebSphere enterprise applications | application_name | Manage modules

    2. Specify the application server where to install modules contained in the application and click OK.

      We can deploy J2EE 1.4 modules to servers on v6 or later nodes. We can deploy Java EE 5 modules to servers on Version 7.x or later nodes. We can deploy Java EE 6 modules to servers on v8.x or later nodes.

      On multiple-server products, you can also deploy modules to clusters.

      • To deploy J2EE 1.4 modules, the clusters must contain cluster members on Version 6 or later nodes.

      • To deploy Java EE 5 modules, the clusters must contain cluster members on v7.x or later nodes.

      • To deploy Java EE 6 modules, the clusters must contain cluster members on v8.x or later nodes.


Results

After replacement of a full application, the product uninstalls the old application. After replacement of a module, file or partial application, the product removes the old installed module, file or partial application from the installed application.


What to do next

After the application file or module installs successfully, do the following:

  1. 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.

    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 the configuration until after you roll out the changes.

  2. Save the changes to the configuration.

    On multiple-server products, after you click Save the product deletes the old application files and copies new files when the configuration on the dmgr 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 dmgr.

  3. 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.

    New feature: If you update module metadata while an application is running, restarting the application might not be sufficient for the changes to take effect. For example, if you change descriptors in running Java EE 6 applications that use annotations, reinstall the application. If you change classes that introduce, remove, or alter class hierarchies within an application, and those changes impact annotated classes, you also must reinstall the application.

  4. If the application you are updating is deployed on a server that has its application class loader policy set to Single on the application server settings page, restart the server.

Ways to update enterprise application files
Installable enterprise module versions
Export enterprise applications
Export enterprise application files
Install enterprise application files with the console
Troubleshoot deployment
Update enterprise application files
Manage administrative console applications using wsadmin.sh
Update installed applications using wsadmin.sh
Manage applications through programming
Enterprise application collection
Prepare for application update settings
Prepare for application installation binding settings
Application server settings
Fine-grained recycle behavior

+

Search Tips   |   Advanced Search