IBM Support

PH17297: CORRECTIONS ARE NEEDED TO THE DOCUMENTATION IN THE KNOWLEDGE CENTER FOR IBM WEBSPHERE APPLICATION SERVER VERSION V8.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 V8.5. These issues
    were resolved as knowledge center updates in Sept. 2019.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  This APAR provides a cumulative list of     *
    *                  the documentation issues for Sept. 2019     *
    *                  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: #1973 (GHE) and PH17297
    Problem: Several knowledge center topics need to clarify what
    JDK levels are used and how these JDK levels affects
    annotations. The application may not be deployed when
    annotations are compiled and available only in the JDK level
    used to compile the application but not the level used in the
    deployment manager.  This needs to be noted.
    
    Resolution: Topics,  Installing enterprise application files
    with the console, Managing applications through programming,
    Installing enterprise applications using wsadmin scripting, are
    updated with the following note:
    AVOID TROUBLE: During an Enterprise application deployment, it
    might be necessary to scan the application binary files for
    annotations that were introduced by Java EE 5 or later. An
    application might not deploy if it is compiled by using a Java
    SDK level that is higher than the Java SDK level of a
    deployment manager. The deployment manager needs to be either
    at the same Java SDK level or at a higher Java SDK level than
    the application.
    
    For topics, Select installation options settings, and, Options
    for the AdminApp object install, installInteractive, edit,
    editInteractive, update, and updateInteractive commands using
    wsadmin scripting,  change all text which reads:
    For this option, install only onto a Version 8.5 deployment
    target
    TO
    For this option, install only onto a Version 8.5 deployment
    target, which has the same or higher Java SDK level than the
    deployment manager.
    
    For V9.0 - for these topics change
    For this option, install only onto a Version 9.0 deployment
    target
    TO
    For this option, install only onto a Version 8.5 deployment
    target, which has the same or higher Java SDK level than the
    deployment manager.
    
    This update also applies to V9.0 of the knowledge center.
    -------
    
    ID: #2172 (GHE)
    Problem: Topic, Java virtual machine settings, describes
    setting, -Dcom.ibm.websphere.wlm.unusable.interval=interval as
    only applying to z/OS and that is incorrect.  This setting
    applies to all operating environments.
    Resolution: Topic,Java virtual machine settings, is updated:
    (1) Removing the z/OS icon at the description of
    -Dcom.ibm.websphere.wlm.unusable.interval=interval
    (2) Removing the first sentence in the description that reads:
    This argument only applies for z/OS.
    
    This update also applies to V9.0 of the knowledge center.
    ------
    
    ID: #2151 (GHE)
    Problem: Client encountered Message BBOT0001D during
    operations. The knowledge center does not document this
    message and it should.
    Resolution: Message BBOT0001D is documented in the knowledge
    and will read as follows:
    
    BBOT0001D OTS ENCOUNTERED HARDENED DATA LOSS DURING RESTART OF
    string. REPLY 'CONTINUE' OR 'CANCEL'
    
    Explanation:
    RRS returned ATR_HARDENED_DATA_LOST from the Begin_Restart
    service (ATRIBRS).
    
    User Response:
    Reply CONTINUE or CANCEL. If the reply is CONTINUE, OTS may
    not be able to resolve all in doubt transactions. Replying
    CANCEL will terminate the control region. Consult the RRS
    documentation for information on resolving this condition.
    
    This update also applies to the V9.0 knowledge center.
    --------
    
    ID: #2039 (GHE)
    Problem: Topic, BLAManagement command group for the AdminTask
    object using wsadmin scripting,contains erroneoous information
    in not using numbers CWWMH0196I for the startBLA
    command and CWWMH0199I for the stopBLA command. Additional
    topics, Example: Creating an SCA business-level application
    with scripting, Stopping business-level applications using
    scripting also need to display these message numbers.
    
    Resolution:
    (1) Topic,BLAManagement command group for the AdminTask
    object using wsadmin scripting, is updated.
    For startBLA command, change the "Return value" to read:
    The command returns a message on the result of the start
    operation. The following example displays the successful
    message output:
    CWWMH0196I: Business-level application
    "WebSphere:blaname=DefaultApplication" was started successfully.
    For stopBLA command, change the "Return value" part to read:
    The command returns a message on the result of the stop
    operation. The following example displays the successful
    message output:
    CWWMH0199I: Business-level application
    "WebSphere:blaname=DefaultApplication" was stopped successfully.
    (2) Topic, Example: Creating an SCA business-level application
    with scripting, is updated. Step 6 shows a CWWMH0196I message,
    which should read:
    CWWMH0196I: Business-level application
    "WebSphere:blaname=HelloWorldAsync" was started successfully.
    AND
    Just before step 7 the text indicates that a message is issued
    as follows:
    BLA: WebSphere:blaname=HelloWorldAsync State of BLA
    WebSphere:blaname=HelloWorldAsync is Started. This is changed
    to read:
    CWWMH0199I: Business-level application
    "WebSphere:blaname=DefaultApplication" was stopped successfully.
    
    (3) Topic, Stopping business-level applications using
    scripting, is updated. Step 4 indicates a message is issued as
    follows:
    BLA ID of stopped BLA if the BLA was not already stopped.
    This message now reads:
    CWWMH0199I: Business-level application
    "WebSphere:blaname=DefaultApplication" was stopped successfully.
    
    This update also applies to the V9.0 knowledge center.
    --------
    
    ID:
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH17297

  • 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

    2019-09-25

  • Closed date

    2019-10-16

  • Last modified date

    2019-10-30

  • 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 #: PH17297

Modified date: 30 October 2019