PI86999: ERROR DURING DEPLOYMENT OF POST MIGRATION PROCESS, IF MULTIPLE APPLICATION EDITIONS EXIST; THE BASE EDITION FAILS TO INSTALL

9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• The Migration log contains the following errors:
  
  [08/25/2017 19:19:03:577 EDT] ADMA5058I: Application and module
  versions are validated with versions of deployment targets.
  [08/25/2017 19:19:03:858 EDT] More than one version of BLA named
  WebSphere:blaname=caeser-core-ws exists. Select the version for
  the BLA.
  [08/25/2017 19:19:04:280 EDT]
  com.ibm.websphere.management.exception.
  AdminException: More than one version of BLA named WebSphere:
  blaname=caeser-core-ws exists. Select the version for the BLA.
  [08/25/2017 19:19:04:280 EDT]  at
  com.ibm.ws.management.bla.j2ee.ext.
  tasks.ValidateBLATask._validateBLAInstall(ValidateBLATask.java:3
  15)
  [08/25/2017 19:19:04:280 EDT]  at
  com.ibm.ws.management.bla.j2ee.ext.
  tasks.ValidateBLATask._performTaskAsSystem(ValidateBLATask.java:
  132)
  [08/25/2017 19:19:04:280 EDT]  at
  com.ibm.ws.management.bla.j2ee.ext.
  tasks.ValidateBLATask$1.run(ValidateBLATask.java:104)
  [08/25/2017 19:19:04:280 EDT]  at com.ibm.ws.security.auth.
  ContextManagerImpl.runAs(ContextManagerImpl.java:5489)
  [08/25/2017 19:19:04:280 EDT]  at com.ibm.ws.security.auth.
  ContextManagerImpl.runAsSpecified(ContextManagerImpl.java:5580)
  [08/25/2017 19:19:04:280 EDT]  at
  com.ibm.ws.management.bla.j2ee.ext.
  tasks.ValidateBLATask.performTask(ValidateBLATask.java:101)
  [08/25/2017 19:19:04:280 EDT]  at
  com.ibm.ws.management.application.
  SchedulerImpl.run(SchedulerImpl.java:315)
  [08/25/2017 19:19:04:280 EDT]  at
  java.lang.Thread.run(Thread.java:785)
  [08/25/2017 19:19:07:436 EDT] ADMA5011I: The cleanup of the temp
  directory for application caeser-core-ws is complete.
  [08/25/2017 19:19:07:436 EDT] ADMA5014E: The installation of
  application caeser-core-ws failed.
  [08/25/2017 19:19:07:468 EDT] WASX7017E: Exception received
  while
  running file "C:
  \IBM\V9\WebSphere\WSMigration\QPASCellManager\install_caeser-cor
  e-ws.
  ear.jy"; exception information: com.ibm.ws.scripting.
  ScriptingException: WASX7132E: Application install for C:
  \IBM\V9\WebSphere\AppServer\profiles\QPASCellManager\installable
  Apps\cae
  ser-core-ws.ear failed: see previous messages for details.
  

Local fix

• Client removed the BKUP edition from the Migration backup
  directory, which subsequently allowed the BASE edition to
  install. The BKUP editions were then successfully installed
  using the Admin Console after migration completely successfully,
  deploying all other applications.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  Configuration Migration Toolkit             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Base edition fails to deploy if other   *
  *                      edition deploys first                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Migration installs all BLAs from the old environment, then
  deploys
  applications to them. However, if the BLA representing an
  edition
  of
  an application is created first, creating the BLA for the base
  edition fails, with a message claiming a BLA by the name already
  exists printed to the "install_all_BLAs" log. Then, when the
  application itself is to be deployed application then fails to
  deploy because it does not know which BLA to install the
  application
  to. This problem is compounded by issues with installing both
  editions concurrently, where the second application will not be
  listed in the ibm-edition-metadata.properties file in the cell.
  This
  may cause one of the editions to be deployed with a lower Java
  EE
  compatibility level than necessary, as the behavior of the tool
  for
  certain kinds of deployment failures is simply to keep retrying
  with
  lower Java EE compatibility levels until one succeeds.
  

Problem conclusion

• BLA creation was modified to always create base edition BLAs fir
  The application deployment process was modified to better identi
  and prevent editions of applications from deploying concurrently
  with the base edition. App deployment was also modified to
  explicitly specify the BASE edition for base edition application
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.6.  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 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

• R900 PSY

     UP