PM56707: WASPOSTUPGRADE THOWS NPE WHEN UPDATING SERVER LEVEL VARIABLES.XM L

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

• A referenced variable cannot be added to the server level
  variables.xml in new servers created during WASPostUpgrade.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server v8.0 migration tools using a custom  *
  *                  profile at the target profile and having    *
  *                  server level variables references in the    *
  *                  libraries.xml file.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: A server level variable is being        *
  *                      referenced during migration but the     *
  *                      target variables.xml file does not      *
  *                      exist at this level yet, causing a      *
  *                      NullPointerException.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The server level variables.xml file does not exist in the
  target profile.  Another config file such as the libraries.xml
  is using a server scoped variable.  The cross machine
  migration code must determine the variables setting in the
  corresponding target variables.xml file.  This corresponding
  file does not exist if the custom profile template was used to
  create the target profile.  Thus the NullPointerException is
  thrown.
  

Problem conclusion

• The code will prime the server level variables.xml file in
  the target profile from the template before any config file
  processing occurs.
  
  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 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