IBM Support

PH18458: MIGRATION IS UNABLE TO RESOLVE RELATIVE FILE PATHS CORRECTLY.

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

  • Migration is unable to resolve relative file paths
    correctly.
    For example, "libs/mylib.jar" would be resolved by
    the server runtime code as
    $USER_INSTALL_ROOT/libs/mylib.jar
    because the startServer script sets its current working
    directory to $USER_INSTALL_ROOT before starting the
    server.
    However. migration's current working directory would be
    what ever directory the code is called from. Migration should
    mimic the runtime behavior for non-absolute type paths.
    

Local fix

  • Copy library files manually.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Migration Tooling                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Library paths defined without a root    *
    *                      path are not processed correctly.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The code is using the wrong root variable for relative paths.
    After talking with the runtime team it was determinied for
    libraries that the relative path for libraries is the
    USER_INSTALL_ROOT variable.  Currently it is being set to the
    WAS_INSTALL_ROOT as that is the CWD for the WASPostUpgrade
    command.
    

Problem conclusion

  • Libraries defined without a root path should be resolved using
    the USER_INSTALL_ROOT path.  This is consisitent with the
    runtime's processing of these relative paths.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.3.  For more information, see 'Recommended Updates for
    WebSphere Application Server':
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH18458

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-23

  • Closed date

    2020-01-20

  • Last modified date

    2020-01-20

  • 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: 900

Reference #: PH18458

Modified date: 20 January 2020