PH09937: AFTER MIGRATION AUTOMATICALLY CREATE ELEMENT AUTOMATICALLY THAT NOT EXIST BEFORE MIGRATION.

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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• After migration from WAS 7.0 to WAS 8.5.5, not exist element in
  the old environment is exist in the new environment.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Configuration Migration              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Removing userID/password from           *
  *                      Session Database Persistence settings   *
  *                      and migrating results in                *
  *                      userID/password returning.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When customers set the userID and passwrod fields in the
  session database persistence settings to blank values, the
  underlying XML attributes in server.xml are removed from the
  SessionDatabasePersistence element. However, in the profile
  templates for most server types, a default userID and password
  are specified. When migration encounters the scenario of
  attributes that are present in the new and not present in the
  old, it assumes the attributes are new config added in the new
  version and keeps them in the resulting merged config.
  However, in this case, if the attributes are missing it is
  because the customer has configured them to be removed, so
  they should remain unset in the new configuration.
  

Problem conclusion

• Migration was adjusted to preserve setting the userID and/or
  password fields to blank in the new environment.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.16 and 9.0.5.0.  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

• R850 PSY

     UP

• R900 PSY

     UP