Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
Environment: ----------- OS: Microsoft Windows 2008 SP2, 32 bit WebSphere Application Server Network Deployment edition V7.0.0.17 migrating to WAS WebSphere Application Server Network Deployment edition V8.0.0.2 Problem description: ------------------- Customer tried to migrate from 7.0.0.17 to 8.0.0.2. The migration was successful, but some of the applications did not get migrated successfully due to the following exception: MIGR0496W: The migration of D:/IBM/WebSphere/32bit/8. 0/profiles/DMGR_DEV/installableApps/WFM_DEV.ear/ terminated unexpectedly. com.ibm.wsspi.migration.document.exceptions.NotFoundException: lib/axis. war [01/18/2012 12:12:39:191 EST] ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=aaaaaa,node=bbbbbb,server =server1 for module lib/axis.war+WEB-INF/web.xml. [01/18/2012 12:12:39:191 EST] com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=aaaaaa,node=bbbbbb,server =server1 for module lib/axis.war+WEB-INF/web.xml. [01/18/2012 12:12:39:191 EST] at com.ibm.ws.management.application.task.ConfigRepoHelper.getServe rNames(C onfigRepoHelper.java:2270) [01/18/2012 12:12:39:191 EST] at com.ibm.ws.management.application.task.ConfigRepoHelper.getAddRe moveServ P erNames(ConfigRepoHelper.java:2175) [01/18/2012 12:12:39:191 EST] at com.ibm.ws.management.application.task.ConfigRepoHelper.getServe rNames(C onfigRepoHelper.java:2048) [01/18/2012 12:12:39:191 EST] at com.ibm.ws.management.application.AppAssociation.getServerNames( AppAssoc iation.java:1293) [01/18/2012 12:12:39:191 EST] at com.ibm.websphere.management.application.AppDeploymentUtil.getNo deInfoFo rTargets(AppDeploymentUtil.java:307) [01/18/2012 12:12:39:191 EST] at com.ibm.ws.management.application.task.ValidateAppTask.performTa sk(Valid ateAppTask.java:219) [01/18/2012 12:12:39:191 EST] at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImp l.java:3 15) P [01/18/2012 12:12:39:191 EST] at java.lang.Thread.run(Thread.java:769) [01/18/2012 12:12:40:191 EST] ADMA5011I: The cleanup of the temp directory for application DWF_STG is complete. It appeared that the migration process did not take into account the possiblity of war modules having paths.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server v8.0 Migration tools with * * applications failing to migrate * **************************************************************** * PROBLEM DESCRIPTION: The generated application install * * scripts fail becuase they have * * incomplete map module settings. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a Web Module's relative location includes a path and it is mapped to more than one location, then the migration code must look up whether it is using a sip.xml or a web.xml META-INF file. This lookup is causing the generated map module information to be incomplete. Thus the application install script is incorrect and will fail.
Problem conclusion
The migration tools now handle these path situations, and gather the complete map module information when creating the application install scripts used for migration. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.3. 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
PM56709
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-25
Closed date
2012-02-07
Last modified date
2012-02-07
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
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 October 2021