|
Problem(Abstract) |
When using the Update Installer to remove IBM® WebSphere®
Application Server fixes and fix packs, changes you have made to
configuration files can be lost. |
|
|
|
Resolving the
problem |
This behavior is by design.
For example:
You have a system running WebSphere Application Server V5.1 You then
apply Fix Pack 1 (V5.1.1) with the Update Installer. The Update Installer
not only updates files, but also backs up any necessary configuration
files for each component.
In the preceding example, if you decide to downgrade the V5.1.1
installation back to V5.1, you can be assured that the files that are
restored are at the V5.1 level. However, responsibility resides with you
to backup files for which you make manual changes. Therefore, the manual
changes can be reapplied when restoring to a previous level.
You can compare this to a standard operating system backup, which is
similar to what the UNINSTALL fix pack process performs, RESTORE a
previous state. As with backups, if after taking a backup the previous
week you were to make manual changes to files, and you want to keep those
changes after you do your restore, you must go to the effort of copying
those files to replace them AFTER the file system restore is done. It will
work exactly the same way with a WebSphere Application Server "restore"
using the uninstall of the fix pack by way of the Update Installer. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|