IBM Support

PI66582: DOCUMENTATION IN KNOWLEDGE CENTER FOR WEBSPHERE APPLICATION SERVER V9

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • This APAR deals with documentation updates for WebSphere
    Application Server V9
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  This APAR provides a cumulative list of     *
    *                  the documentation issues for                *
    *                  December, 2016                              *
    *                  that affect users of IBM WebSphere          *
    *                  Application Server Version 9.0.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Knowledge Centers for WebSphere     *
    *                      Application Server Version 9.0 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 9.0 modifications will be available in the
    December, 2016
    update to the Knowledge 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.
    
    The following Version 9.0 issues will be addressed:
    
    ID: PI66582
    Problem:
    The hover-over help for the SIBJMSActivationSpec subscription
    name in the Admin Center does not identify the field as
    requiring a durable topic subscriber.
    
    Resolution:
    The hover-over help for this field has been updated to state
    this field requires a durable topic subscriber
    
    ---------------
    ID: 779761
    Problem: Customer sees that content in a technote should be in
    the knowledge center.
    The note in the technote reads:
    http://www-01.ibm.com/support/docview.wss?uid=swg21139573
    that says,
    Note: Anytime you merge two plugin-cfg.xml files, you should
    take time to review all properties that would be considered
    global to the merged xml (i.e.. refreshInterval or esiEnable).
    Is it possible to add a description to  Knowlege Center  that
    about checking execution contents and manual correction after
    executing the pluginCfgMerge tool.
    
    Resolution: Topic, Configuring simple load balancing across
    multiple application server profiles, is updated as follows:
    The last paragraph in step is replaced with the following
    
    Step 8 reads...Merge the plugin-cfg.xml files from multiple
    application server nodes.....
    (1) The last paragraph in step is replace with the following:
    REMEMBER: Anytime you merge two plugin-cfg.xml files, you
    should take time to review all properties that would be
    considered global to the merged xml (i.e.. refreshInterval or
    esiEnable). If you see disparaging settings between the two,
    you will need to evaluate which setting best suits the
    environment under the new xml.  If you are using the
    pluginCfgMerge tool to automatically merge the plugin-cfg.xml
    file then the first xml file in the command string will be
    used as the source for global properties for the new xml file.
    
    Warning: As you make changes to the WAS environment that
    require a new
    plug-in generation, you will need to remerge the files.
    
    (2) the Related Information reference to the technote at the
    bottom of the topic is deleted.
    
    This update also applies to V7.0, V8.0, and V8.5 levels of the
    knowledge center topic.
    -----------
    
    ID: 779827
    Problem: Topic, Algorithm for performing a rollout,has  8
    steps under the Atomic Rollout section that are not entirely
    correct in functional detail and need updating to avoid future
    customer errors.
    
    Resolution: Topic, Algorithm for performing a rollout, is
    updated in the Atomic rollout section to read as follows:
    
    When you choose to perform an atomic rollout, the following
    steps occur:
    1. Quiesce work to half of the servers.
    2. Stop the applications or servers in the first half of the
    servers.
    3. Update the server configurations.
    4. Start the applications or servers in the first half of the
    servers.
    5. Quiesce work to the second half of the servers.
    6. Queue or delay requests until the rollout is complete
    7. On the second half of the servers, stop the applications or
    servers, update the server configurations, and start the
    applications or servers.
    8. Rollout is complete.
    
    This update also applies the V8.5 topic in the knowledge center.
    ---------------
    
    ID: 779861
    Problem: For EclipseLink on WebSphere Application Server,
    logging output to a file other than the serve
    trace.log is not currently supported. Even if you set the
    eclipselink.logging.file, the eclipselink trace will be
    written in WebSphere trace. This processing should be
    documented.
    
    Resolution: Topic, Logging applications with JPA, is updated.
    Under section, Notable logging persistence properties: add an
    additional bullet the reads:
    - eclipselink.logging.file
    WebSphere Application Server does not support EclipseLink
    redirecting trace to an external file. All EclipseLink logging
    and tracing is routed through WebSphere Application Server
    trace components.
    
    This update applies to V9.0 ONLY.
    ---------------
    
    ID: 778604
    Problem: The customer is using two topics to use the
    manageprofiles
    command and needs to remember to have the proper permissions
    for the directory structure that the manageprofile command will
    require.  These two topics need some addition text to remind
    the user of these permissions.
    Resolution:
    Topic (1) is, Administering application servers.
    The note is added just after the Best practice note in the
    About this task section.
    
    Topic (2) is, Managing profiles for nonroot users.
    The note is added in the About this task section.
    
    The note reads as follows:
    AVOID TROUBLE: Prior to using the manageprofiles
    command, remember to have established the proper permissions
    to the directory to which you will be using the manageprofiles
    command.
    
    The update also applies to V7.0, V8.0, and V8.5 levels of the
    knowledge center.
    -----------
    ID: 779912
    Problem:  The knowledge center describes the meaning of the
    default maximum heap size settings in such a way that it is
    confusing to understand and use.  An update to clarify the
    maximum heap size setting is necessary.
    
    Resolution: Two topics are updated:
    Topic (1) - Java virtual machine settings, is updated (for
    V7.0, V8.0, and V8.5.5) -
    The first two paragraphs of the maximum heap size section is
    updated to read:
    Maximum heap size
    Specifies, in megabytes, the maximum heap size that is
    available to the  JVM code.  If this field is left blank, the
    default value is used.
    
    The default maximum heap size for any distributed (AIX,
    Solaris,  Windows, and such)
    operating system is 256 MB for all servers, such as dmgr,
    nodeagent, and application servers.
    NOTE: The default maximum heap size value does not display in
    the Integrated solution console unless you change or update
    the heap size value. The minimum default heap size is 50 MB.
    
    For the V9.0 level of this topic, we only add the following
    sentence to the second paragraph:
    The default maximum heap size value does not display  in the
    Integrated solution console unless you change or update the
    heapsize value.
    
    Topic (2) - Tuning the IBM virtual machine for Java, is
    updated.  Under the Xmx parameter, the table entry of Default
    is updated to read (for V7.0, V8.0, V8.5.5):
    Information  Value
    Default      By default, the JVM dynamically calculates the
    Java heap size based on the available memory in the system.
    For any distributed (AIX, Solaris, Windows, and
    such) operating system, the default is 256 MB for all servers,
    such as dmgr, nodeagent, and application servers.
    NOTE: The default maximum heap size value does not display in
    the Integrated solution console unless you change or update
    the heapsize value.
    
    The V9.0 level under the Xmx parameter reads as follows:
    Information  Value
    Default      By default, the JVM dynamically calculates the
    Java heap size based on the available memory in the system.
    NOTE: The default maximum heap size is 25% of the total amount
    of system memory up to 4 GB. The default maximum heap size
    value does not display  in the Integrated solution console
    unless you change or update the heapsize value.
    ---------
    
    ID: 235373 (RTC)
    Problem:
    
    Resolution:
    
    --------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI66582

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-28

  • Closed date

    2016-12-12

  • Last modified date

    2017-03-09

  • 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":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 October 2021