PH15060: WASPREUPGRADE - THE "PLUGINS" DIRECTORY WAS NOT IN THE LIST OF WAS_INSTALL_ROOT PROTECTED DIRECTORIES.

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

APAR status

• Closed as program error.

Error description

• WASPreUpgrade examines whether collecting the "mjar" (migration
  jar) will cause harm to the new WebSphere environment when it is
  processed later by WASPostUpgrade.
  If it thinks it will be
  harmful the following message is issued as was done for the
  "<classPath>${WAS_INSTALL_ROOT}/runtimes</classPath>"
  entry:
  MIGR0575W: The following directory was not migrated to
  avoid corrupting the new application server installation or
  target profile
  There was no message for the
  "<classPath>${WAS_INSTALL_ROOT}/plugins</classPath>" entry
  because in the migration code the "plugins" directory was not in
  the list of WAS_INSTALL_ROOT protected directories, so
  WASPreUpgrade created the "mjar" and WASPostUpgrade processed it
  replacing the com.ibm.ws.migration.jar with the v8.5.5 version
  right in the middle of the migration.
  

Local fix

• Re-install v9.0.0.9
   Go back to v8.5.5, use the admin console and
  remove the "${WAS_INSTALL_ROOT}/plugins" from the library
  classpath.
   Rerun WASPreUpgrade
   Ensure there is no
  .../plugins/plugins.mjar in the migration backup directory.
  
  rerun WASPostUpgrade
   Then if they want they can add the
  "${WAS_INSTALL_ROOT}/plugins" back to the library's classpath.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server WASPostUpgrade Migration tool        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Missing java class from the             *
  *                      v9 migration plugin jar.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The migration process replaced the v9 migration plugin jar
  with the v855 version of the jar causing the WASPostUpgrade
  process to fail with a ClassNotFoundException.
  

Problem conclusion

• The customer added a library entry to their configuration which
  pointed to the ${WAS_HOME}/plugins directory.  WASPreUpgrade
  created an archive of that directory and WASPostUpgrade moved
  it forward and replaced the plugins directory in V9 with the
  one from V855.  Looking at the WASPostUpgrade code, the plugins
  directory happened to be missing from the protected directory
  list.  Other ${WAS_HOME} directories listed in their
  libraries.xml file were not migrated and a message was written
  to the log and trace stating that this library reference is
  being skipped to protect the new WebSphere installation from
  being corrupted.  Somehow "plugins" dir wsa missing.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.5.1.  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