IBM Support

PH22735: CORRECTIONS ARE NEEDED TO THE DOCUMENTATION IN THE KNOWLEDGE CENTER FOR IBM WEBSPHERE APPLICATION SERVER VERSION 8.5

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • This APAR describes the issues that customers encountered with
    IBM WebSphere Application Server Version 8.5.  These issues were
    resolved as knowledge center updates in March, 2020.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  This APAR provides a cumulative list of     *
    *                  the documentation issues for March 2020     *
    *                  that affect users of IBM WebSphere          *
    *                  Application Server Version 8.5.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Knowledge Centers for WebSphere     *
    *                      Application Server Version 8.5 need     *
    *                      to reflect customer enhancement         *
    *                      requests received in problem            *
    *                      management records (PMRs). These        *
    *                      enhancements can include fixing         *
    *                      technical inaccuracies or clarifying    *
    *                      vague information                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    See the Problem conclusion section for a description of the
    issues, which are described in customer PMRs, and the
    documentation change or changes that will address these issues.
    

Problem conclusion

  • Note: As we update our knowledge centers, the following
    Version 8.5 modifications will be available. To access the
    latest on-line documentation, go to the product library page
    at https://www.ibm.com/support/knowledgecenter/en and select
    the version and product that is appropriate for your WebSphere
    Application Server environment.
    
    The following Version 8.5 issues will be addressed:
    
    ID: 2991 (GHE)
    Problem: Topic, Thread pool counters, has an error in table
    entry for thread pool counter, PercentUsed.  The key value is
    documented as threadPoolModule.percenteUsed and should be,
    threadPoolModule.percentUsed
    Resolution: Topic, Thread pool counters, is updated with the
    correct key value of threadPoolModule.percentUsed.
    
    This update also applies to V9.0 level of the knowledge center.
    -------
    
    ID: #2777 (GHE)
    Problem: The topic, Web server plug-in custom properties
    provides a good description of what the
    Plugin_PersistTimeOut_Reduction property does, however this
    property cannot be set according to the administrative console
    navigation presented in this topic.
    This can cause errors and mistakes in setting this property.
    Resolution: topic, Web server plug-in custom properties , is
    updated and property Plugin_PersistTimeOut_Reduction, is moved
    to topic, Administration services custom properties, where the
    following updates are made:
    (1) Topic, Administration services custom properties, is
    updated with a new title, Administration and Administration
    services custom properties.
    (2) Property,Plugin_PersistTimeOut_Reduction, is added and its
    description along with the correct navigation to use to set
    the property, which is:
    Administrative Console: Click Servers > Server Types >
    WebSphere application servers > server_name, next, click the
    "+" to epand the Server Infrastruture section, then click
    Custom properties.
    
    This update also applies to the V9.0 level of the knowledge
    center.
    ---------
    
    ID: #2934 (GHE)
    Problem: Topic, Characters that are valid for user IDs and
    passwords, was removed from the English knowledge center because
    it has many errors and needs to be redone and republished.  But,
    certain translations of this topic are still appearing in the
    knowledge centers for Japanese, Chinese, Korean, German, French,
    and Spanish.  These translated versions of the topic need to be
    removed also.
    Resolution:  When the V8.5 level of the English knowledge center
    is re-translated, these language specific topics will not
    appear, but until that re-translation occurs, a DISQUS note will
    be place in each of these appearing languages for the topic that
    says:
    *** This topic was removed from the knowledge center. ***
    Correct information will be supplied in the future.
    If you accessed this page by using a bookmark or external URL,
    the bookmark or links will need updating when the new
    information is published.
    If you accessed this page from the Table of Contents or Search
    Bar, remember that the information is inaccurate, and the topic
    will be removed in the future.
    -------
    
    ID: #3052 (GHE)
    Problem: Setting the WebSphere Environment Variable
    wlm_stateful_session_placement_on to true didn't have any
    effect. The server's was.env file still showed
    wlm_stateful_session_placement_on set to 0.
    
    The property WLMStatefulSession was set to 'false' under the
    Server's Administration Services, and if it is set explicitly
    there, will take precedence. Removing the property
    WLMStatefulSession allowed the Environment Variable
    wlm_stateful_session_placement_on to take effect.
    
    The default for WLMStatefulSession is 'false'. However, if
    WLMStatefulSession is not specifically set as a custom
    property,
    then setting the WebSphere variable
     wlm_stateful_session_placement_on to 'true' will take effect.
    
    This explanation needs clarification.
    
    Resolution: (1) Topic, Configuring an application server to use
    the WLM even distribution of HTTP requests function, is
    updated.
    The following is added to step 1e.
    If the property, WLMStatefulSession exists, its setting takes
    precedence over any setting for the environment variable
    wlm_stateful_session_placement_on. If WLMStatefulSession does
    not exist, then you can set wlm_stateful_session_placement_on
    to
    true (or accept the default, false) to establish (or not
    establish) an even distribution of HTTP requests.
    (2) Topic, Application server custom properties for z/OS, is
    updated. A Note is added to the
    wlm_stateful_session_placement_on description that reads:
    NOTE: If the property, WLMStatefulSession exists, its setting
    takes precedence over any setting for
    wlm_stateful_session_placement_on. See the use of the custom
    property, WLMStatefulSession here,Configuring an application
    server to use the WLM even distribution of HTTP requests
    function, for more information on the effect of using
    wlm_stateful_session_placement_on.
    
    This update also applies to V9.0 level of the knowledge center.
    -------
    
    ID: #3088 (GHE)
    Problem: Topic, removeNode command, has an error in the
    section, Removing a node that was federated as part of cell
    profile creation. The second paragraph in this section reads:
    To successfully remove a node that was federated as part of a
    cell profile creation, use the Profile Management Tool to
    delete the profile for the node.  and refers to using the
    Profile Management Tool to delete the profile for the node.
    This is wrong.
    Resolution: Topic, removeNode command, is updated in section,
    Removing a node that was federated as part of cell profile
    creation.  The second paragraph now reads:
    
    To successfully remove a node that was federated as part of a
    cell profile creation, use the manageprofiles utility to
    delete the profile for the node. After the profile for the
    node is deleted, use the cleanupNode command on the deployment
    manager to remove the node configuration from the cell
    repository. You can create a new profile using the Profile
    Management Tool.
    
    This update also applies to the V9.0 topic level in the
    knowledge center.
    ---------
    
    ID: #3106
    Problem: Topic, managesdk command, needs some extra
    explanation for the -enableProfile and -enableProfileAll
    parameter concerning node-scoped JDK and server-scope JDK so
    that these parameters and the managesdk command can be used
    properly.
    Resolution; Topic, managesdk command, is updated in the
    descriptions of the -enableProfile and -enableProfileAll
    paramaters.  The first paragraph of -enableProfile now reads:
    Enables a profile to use a specified SDK name. The
    -profileName parameter specifies the profile and the -sdkname
    parameter specifies the SDK name. The command enables the
    profile and the node-level default SDK of the profile to use
    the specified SDK name. WebSphere Application Server profiles
    have a profile wide (node) JDK setting. If no specific
    Server-level JDK is set, the WebSphere Application Servers
    inherit the JDK configured at the profile (node) level.
    
    If a specific server-level JDK is set from a specific
    profile's client scripts and tools, you can change this
    specific server-level JDK setting to be the server-level JDK
    setting at the profile (node) level. To make this change, you
    use the managesdk command with the -enableProfile and
    -enableServers parameters. Using the -enableServers parameter
    clears out all the SDK configuration settings for the client's
    profile and allows the client server to inherit the JDK
    configured at the profile (node) level. If you do not use the
    -enableServers option in the managesdk command, the
    server-level SDK settings are not changed.
    
    Attention: In the system, there exists a node-scoped JDK and a
    server-scoped JDK. If no server-scoped JDK is configured, then
    the servers inherit the node-scoped JDK. If the servers define
    the server-scope JDK then the servers will use that
    server-scoped JDK instead of the node scoped JDK.
    
    The first paragraph of -enableProfileAll now reads:
    Enables all profiles in an installation to use a specified SDK
    name. The -profileName parameter specifies the profile and the
    -sdkname parameter specifies the SDK name. The command enables
    the profile and the node-level default SDK of the profile to
    use the specified SDK name. WebSphere Application Server
    profiles have a profile wide (node) JDK setting. If no specific
    Server-level JDK is set, the WebSphere Application Servers
    inherit the JDK configured at the profile (node) level.
    
    If a specific server-level JDK is set from a specific
    profile's client scripts and tools, you can change this
    specific server-level JDK setting to be the server-level JDK
    setting at the profile (node) level. To make this change, you
    use the managesdk command with the -enableProfile and
    -enableServers parameters. Using the -enableServers parameter
    clears out all the SDK configuration settings for the client's
    profile and allows the client server to inherit the JDK
    configured at the profile (node) level. If you do not use the
    -enableServers option in the managesdk command, the
    server-level SDK settings are not changed.
    
    Attention: In the system, there exists a node-scoped JDK and a
    server-scoped JDK. If no server-scoped JDK is configured, then
    the servers inherit the node-scoped JDK. If the servers define
    the server-scope JDK then the servers will use that
    server-scoped JDK instead of the node scoped JDK.
    
    This update also applies to the V9.0 topic level of the
    knowledge center.
    ------
    
    ID:
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH22735

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-28

  • Closed date

    2020-03-05

  • Last modified date

    2020-06-23

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
24 June 2020