IBM Support

PI21810: CORRECTIONS ARE NEEDED TO THE DOCUMENTATAION IN THE INFORMATION 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 information center updates in August, 2014.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  This APAR provides a cumulative list of     *
    *                  the documentation issues for month_year     *
    *                  that affect users of IBM WebSphere          *
    *                  Application Server Version 8.5.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Information 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: We update our information centers monthly. The following
    Version 8.5 modifications will be available in the month_year
    update to the Information Centers. To access the latest
    on-line documentation, go to the product library page at
    http://www.ibm.com/software/webservers/appserv/library and
    select the version and product that is appropriate for your
    WebSphere Application Server environment.
    ID: PI21810
    Problem  In Topic, Storing transaction and compensation logs
    in a relational database for high availability, describes how
    with examples of the "CREATE TABLE" function.  These lines to
    the example need to indicate that if any tablesuffix is
    specified, that the table value needs to be appended with the
    value. For example:
    CREATE TABLE WAS_TRAN_LOG<tablesuffix>(
    Where <tablesuffix> is the value of the specified tablesuffix
    (referred to as "suffix" in section 2d and 3d.
    Resolution: Topic, Storing transaction and compensation logs
    in a relational database for high availability, is updated
    with the corrected examples that include the <tablesuffix> as
    follows:
    The following DDL shows how to create the database tables with
    the App1 table suffix on DB2:
    
    CREATE TABLE WAS_TRAN_LOGApp1(
      SERVER_NAME VARCHAR(128),
      SERVICE_ID SMALLINT,
      RU_ID BIGINT,
      RUSECTION_ID BIGINT,
      RUSECTION_DATA_INDEX SMALLINT,
      DATA LONG VARCHAR FOR BIT DATA)
               --------
    -----------
    ID: 760072
    Problem:   The GetDWLMTable property is not valid as a custom
    property in Version 8.5 of the knowledge center.  The custom
    nature of this property needs to be removed.  The current
    description is  causing confusion for the customer.
    Resolution:  Topic, plugin-cfg.xml file, is updated. The
    descriptiions for ESIEnableToPassCookies and GetDWLMTable are
    moved from the section of the topic describing RequestMetrics
    to right after ChunkedResponse.
    Topic, Creating clusters, is updated.  A note is added to step
    4, which reads as follows:
    Remember: Set the GetDWLMTable property using the check box on
    the administrative console rather than using the custom
    property.
    Topic, Web server plug-in custom properties, is updated.  The
    GetDWLMTable description is removed from the topic.
    -------------
    
    ID: RTC_138479
    Problem : There is not enough knowledge center information
    concerning the Liberty TAI Config Properties .  Specifically,
    the description of invokeBeforeSSO and invokeAfterSSO need to
    be expanded to
    avoid confusion for users.
    
    Resolution: Topic, Configuring TAI for the Liberty profile, is
    updated with a NOTE that reads,
    Note: By default, the invokeBeforeSSO property is set to true.
    By using this setting TAI is invoked even when the SSO token
    is present and valid. However, if the expected behavior is to
    invoke TAI only when the SSO token is invalid or not present,
    then this property can be disabled by setting it to false, and
    enabling the invokeAfterSSO property. By using this setting
    TAI is invoked only when the SSO token is not present or is
    invalid. In some cases, this setup might improve the
    performance of your system.
    ---------
    ID: 760183
    Problem:    There is confusion between two different kinds
    of command-line certificate management commands that are
    available. gskcmd is java code that is the original function,
    but gskcapicmd is the preferred command-line function to use.
    This preferred function needs to be documented in the
    knowledge center.
    
    Resolution: Topic, Using the gskcapicmd command, is updated
    to read as follows:
    The gskcapicmd command provides a command line interface for
    certificate management tasks that might otherwise be provided
    by the ikeyman command. (The gskcmd command is a Java-based
    alternative.)
    Procedure
        You can invoke the gskcapicmd from the
    <ihsinst>/bin/ directory.
            [Windows] gskcapicmd.bat
            [AIX][Linux][HP-UX][Solaris] gskcapicmd
        Perform the certificate management tasks that you want to
    complete.
    The  V8.0 knowledge center is also updated.
    -----------
    ID: 760168
    Problem: There is an incorrect system path documented in
    Topic, Configuring stand-alone custom registries, in step 5.
    This error can lead to system errors.
    
    Resolution:Topic, Configuring stand-alone custom
    registries, in step 5 is updated to read:
    5. Add your custom registry class name to the class path. It
    is recommended that you add the Java Archive (JAR) file that
    contains your custom user registry implementation to the
    following directory:
    app_server_root/classes
    
    The  V8.0 knowledge center is also updated.
    ------------
    ID: 760070
    Problem:The explanation of the custom property,
    overrideAutoProp, is not found in Knowledge Center.   It
    should be documented.
    
    Resolution: Topic, Java virtual machine custom properties, is
    updated to add, overrideAutoProp.  It reads:
    overrideAutoProp
    Use this custom property to propagate the plugin-cfg.xml to
    both the remote node repository and the remote web server
    location.
    When this property is set to true with manual propagation, the
    plugin-cfg.xml is propagated to BOTH the remote node
    repository and the remote web server location. When this
    property is set to false with manual propagation, the
    plugin-cfg.xml is propagated to ONLY to the remote node
    repository and NOT to the web server location.
    The default value is false.
    If you decide to use this custom property, you must specify it
    as a node JVM custom property.
    
    Once this property is set for the node, you must synchronize
    the change to the node. Setting this property does require you
    to stop and start the node so that the setting takes effect.
    
    The V7.0, and V8.0 knowledge centers are also updated with
    this property.
    -------------
    ID: 760018
    Problem: Topic, HTTP session rebalancing, needs to explain in
    better detail that is It is beneficial to run with very low
    write intervals when using session persistence. The customer
    found very little information in this topic addressing this
    information.
    
    Resolution: A new section, Recommendation for Session
    distribution with time-based writes, is added to this topic
    and reads:
    Note: When using session distribution, with time-based write,
    use of very low write intervals is recommended. Low write
    intervals minimize the likelihood of a "hole or gap" that can
    occur when a rebalance occurs between session writes. A
    rebalance in this scenario will result in the response to the
    end user to appear as if the session has expired.
    Alternatively the End of Servlet Service Method writes option
    can be employed to eliminate the vulnerability that exists
    with any time-based write interval, though End of Servlet
    Service Method does incur a performance penalty. Low write
    intervals inhibit this condition.
    ------------
    ID: RTC_140249
    Problem:  When using a WebSphere Application Server-provided
    IBM JVM, there is a known limitation which causes the
    Administrative Center to come up with a blank display.   This
    is a limitation that needs to be explained.
    
    Resolution: Topic, Liberty profile: Runtime environment known
    restrictions, is updated to add the following restriction
    information:
    Admin Center feature restrictions
    For the adminCenter-1.0 feature, the following restriction
    applies:
    Using an IBM Java virtual machine (JVM) available with a
    WebSphere Application Server full profile product, such as
    Network Deployment, causes WebSphere Liberty Administrative
    Center ("Admin Center") to not display in a browser. The IBM
    JVM available with a full profile product points to security
    classes that are available only with a full profile product,
    and not to security classes needed by Admin Center, which
    requires Secure Sockets Layer (SSL). Use a JVM that supports
    Liberty profile products and SSL.
    ---------
    ID: 760181
    Problem: Topic,  Preparing Solaris systems for installation,
    in the the knowledge
    center does not contain any infroamtion for Solaris 11. The
    user cannot
    confirm if required operating system settings are satisfied or
    not for installing WebSphere Application Server.
    
    Resolution:  Topic,  Preparing Solaris systems for
    installation, is update for Solaris 11 as follows:
    1)a note is added that reads:
    Important: On the Solaris platform, remote IBM Installation
    Manager graphical user interface (GUI) processing is only
    supported with VNC because of problems with X servers.
    2)Step 9 is updated to include Solaris 11 along with Solaris 9
    and Solaris 10.
    3)A section is added to the end of the topic that gives an
    example of Solaris 11 settings that might be useful after the
    installation.   This section reads:
    
    After the installation, you can examine the following setup
    script for information concerning initial settings for Solaris
    11.
    
    echo "V2014-06-20"
    echo "master version ->
    https://rtpmsa.raleigh.ibm.com/msa/projects/t/testappbinaries/OS
    /ossetup.zip"
    echo ""
    #
    #
    ### check if the .txt file exists
    if [ ! -f "hostlist.txt" ]; then
       echo "-- hostlist.txt file does not exist. cp
    hostlist.txt.TEMPLATE hostlist.txt and add your hosts"
       echo "-- Processing halted"
       exit 1
    fi
    for hostName in &#180;cat hostlist.txt&#180;
     do
      echo "checking: $hostName"
      ssh $hostName 'grep "ulimit -n 20000" /etc/profile'
      if [ $? != 0 ]; then
        ssh $hostName 'echo "ulimit -n 20000" >> /etc/profile'
        echo "set the ulimit on $hostName"
      fi
      ssh $hostName 'grep "semsys:seminfo_semopm = 200" /etc/system'
      if [ $? != 0 ]; then
        ssh $hostName 'echo "semsys:seminfo_semopm = 200" >>
    /etc/system'
        echo "set the seminfo_semopm on $hostName"
      fi
      ssh $hostName 'ipadm set-prop -p _conn_req_max_q=8000 tcp'
      ssh $hostName 'ipadm set-prop -p  _time_wait_interval=30000
    tcp'
      ssh $hostName 'ipadm set-prop -p
    _fin_wait_2_flush_interval=67500 tcp'
      ssh $hostName 'ipadm set-prop -p _keepalive_interval=300000
    tcp'
     done
    ------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI21810

  • 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

    2014-07-11

  • Closed date

    2014-08-06

  • Last modified date

    2015-04-17

  • 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 November 2021