Fixes are available
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
While migrating from a previous version of WebSphere Application Server to V7.0, the WASPostUpgrade utility may fail with a NotFoundException. The stack trace in the WASPostUpgrade trace indicates the following: com.ibm.ws.migration.utility.UpgradeException: com.ibm.wsspi.migration.document.exceptions.NotFoundException: java.lang.Throwable.<init>(Throwable.java:241) java.lang.Exception.<init>(Exception.java:77) com.ibm.ws.migration.utility.UpgradeException.<init> (UpgradeException.java:42) [... truncated for brevity ...] Caused by: com.ibm.wsspi.migration.document.exceptions.NotFoundException: java.lang.Throwable.<init>(Throwable.java:196) java.lang.Exception.<init>(Exception.java:41) com.ibm.wsspi.migration.document.exceptions.NotFoundException. <init>(NotFoundException.java:56) com.ibm.wsspi.migration.transform.BasicDocumentTransform. getChild(BasicDocumentTransform.java:221) com.ibm.ws.migration.postupgrade.common. ConfigCommonTransactionalDocumentTransform. internalPopulateNodeLevelTransform (ConfigCommonTransactionalDocumentTransform.java:450) com.ibm.ws.migration.postupgrade.common. ConfigCommonTransactionalDocumentTransform. populateNodeLevelTransform (ConfigCommonTransactionalDocumentTransform.java:508) The key highlight is that in the "caused by section", the method calls are ... -> populateNodeLevelTransform -> internalPopulateNodeLevelTransform -> getChild A small number of method calls above this, the message "Populating node level Transforms for level:" appears in the trace. ---------------------------------------------------------------- This occurs when the old product version's configuration contains a node which has no servers (application servers or web server definitions) defined in it. It is essentially an "empty" node.
Local fix
The workaround is to delete the empty node from the old product's configuration, then perform the WASPreMigrate and WASPostMigrate again (or use the migration wizard to perform the migration again). Please be sure to double-check the node to make sure it does not contain any servers before deleting it. If it is not apparent which node is causing the issue, review the WASPostUpgrade trace. Search for the phrase "Populating node level Transforms for level:". That trace data will indicate which node the migration utility was processing when it encountered the failure.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 migration tools * * migrating a standalone server with an * * unmanaged web server. * **************************************************************** * PROBLEM DESCRIPTION: WASPostUpgrade throws an exception * * when it encounters an incompletely * * defined Web Server associated with a * * standalone server. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the Web Server associated with the standalone server is not completely set up, that is no servers were defined, thus no servers directory was found under the node, the WASPostUpgrade command will throw an exception and quit.
Problem conclusion
Web Servers which are not fully defined will not be migrated. The code will detect the missing servers directory, issue a message and continue with the migration of the standalone server. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.25 and 8.0.0.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM53390
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-01
Closed date
2012-03-28
Last modified date
2012-03-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021