PH10601: CORRECTIONS ARE NEEDED TO THE DOCUMENTATION IN THE KNOWLEDGE ENTER FOR IBM WEBSPHERE APPLICATION SERVER VERSION V8.5

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 April, 2019.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the documentation issues for March, 2019    *
  *                  This APAR provides a cumulative list of     *
  *                  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: PH10601 and #873 (GHE)
  Problem: Topic, Optimized local adapters for z/OS APIs
  article is missing description for Return Code 12 and Reason
  Code 15.  The knowledge center needs to add this information.
  Resolution: Topic, Optimized local adapters for z/OS APIs , is
  updated to add return code 12 and reason code 15 as follows:
  (1) The following functions - connection release, send
  request, send response, send response exception, receive
  request any, request specific, receive response length, and get
  message data have return code 12 and reason code 15 added with
  a DESCRIPTION that reads:
  The connection handle used for this call is not valid for this
  client.
  and an ACTION that reads:
  Ensure the connection is for the correct client. If the
  problem persists. Unregister and reregister the client.
  
  (2) The following functions: - invoke and host service have
  return code 12 and reason code 15 added with a DESCRIPTION
  that reads:
  A valid connection could not be obtained from the connection
  pool.
  and an ACTION that reads:
  Ensure the registration name used by the client is unique
  within the WebSphere daemon group.  Ensure that the API is
  being driven from the same address space that registered the
  client.  If the problem persists, unregister and reregister
  the client.
  
  This update also applies to V9.0 level of the knowledge center.
  --------
  
  ID: 791336
  Problem: For topic, Disabling WebSphere MQ functionality in
  WebSphere Application Server, the section What to Do Next is
  incomplete.
  If the MQ functionality has been disabled in the app server the
  WMSG2016I message is not output - the correct message is
  WMSG1720I. When MQ functionality has been disabled in the
  client WMSG2016I is the correct message that is output
  (WMSG1720I is not output in the client).  Both conditions need
  to be documented.
  Resolution: Topic,Disabling WebSphere MQ functionality in
  WebSphere Application Server, is updated.  The What to do Next
  section now reads:
  When the server starts, it is possible to detect whether IBM
  MQ functionality has been disabled on that server because
  messages with the following IDs are output:
  WMSG1720I is output when the server starts if IBM MQ has been
  disabled.
      CWSIC3650I is output once for any configured IBM MQ links
  that are running on the server.
      CWSIC3713I is output once for any configured IBM MQ client
  links that are running on the server.
  
  When the client starts, it is possible to detect whether IBM
  MQ functionality has been disabled on that client because a
  message with the following ID is output:
  WMSG2016I is output when the client starts if IBM MQ has been
  disabled.
  
  This update also applies to V9.0 level of the knowledge center.
  -------
  
  ID: #926 (GHE)
  Problem:  vmmsampleadapter.jar was in Developer works for
  download but has be withdrawn. Customers still want to use it.
  So the JAR file needs a new home and the knowledge center need
  updating to accommodate vmmsampleadapter.jar.
  Resolution: Three knowledge center topics are updated to
  restore a location where vmmsampleadapter.jar can be downloaded.
  (1) Establishing custom adapters for federated repositories
  (2) Configuring custom adapters for federated repositories
  using wsadmin - Step 3 now reads:
  Download the vmmsampleadapter.jar file from LINK. Copy
  samplevmmsampleadapter.jar file to the product classpath. The
  preferred location is the app_server_root/lib/ext directory.
  This should be copied to the classpaths of all the product
  processes (cell and all NodeAgents). If you created a custom
  adapter, use that jar instead of the vmmsampleadapter.jar.
  (3) Sample custom adapters for federated repositories examples
  
  This update also applies to V9.0 level of the knowledge center.
  -----
  
  ID: 791069 and #2572 (GHE)
  Problem: WSDM, which is deprecated in V7.0 and has not been
  used for 2-3 years. Approximately 18 topics in the KC need
  to either be deleted or updated (per links and such)
  so as to remove WSDM from the knowledge center. Clients need
  to know the status of WSDM in the product.
  Resolution: Topic, Creating a monitor for WebSphere
  Application Server for WSDM resources (deprecated), is
  updated. A new paragraph is added to the Deprecated feature
  note that reads:
  The Web Services Distributed Management (WSDM) monitoring
  support provided in the Version 6.1 Feature Pack for Web
  Services came with a built-in code sample, a wsdm-demo.jar
  file in the product that you could use to retrieve the
  statistics for a servlet resource, The wsdm-demo.jar file is
  not available and will not be available in the future. Instead
  of following steps in this topic to create a WSDM monitor and
  use WSDM, you can administer your web services applications
  with the administrative console or scripting. WSDM remains
  part of the product and is supported in this state.
  
  This update also applies to version V9.0 of the knowledge
  center.
  -----------
  
  ID: 791337 and 4591 (GHE)
  Problem: While it may look like you can simply slide in the
  new intermediate signer certificate into the chain and have
  things working again, this is not a recommended action to
  take.  It is the best course of action to regenerate the
  entire chain (and that means a new certificate request) to
  ensure the certificate is fully chained and functional, as
  simply replacing the intermediate, or even reimporting the old
  certificate, may not work as intended. There is insufficient
  documentation that highlights this to customers.
  Resolution: Several topics are updated with the following NOTE:
  
  IMPORTANT: For an expired certificate chain or an expired
  certificate authority (CA) certificate chain, you are required
  to update the entire chain. You must generate a new
  certificate chain that has the individual signer certificates.
  For a CA certificate chain, this may require importing a new
  certificate chain, usually through a new certificate request
  file (CSR).
  Topics update with this note are:
  1)Secure communications using Secure Sockets Layer (SSL)
  2) Creating a certificate authority request
  3) Configuring certificate expiration monitoring
  Also
  4) A new section, Handling expired chained certificates, is
  added
  to topic, SSL errors for security, which reads:
  
  when you have to replace part of a certificate chain,
  including CA (certificate authority) certificates and an
  individual part of a certificate chain has expired, you are
  required to update the entire chain. Specifically, for chained
  self-signed certificates, you have to create a brand new
  certificate chain in the keystore or renew the self-signed
  certificate. For a CA certificate chain, you
  are usually required to request a brand new certificate chain
  from your CA by presenting them with a new certificate request
  file (CSR) so that a new CA certificate chain can be generated.
  AND
  a related reference to topic, Renewing a certificate in SSL,
  is added to the related reference section of the topic, SSL
  errors for security.
  
  This update also applies to version V9.0 of the documentation.
  -------
  

Temporary fix

Comments

APAR Information

• 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