Why and when to perform this task
You can update an application deployed on a server. The steps below describe how to update a deployed application using the administrative console.Note: You can also update applications using the wsadmin tool, which provides updating capabilities identical to those available using the administrative console. Further, in some situations, you can update applications without needing to restart the application server.
Steps for this task
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.
If Override existing bindings is selected, then the default bindings (specified using Generate default bindings or a custom bindings file) are chosen over bindings in the new or old EAR file.
You can select whether to ignore bindings in the old version or ones in the new version. Select Use new bindings or Use existing bindings, respectively, instead of Merge old and new bindings. If Use new bindings is selected, only bindings specified in the new EAR file are used. If Generate default bindings is enabled, then the default bindings are merged with the binding information in the new EAR file. If Use existing bindings is selected, only the bindings specified in the old EAR file are used. If Generate default bindings is enabled, then the default bindings are merged with the binding information in the old EAR file. This option is similar to the scripting options -update.ignore.old and -update.ignore.new.
For all applications, including applications that contain Web modules, examine the Reload Enabled and Reload Interval values on the settings page for your enterprise application. If reloading of application files is enabled and the reloading interval is greater than zero (0), the application's files are reloaded after the application is updated.
To enable reloading for only the Web modules in an application, deselect Reload Enabled. Then, in the ibm-web-ext.xmi file for the application, set the reloadingEnabled extension to true and specify a value, in seconds, for the reloadInterval extension. You can set reloadingEnabled to true and specify an integer for reloadInterval when editing your Web module's extended deployment descriptors in an assembly tool.
Note: