|
Problem(Abstract) |
After updating a previously installed application,
settings such as classloader and shared libraries associated with this
application have been reset. |
|
|
|
Resolving the
problem |
Background:
An application update in WebSphere Application Server is performed by:
- Uninstalling the Enterprise Application (EAR), then
- Installing the EAR
The wsadmin utility and the admin console will merge binding information
from the old enterprise application with the enterprise application to
avoid loss of information. For example, JNDI names of EJBs, EJB references
and resource references should be preserved, so that it is only necessary
to input this information when the Enterprise Application is first
deployed.
After installing the application, wsadmin may be used to update the
configuration. Changes include adding shared libraries and setting
classloader attributes.
Problem:
Since this is not the initial install, the information is NOT saved in a
way that is usable to the merge tool. As a result, during the application
uninstall configuration changes made after the install are lost.
Therefore, the binding information is successfully merged during an
update, but subsequent configuration changes are not preserved.
Solution:
- Plan configuration settings prior to installation.
- Perform all needed configuration setting changes during
installation.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|