Updating an application in a production cell has to be done in a controlled, repeatable manner, and the product supports this through its administrative interfaces. The administrative console includes an update wizard, available from the enterprise application list, that lets the administrator replace the whole application, a single module, a single file, or part of the application, with the changes synchronised to the nodes. The wsadmin scripting client provides the same capability through AdminApp.update, which is suited to automation and to release procedures that must be scripted. Options D and E are correct.
The other approaches are intended for development or are not controlled enough for production. Hot deployment, option A, refers to placing files directly in the deployed application directory, a technique that is not supported for production. Dynamic reloading, option B, refreshes classes when files change on disk and, again, is a development convenience; in production it may be turned off. Monitored directories, option C, install applications automatically when the archive is dropped into a folder, and they apply default bindings and give no control over the process, so the facility is suitable for test environments.
In production, administrators generally combine the console or wsadmin update with a rolling restart of cluster members, so the application stays available. A backup of the configuration beforehand allows a rollback if the update has unwanted effects.
[Reference: Updating enterprise applications; AdminApp.update; Hot deployment and dynamic reloading; Monitored directory.]
Submit