IBM Support

PI98150: 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 June, 2018.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  This APAR provides a cumulative list of     *
    *                  the documentation issues for June, 2018     *
    *                  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 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: PI98150
    Problem: Topic, Migrating unrestricted jurisdiction policy
    files, local_policy.jar and US_export_policy.jar, only shows
    the migrating of the local_policy.jar in the procedure and
    should should the US_export_policy.jar migration also.  The
    technical details about the location of these files has
    changed for Java 8 SR5 FP10 and this topic should be updated
    with these implications.
    Resolution: Topic, Migrating unrestricted jurisdiction policy
    files, local_policy.jar and US_export_policy.jar, is update to
    also indicate the migration of the US_export_policy.jar.
    and the following table is added to describe the implications
    of Java 8 SR5 FP10:
    ATTENTION: Changes in Java (Java 8 SR5 FP10) move the
    restricted and unrestricted policy files to new locations and
    add a parameter, crypto.policy, to the java.security file that
    allows you to govern which policy files are used.
    Java SR5 Implications
    Table 1. Java SR5 Implications when using the crypto.policy
    setting within the java.security file .
    Java SR5 | crypto.policy  | Comments
     level   | setting        |
    
    Pre-FP10 |   N/A          | Proceed to the migration procedure
                              |  below.
    FP10
    and beyond| Not set       |If the traditional
    US_export_policy.jar and local_policy.jar files (that is,
    limited or unlimited) are found in the legacy
    JAVA-HOME/lib/security directory, then the rules embedded
    within these jar files are used. This helps preserve
    compatibility for users upgrading from an older installation.
    
    If the jar files are not present in the legacy
    JAVA-HOME/lib/security directory, then the JDK uses the
    unlimited settings, which is equivalent to setting
    crypto.policy=unlimited.
    
    Performing the migration procedure is not necessary.
    FP10       |                          |
    and beyond | crytpo.policy=unlimited  |
    
    If the traditional US_export_policy.jar and local_policy.jar
    files (that is, unlimited or limited ) are found in the legacy
    JAVA-HOME/lib/security directory, then the rules embedded
    within these jar files are used. This helps preserve
    compatibility for users upgrading from an older installation.
    
    If the jar files are not present in the legacy
    JAVA-HOME/lib/security directory, then the JDK uses the
    unlimited settings.
    
    Performing the migration procedure is not necessary.
    FP10       |                        |
    and beyond | crytpo.policy=limited  |
    
    If the traditional US_export_policy.jar and local_policy.jar
    files (that is, unlimited or limited ) are found in the legacy
    JAVA-HOME/lib/security directory, then the rules embedded
    within these jar files are used. This helps preserve
    compatibility for users upgrading from an older installation.
    
    If the jar files are not present in the legacy
    JAVA-HOME/lib/security directory, then the JDK uses the
    limited settings,
    
    Performing the migration procedure is not necessary.
    
    This update also applies to V9.0 level of the knowledge center.
    -----
    
    ID: 255655 (RTC)
    Problem: The CAUTION at the bottom of the topic,
    securityUtility command, is completely
    accurate, but its placement is missed by customers
    reading the topic.  Many customers only read so far as they
    need to.....  In this specific case, not reading the CAUTION
    caused errors for the customer.
    
    Resolution: Topic, securityUtility command, is updated as
    follows:
    (1) Copy the CAUTION in its entirety and paste it just after
    the first sentence intro and just before the SYNTAX section.
    (2) The topic will have then the CAUTION in two distinct
    places.... the beginning of the topic and at the end of the
    topic
    
    This update applies to all levels of Liberty.
    ------
    
    ID: 787488
    Problem: Wrong configuration parameters are being used as in
    the following:
    id = AdminConfig.create( 'StringNameSpaceBinding',
    AdminConfig.list("Cell"), [['name', name], ['nameInNameSpace',
    nameInSpace], ['stringToBind', stringToBind]])
    id2 = AdminConfig.create( 'StringNameSpaceBinding',
    The knowledge center needs to clarify this usage.
    
    Resolution: Topic, Commands for the AdminConfig object using
    wsadmin scripting, is updated.  The following additional
    information is added to the existing AVOID TROUBLE note.
    <*******BEGIN******>
    When a string contains special characters such as quotes,
    backslash or brackets, it can use the Jython String syntax,
    see below examples:
    
    1. String contains backslash "\" such as value = 'c\d".
    The backslash will be treated as escape character in Jython
    and it will be converted to double backslash by design:
    value = 'c\d'
    id = AdminConfig.create( 'StringNameSpaceBinding',
    AdminConfig.list("Cell"), [['name', 'test'],
    ['nameInNameSpace', 'test'], ['stringToBind', value]])
    print AdminConfig.showall(id)
    [name test]
    [nameInNameSpace test]
    [stringToBind c\\d]]
    
    If user likes to reserve original backslash in a path, it will
    need to use Jython with string attributes:
    id = AdminConfig.create("StringNameSpaceBinding",
    AdminConfig.list("Cell"), '[[name "test"] [nameInNameSpace
    "test"] [stringToBind c\d]]')
    or
    Use variable:
    value = "c\d"
    id = AdminConfig.create("StringNameSpaceBinding",
    AdminConfig.list("Cell"), '[[name "test"] [nameInNameSpace
    "test"] [stringToBind '+value+']]')
    
    
    2. String contains backslash "\" and brackets "[]" such as
    value = '\[br]'.
    Use Jython string attributes:
    id = AdminConfig.create("StringNameSpaceBinding",
    AdminConfig.list("Cell"), '[[name "test"] [nameInNameSpace
    "test"] [stringToBind "\[br]"]]')
    or
    Use variable:  Add additional brackets [] to enclose it
    value = "[\[br]]"
    id = AdminConfig.create("StringNameSpaceBinding",
    AdminConfig.list("Cell"), '[[name "test"] [nameInNameSpace
    "test"] [stringToBind '+value+']]')
    
    
    3. String contain quotes (""), backslash ("\") and brackets
    ("[]") such as value =  '"dq" \[br]'
    - Use "\" to escape quotes when passing value directly
    Use Jython string attributes:
    id = AdminConfig.create( 'StringNameSpaceBinding',
    AdminConfig.list("Cell"), "[[name 'test'] [nameInNameSpace
    'test'] [stringToBind '\"dq\" \[abc]']]")
    
    or
    - Use variable:  put additional brackets to enclose it
    value = '[\"dq\" \[br]]'    (original value: '"dq" \[br]')
    id = AdminConfig.create("StringNameSpaceBinding",
    AdminConfig.list("Cell"), '[[name "test"] [nameInNameSpace
    "test"] [stringToBind '+value+']]')
    
    
    You can use Jython with the object attributes (list syntax),
    see below examples:
    
    1. String contains brackets "[]" such as value = '[br]'
    Use Jython with object attributes:
    value = " [br]"  (add a leading space in front of bracket)
    id = AdminConfig.create( 'StringNameSpaceBinding',
    AdminConfig.list("Cell"), [['name', 'test'],
    ['nameInNameSpace', 'test'], ['stringToBind', value]])
    
    2.  String contain quotes ("") and brackets ("[]") such as
    value =  '"dq" [br]'
    Use Jython with object attributes:
    value = '"dq" [br]'
    id = AdminConfig.create( 'StringNameSpaceBinding',
    AdminConfig.list("Cell"), [['name', 'test'],
    ['nameInNameSpace', 'test'], ['stringToBind', value]])
    
    <*******END******>
    
    This update also applies to V9.0 of knowledge center.
    -----
    
    ID:
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI98150

  • 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

    2018-05-18

  • Closed date

    2018-06-01

  • Last modified date

    2018-06-21

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI98150

Modified date: 21 June 2018


Translate this page: