Update applications using the console


You can update a deployed application using the console, with the AdminAapp command, or with dynamic reloading. To update a deployed application using the console:

  1. Go to...

    Applications | Enterprise Applications

  2. Back up the application.

    Place a checkmark in the check box beside the application and click Export to export the application to an EAR file and preserve the binding information.

  3. With a checkmark beside the application, click Update.

  4. Complete the steps in the Preparing for application update page and the pages that follow it.

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

  5. Map the installed application or module to servers.

    Use the Map modules to appservers page of the Install New Application pages displayed during updating the application. Or, after updating the application, use the Map modules to appservers page accessed from the Enterprise Applications page.

    1. Go to...

      Applications | Enterprise Applications | application name | Map modules to appservers

    2. Specify the appserver where you want to install modules contained in your application and click OK.

  6. Click Save on the administrative console taskbar to save the changes to your configuration.

    In the single server (base) product, after you click Save 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.

  7. Examine the values specified for Reload Enabled and Reload Interval on the settings page for your enterprise application.

    If reloading of application files is enabled and the reload interval is greater than zero (0), the application's files are reloaded after the application is updated. For Web modules such as servlets and JSP files, a Web container reloads a Web module only when the IBM extension reloadingEnabled in the ibm-web-ext.xmi file is also set to true. Set reloadingEnabled to true when editing your Web module's extended deployment descriptors in an assembly tool.

  8. Restart the application so the changes take effect.

    If the application is updated while it is running, WAS stops the application, updates the application logic and restarts the application.

    1. Click Applications > Enterprise Applications in the console navigation tree to go to the Enterprise Applications page.

    2. Check the check box for the updated application.

    3. Click Start.

  9. (Optional)   If the application you are updating is deployed on a server that has its application class loader policy set to SINGLE, restart the server.


See Also

Deploying and managing applications
Deploying and managing using scripting