IBM Support

PH10258: ODRPORTPATHPREFIX CANNOT BE ADDED FROM THE WEBSPHERE ADMIN CONSOLE

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

  • OdrPortPathPrefix property was manually added to the
    plugin-cfg.xml file by the user. However, the Plug-in did not
    recognize the propery and the file would write to a directory
    that was not writeable
    
    The property is hardcoded to write to INSTANCE_DIR/logs
    
    User is unable to change the property to write the file to
    a custom directory.
    
    This property is also not available as a Plug-in property that
    can be added in the web server definition in the WebSphere
    Admin Console.
    
    Versions where problem was reproduced:
    WebSphere Plugin 8.5.5.14
    WebSphere Plugin 9.0.0.10
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Can't add custom properties to          *
    *                      <Property Name section                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    PI55092 introduced a way for customers to add new custom
    properties within the plugin-cfg.xml file.  This new
    feature utilizes a prefix like PLG.config or PLG.cluster.  The
    plugin gen knows to look for these labels and then adds the
    property to the proper place within the XML.  It was
    discovered that the area that contains the "ESI" type
    properties didn't have any way to get a custom property.
    

Problem conclusion

  • This appar addresses this by acknowledging the PLG.prop
    prefix
    and will add properties within the <Property Name section
    which is just below the <Config tag.  These properties are
    added within the Admin Console at Webserver -> [servername]
    ->
    plugin properties -> custom properties.
    
    See APAR PI55092 for details on the other prefixes used to
    set custom properties.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.16 & 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

    PH10258

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-27

  • Closed date

    2019-04-17

  • Last modified date

    2019-04-17

  • APAR is sysrouted FROM one or more of the following:

    PH10236

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PH10258

Modified date: 17 April 2019