IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

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 number

    PH09937

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-19

  • Closed date

    2019-06-03

  • Last modified date

    2019-06-03

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PH09937

Modified date: 03 June 2019