IBM Support

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

Fixes are available

17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • This APAR describes the issues that customer encountered with
    IBM WebSphere Application Server Version 8.5  These issues were
    resolved as knowledge center updates in February, 2017
    

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 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: We update our knowledge centers monthly. The following
    Version 8.5 modifications will be available in an
    update to the Knowledge Center. 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.
    
    The following Version 8.5 issues will be addressed:
    
    ID: PI75590
    Problem: Topic, Requirements-based job scheduling, is being
    documented in the V8.0, V8.5.5, and V9.0 knowledge center, but
    the function is not supported in these releases.  This
    condition would be confusing to customers and this topic needs
    to be deleted from these levels of the knowledge center.
    
    Resolution: Topic, Requirements-based job scheduling, is
    deleted from the V8.0, V8.5.5, and V9.0 levels of the
    knowledge center.
    
    This update applies to V8.0, V8.5.5, and V9.0 levels of the
    knowledge center.
    -----------
    
    ID: 237326 (RTC)
    Problem: in the knowledge center topic, Messaging Engine
    (messagingEngine) and specifically under the entry for
    fileStore, the description for the logFileSize is not quite
    accurate and is unclear. The description should be rewritten
    to clarify its use and to clarify any recommendations.
    
    Resolution: Topic, Messaging Engine (messagingEngine), is
    updated the description for the logFileSize is rewritten to
    read as follows:
    Size in megabytes of the log file.
    
    The log file size CANNOT exceed half the size of the file
    store size. For a file store size set to 400 MB, the log file
    size cannot exceed 200 MB.
    
    Recommendation: 25% of the file store size is the maximum
    recommended setting for log file size. For a file store size
    set to 400 MB, the maximum recommended setting for log file
    size would be 100 MB.
    
    This update also applies to V9.0 of the knowledge center.
    ------------
    
    ID: 236072 (RTC)
    Problem: Topic, Liberty feature manifest files, has a
    description of the location directive, but the
    location directive explanation does not work for OSGi bundles
    and needs to be updated.
    
    Resolution:  Topic, Liberty feature manifest files, is
    updated.  The location directive description is expanded to
    read as follows:
    
    location - The location of the bundle. For a bundle or JAR
    type, this value can be a comma-separated list of directories
    that represent a search path. For any type, this value might
    be a single entry that points directly to the resource and
    might be specified as a file URL. Paths might be absolute or
    relative. Relative paths are resolved relative to the location
    of the product extension that contains the feature. For a user
    feature, the default product extension location is used which
    is ${wlp.user.dir}/extension. The location of non-default
    product extensions is declared by the
    com.ibm.websphere.productInstall property in its properties
    file in the ${wlp.install.dir}/etc/extensions directory.
    
    This update also applies to the V9.0 topic of the knowledge
    center.
    ----------
    
    ID: 779456
    Problem: topic, Creating a new key pair and certificate
    request, has an AVOID TROUBLE note that pertains to Unix
    operating systems and encapsulating string values when using
    the gskcapicmd command.  It is unclear in its description.
    The page lists four special characters, (!), (\), { ?? }, and
    ( ?/ ). Not sure if this is a complete list. It is not clear
    if the ( ?/ ) character is the opening single quote or
    closing single quote (apostrophe). Should the user escape both
    characters?  The AVOID TROUBLE note should be corrected.
    
    Resolution: Topic, Creating a new key pair and certificate
    request, is updated.  The AVOID trouble note is updated to
    read as follows:
    AVOID TROUBLE:
    AVOID TROUBLE: Two types of escaping may be necessary when
    creating certificate requests on the command line.
    1) Shell escaping
    As with any command passed through a Unix shell, shell
    meta-characters must be escaped if they are meant to be
    interpreted by the underlying command.
    
     ?? ?ncapsulate string values associated with all tags in dou
    quotes (  ?? ??? ?. ??  ?  ).
     ?? ?scape with a  backslash ( \ ) character, the following
    characters if they appear in the string values: exclamation
    mark ( ! ), backslash ( \ ), double quote (   ?? ? ).
    
    Note: When you are interactively prompted by the gskcapicmd
    command for a value (such as a password), you do not need to
    quote the string or add the escape characters,  because the
    shell is no longer influencing the input you provide to the
    command.
    2) Escaping commas within the  ?? ?dn ??  ?option
    The  ?? ?dn ??  ?argument takes a comma-separated list of
    distinguished name components.  Because the comma is used as a
    delimeter, it must be escaped with a backslash when it is used
    as a literal.
    For example, if the -dn option has the following elements:
    CN=www.example.com
    O=Example, Inc.
    OU=example unit
    Specify the -dn option as follows:
      ?? ?-dn  ?? ?N=www.example.com,O=Example\, Inc.,OU=examp
    
    This update also applie to V7.0, V8.0, and V9.0 topic of the
    knowledge center.
    -----------
    
    ID: 779458
    Problem: For migration jobs, symbolic links require special
    attention so as not to use symbolic links from a previous
    install.  The knowledge center needs an update to make this
    point.
    
    Resolution: Topic, Configuring with symbolic links on z/OS, is
    updated with the following note:
    AVOID TROUBLE: When generating the migration jobs, do not
    provide an existing symbolic link from a previous WebSphere
    install for the intermediate symbolic link. The intermediate
    symbolic link should be a new unique symbolic link otherwise
    the migration jobs will fail.
    
    This update to the knowledge center also applies to V7.0,
    V8.0, and V9.0.
    -------
    
    ID: 779826
    Problem: When configuring HTTP Strict Transport Security (HSTS)
    in response headers so that your server advertises to clients
    that it accepts only HTTPS requests, the topic:
    Setting up HTTP Strict Transport Security (HSTS), fails to
    indicate that this process only works if the client is
    connecting to the default ports for http (80) and https (443).
     An update to the knowledge center topics is necessary to
    remind users of this requirement.
    
    Resolution: Topic, Setting up HTTP Strict Transport Security
    (HSTS), is updated to add another bullet item in the Before
    you begin section of the topic that says:
    
    -- WARNING: HSTS only works if the client is connecting to the
    default ports for HTTP (port 80) and HTTPS (port 443).  If you
    are using non-default ports in your IBM HTTP Server
    configuration, you will need to put some other front-end
    device in-front of IHS that does use the default ports.
    
    For example:
    
    client ----> load balancer (ports 80 and 443) ----> IHS (other
    ports)
    
    This update also applies to V7.0, V8.0, and V9.0 level of th
    e knowledge center.
    
    *************************************************************
    Refer to continuation DOC APAR PI85544 for ID# - 779179
    *************************************************************
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI75590

  • 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

    2017-01-30

  • Closed date

    2017-02-20

  • Last modified date

    2017-08-08

  • 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":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021