IBM Support

PI93622: MIGRATING FROM WEBSPHERE V7 TO V8.5.5+ WITH A SERVER-LEVEL SECURITY.XML CAUSES POSTUPGRADE NULLPOINTEREXCEPTION

Fixes are available

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
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
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
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
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
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer had a server-level security.xml present in the config
    HFS when migrating from WebSphere Application Server v7 to
    v8.5.5.  The unexpected xml file caused the migration post
    upgrade step to have a NullPointerExecption.
    

Local fix

  • Two options exist:
    1) Remove any server-level security.xml files and re-run the
    WASPostUpgrade step
    or
    2) Run WASPostUpgrade with -scriptCompatibility=false
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Configuration Migration Tools v8.5 and      *
    *                  v9.0                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException when processing    *
    *                      security.xml in a server directory      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem will appear as a null pointer exception in the trace
    files that
    comes right after mentions of processing a security.xml with a
    path
    in a
    server directory, beneath the cell and node. Methods in the
    SecurityConfig
    or SecurityConfigCommon classes will be present in the stack
    trace.
    The problem occurs when migration encounters a security.xml file
    in
    a server
    directory. Usually, migration expects to only encounter the file
    at
    the cell
    level and expects it to have certain elements. The files found
    at
    the server
    level do not contain these elements, which migration doesn't
    expect. This
    causes null pointers when attempting to inspect and merge
    configuration that
    isn't present but is expected.
    This configuration is an older model, and customers who have run
    convertScriptCompatibility prior to migrating should not see
    this,
    as the
    server-level security.xml files are removed as part of that
    process.
    

Problem conclusion

  • Migration was adjusted to better handle cases where expected
    security configuration is not present, allowing it to handle
    server-level security.xml files.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.14 and 9.0.0.8.  Please refer to the Recommended Upda
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Remove or rename the security.xml file in the server directory
    within the migration backup directory before running
    WASPostUpgrade, then copy manually afterwards OR run
    convertScriptCompatibility.sh against the old profile prior to
    running WASPreUpgrade OR run WASPostUpgrade with the "-
    scriptCompatibility false" parameter.
    

Comments

APAR Information

  • APAR number

    PI93622

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-11

  • Closed date

    2018-04-05

  • Last modified date

    2018-04-05

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022