IBM Support

PI40830: SET DEFAULT OF VALUE OF SUPPORTCHANGELOG TO NONE FROM CLI

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If LDAP repository is configured using CLI
    createIdMgrLDAPRepository and the supportChangeLog parameter is
    not specified, then the default value for supportChangeLog is
    "none" (but the parameter and value are explicitly written to
    wimconfig.xml). This can potentially present a problem since
    the Integration Solutions Console considers the value to be
    "native" when the parameter is not present in wimconfig.xml.
    

Local fix

  • - Pass the parameter for supportChangeLog when using
    createIdMgrLDAPRepository
    
    - Use the ISC to explicitly set the change log support to
    "none" instead of "native" after configuring via
    createIdMgrLDAPRepository.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The console shows the value of          *
    *                      supportChangeLog to native if LDAP      *
    *                      repository is configured using CLI      *
    *                      with no value in supportChangeLog       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The default value of supportChangeLog in VMM configuration is
    None. But if the LDAP repository is configured using CLI
    without specifying the supportChangeLog parameter, the
    administrative console shows its value as Native.
    

Problem conclusion

  • LDAP repository configuration CLI will now keep the
    supportChangeLog value to NONE if a parameter for
    supportChangeLog is not specified.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.11 and 8.5.5.7.  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

    PI40830

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-11

  • Closed date

    2015-05-29

  • Last modified date

    2015-05-29

  • 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 APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
28 April 2022