IBM Support

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

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 9.0 These issues were
    resolved as knowledge center updates in December, 2017.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  This APAR provides a cumulative list of     *
    *                  the documentation issues for Dec., 2017     *
    *                  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: As we update our knowledge centers, the following
    Version 9.0 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 9.0 issues will be addressed:
    
    ID: 248926(RTC) and PI90959
    Problem: Servlet security methods - explains various servlet
    security methods of the
    javax.servlet.http.HttpServletRequest interface. - BUT does
    not also indicate in the knowledge center that
    you need to enable security
    settings(Global Security and Application Security) if you use
    these security methods.  Errors can occur as a result.
    Resolution: Topic, Servlet security methods, is updated as
    follows:
    1) for authenticate - add another bullet to the AVOID TROUBLE
    note in this section that reads:
    AVOID TROUBLE: authenticate always returns "false" if global
    and application security are not enabled.
    
    2) for login - add another bullet to the AVOID TROUBLE note in
    this section that reads:
    AVOID TROUBLE: logon is a NOOP if global and application
    security are not enabled.
    
    3) for logout -  at the end of this section add an AVOID
    TROUBLE note that reads:
    AVOID TROUBLE: logout is a NOOP if global and application
    security are not enabled.
    
    4) for isUserInRole - add an AVOID TROUBLE note that
    reads:
    AVOID TROUBLE: isUserInRole returns "false" if global and
    application security are not enabled.
    
    This update also applies to V8.0 and V8.5
    -------
    
    ID: 250260 (RTC)
    Problem: V8.5 text in topic, Web server plug-in
    troubleshooting tips, identifies a message in detailed
    format, but the V9.0 format of the message is different and
    can cause confusion.
    Resolution: Topic, Web server plug-in troubleshooting tips,
    is updated.  The bullet section that describes how to
    determine whether there are network connection problems with
    the plug-in....  has a sentence that will now read:
    Typically you will see the following message when this
    is the case:
    Connection to hostname:port number failed (error code) : error
    message (local port port number)
    
    -------
    
    ID: 249860 (RTC)
    Problem: Information in knowledge center topic, Liberty
    Storing transaction logs in a relational database,
    insufficiently documents storing transaction logs in databases
    and leaves out much of the specifics.  The traditional
    WebSphere Application Server topic page has detail that should
    also appear in the Liberty topic.
    
    Resolution: Topic, Liberty:  Storing transaction logs
    in a relational database, is updated as follows:
    (1) First paragraph of topic now reads:
    You can, choose to store your Liberty transaction logs
    in a relational database rather than as operating system
    files. In traditional WebSphere Application Server, this
    feature provides high availability (HA) support without having
    to use a shared file system. For your Liberty , storing
    transaction service logs in a relational database is supported
    for production use.
    (2) Third paragraph in the About this task, section now reads:
    By default, Liberty transaction logs are stored in
    operating system files. However, you can configure the
    transaction logs to be stored in an RDBMS. You can use any
    database type that is supported by the Liberty .
    
    An application server can be configured to recover a different
    application server's logs. The original owning application
    server must not be running when using this procedure, it is
    typically employed in order to perform any outstanding
    transactional recovery when the transaction service logs are
    available but the original owning application server cannot be
    started.
    
    The principal of recovery is the same as for the
    traditional product.
    See the following resources for expanded information about
    recovery
       - Transaction Recovery in WebSphere Application Server -
    Liberty
       - Restarting an application server on a different host
       - Moving a transaction log from one server to another
    
    REMEMBER: Application servers MUST NOT be configured to use
    the same tables. Doing so may result in data integrity issues
    and log corruption.
    
    If a suffix is specified then the suffix is appended directly
    to both the name of the table and the index.
    
    (3) Step 2 (optional) in the Procedure, second paragraph now
    reads:
    For storing transaction logs in an RDBMS for an application
    server, each server must have its own tables. For a
    traditional product configuration, you specifiy a table
    suffix in the custom URL that is unique for each application
    server. WebSphere Application Server: Storing transaction and
    compensation logs in a relational database for high
    availability applies to the traditional product but
    demonstrates the creation of the suffix and table names. In
    Liberty the suffix is specified using the transaction element
    attibute, transactionLogDBTableSuffix. See Transaction Manager
    (transaction) for more information about
    transactionLogDBTableSuffix.
    (4) DDL structures for the old DB2 version are added as
    follows:
        The following DDL structures show how to create the tables
    on the old DB2 version:
    
        CREATE TABLE WAS_TRAN_LOG(
          SERVER_NAME VARCHAR(128),
          SERVICE_ID SMALLINT,
          RU_ID BIGINT,
          RUSECTION_ID BIGINT,
          RUSECTION_DATA_INDEX SMALLINT,
          DATA LONG VARCHAR FOR BIT DATA)
    
        CREATE TABLE WAS_PARTNER_LOG(
          SERVER_NAME VARCHAR(128),
          SERVICE_ID SMALLINT,
          RU_ID BIGINT,
          RUSECTION_ID BIGINT,
          RUSECTION_DATA_INDEX SMALLINT,
          DATA LONG VARCHAR FOR BIT DATA)
    
    The following DDL structures show how to create indexes for
    these tables :
    
    CREATE INDEX IXWSTRAN_LOG ON WAS_TRAN_LOG (RU_ID ASC,
    SERVICE_ID ASC, SERVER_NAME ASC)
    CREATE INDEX IXWSPARTNER_LOG ON WAS_PARTNER_LOG (RU_ID ASC,
    SERVICE_ID ASC, SERVER_NAME ASC)
    ---------
    
    ID: 784731 and 250318 (RTC)
    Problem: Information is confusing and inaccurate related to
    JAR file identification in topics, Data source minimum
    required settings for Oracle, and ,Creating a data source that
    uses the Oracle JDBC Driver for OCI
    Resolution:
    (1) Topic, Data source minimum required settings for Oracle,
    is updated as follows:
    Under requires the following JDBC driver files:
     - Change "ojdbc6.jar or ojdbc5.jar" to "ojdbcversion.jar",
    where version is italicized like in the avoid trouble section
    Under Avoid Trouble:
     - Remove "Oracle does not support the use of JDBC 4.0 APIs
    that are part of the Java SE Development Kit Version 6 or
    later when using ojdbc5.jar"
     - Remove "In mixed node environments, the data source wizard
    in the administrative console allows you to choose a class
    path for ojdbc6.jar or ojdbc5.jar"
    Under requires the following JDBC driver files:
     - Change "ojdbc6.jar or ojdbc5.jar" to "ojdbcversion.jar",
    where version is italicized like in the avoid trouble section
    Under Avoid Trouble:
     - Remove "Oracle does not support the use of JDBC 4.0 APIs
    that are part of the Java SE Development Kit Version 6 or
    later when using ojdbc5.jar"
     - Remove "In mixed node environments, the data source wizard
    in the administrative console allows you to choose a class path
    for ojdbc6.jar or ojdbc5.jar"
    
    Topic Creating a data source that uses the Oracle JDBC Driver
    for OCI, is updated as follows:
    Under Procedure 2f:
     - Change "ojdbc6.jar or ojdbc7.jar (if you are running Java 7
    or  later)" to "ojdbcversion.jar" where version is italicized
    like above
    - In best practice, change
    "${ORACLE_JDBC_DRIVER_PATH}/ojdbc6.jar" to
    "${ORACLE_JDBC_DRIVER_PATH}/ojdbc8.jar"
    Under What to do next section 3:
    Remove "The ojdbc6.jar can be used with Java 6 or Java 7. The
    ojdbc7.jar can only be used with Java 7."
    
    This update also applies to V7.0, V8.0, and V9.0.
    -------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI90959

  • 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

    2017-12-01

  • Closed date

    2018-01-31

  • Last modified date

    2018-04-10

  • 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: 900

Reference #: PI90959

Modified date: 10 April 2018


Translate this page: