WAS v8.5 > Administer applications and their environment > Deploy 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.

Before you update the application files on a server, ensure the files are assembled in deployable modules.

Next, refer to Ways to update enterprise application files and decide how to update the application files. We can update enterprise applications or modules using the dmgr console, wsadmin, or Java MBean programming. These ways provide similar updating capabilities.

Further, ensure the updated files can be installed to your deployment targets. This topic describes how to update deployed applications or modules using the dmgr console.

  1. Back up the installed application or module.

    1. Go to the Enterprise applications page of the dmgr console.

      Click Applications > Application Types > WebSphere enterprise applications in the console navigation tree.

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

      Select the application 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. The Preparing for application update page is displayed.

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

    1. Ensure that Application to be updated refers to the application to be updated.

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

      The online help Prepare for application update settings provides detailed information on the options.

      We cannot add, remove, or modify a Java Application Programming Interface (API) for XML-Based Web Services (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.

  4. 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. Refer to information on installing applications using the console and on the Preparing for application installation binding settings page for guidance.

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

  5. Click Finish.

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

    Use the page accessed from the Enterprise applications page.

    1. Go to the Manage modules page. Click 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 v7.x or later nodes. We can deploy Java EE 6 modules to servers 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.

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

  1. Save the changes to your configuration.

    When you update a full application in the single server (base) 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.

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

    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, you must 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.

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


Related concepts:

Ways to update enterprise application files
Installable enterprise module versions


Related


Export enterprise applications
Export enterprise application files
Install enterprise application files with the console
Troubleshooting deployment
Update enterprise application files
Manage dmgr console applications using wsadmin.sh
Update installed applications using wsadmin.sh
Manage applications through programming


Reference:

Enterprise application page
Prepare for application update settings
Prepare for application installation binding settings
Application server settings


Related information:

Fine-grained recycle behavior


+

Search Tips   |   Advanced Search