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

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

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the documentation issues for June, 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: 1297 (GHE)
  Problem: Topic, SSL configuration settings, describes settings
  for Default server certificate alias and Default client
  certificate alias.  Extra information is needed when using
  a localOS SAF security provider, such as RACF. The
  Certificates aliases displayed are obtained by querying all
  started processes (including controller, servant or adjunct
  regions), via an mbean, in the selected management scope at
  time of display. As such, the server processes (including
  controller, servant or adjunct regions) in the SSL management
  scope may or may not utilize the same keyring and process
  user.  Errors can result.
  Resolution: Topic, SSL configuration settings, is update for
  Default server certificate alias and Default client
  certificate alias to add the following note:
  Avoid Trouble:
  ZOS Platform: Beware when using the localOS SAF security
  provider, such as RACF. The Certificates aliases displayed are
  obtained by querying all started processes (including
  controller, servant or adjunct regions), via an mbean, in the
  selected management scope at time of display.
  
  The server processes (including controller, servant or adjunct
  regions) in the SSL management scope may or may not utilize
  the same keyring and process user. Because of this, you should
  not assume that all certificate aliases in the list are
  available for use. Please query the SAF security provider to
  be sure the safkeyring for each process ID contains the alias
  in question.
  
  When selecting a personal alias it must be connected to both
  the control and servant region keyring. Assigning an alias
  that does not exist in all the target server
  processes(Controller, Servant, Adjunct) keyring may result in
  SSL initialization and/or SSL runtime errors. Initialization
  errors could prevent all SSL behavior. For example, selecting
  a personal certificate that exists only on the servant region
  userid keyring could break inbound SSL to the control region,
  and selecting a personal certificate that exists only on the
  control region userid keyring could break outbound SSL from
  the servant region.
  
  Consider utilizing SSLConfigGroups instead. SSLConfigGroups
  will prevent SSL initialization errors. Although SSL runtime
  errors can still occur if the certificate alias is not found
  in the process safkeyring.
  
  This update also applies to V9.0 level of the knowledge center.
  -------
  
  ID: #1274 GHE
  Problem: The Edge ULB Guide command syntax is incorrect for
  dscontrol port.  Errors can occur in usage.
  Resolution: The Edge topic, dscontrol port syntax diagram is
  updated for the add cluster@port@seervrer and set for
  cluster@port@seervrer operand.
  
  This update also applies to V9 level of the knowledge center.
  ------
  
  ID: #1692
  Problem: LogViewer command line tool describes the -format
  parameter with a keyword value of JSON.  In V8.5.5.16 support
  for JSON was introduced, but this topic does not identify that
  JSON applies to 8.5.5.16+ and should.
  Resolution: Topic, LogViewer command line tool is updated for
  the -format parameter by identifying the description using a
  8.5.5.16 icon as follows:
  format basic | advanced | cbe-1.0.1 | [8.5.5.16 or later]json
      Specifies the output format. Supported formats include
  basic, advanced, [8.5.5.16 or later]JSON, and the CBE-1.0.1
  format. If you do not provide this information, the output is
  in basic format.
  
  --------
  ID: #1742
  Problem: The knowledge center has a topic, Preparing Red Hat
  Enterprise Linux 7 for installation, but with Red Hat
  Enterprise Linus 8 a similar topic is required in the
  knowledge center.
  Resolution: Topic, Preparing Red Hat Enterprise Linux 8 for
  installation, is a new topic in the knowledge center as reads
  as follows:
  Preparing Red Hat Enterprise Linux 8 for installation
  
  You must complete additional steps to prepare a Red Hat
  Enterprise Linux Version 8 system for a WebSphere ? ? Applicatio
  Server installation.
  Before you begin
  
  Complete all steps in **** MISSING FILE ****. Those steps are
  common to installing WebSphere Application Server on any Linux
  system.
  About this task
  
  After you complete the common steps that are required to
  install any Linux system, you must also complete extra
  system-specific steps that are required for Red Hat Enterprise
  Linux Version 8.
  
  Verify that the prerequisite packages are installed. A Linux
  package registration limitation prevents the prerequisites
  checker program from examining prerequisite packages on Linux
  systems. See **** MISSING FILE **** for more information.
  If Security-Enhanced Linux (SELinux) is enabled and enforced
  on your Red Hat Enterprise Linux Version 8 operating system
  while you are installing the product from the disk, mount the
  disk with the following option:
  
  -o context=system_u:object_r:textrel_shlib_t:s0
  
  Important: If you are using Red Hat Multi Level Security
  (MLS), review the final s0 parameter.
  Procedure
  
      Edge Caching Proxy (32-bit) requires the 32-bit
  compat-libstdc++33 package to be installed.
      On all hardware platforms, install all required packages
  and their dependencies by running the following yum command:
  
      yum install gtk2 libXtst xorg-x11-fonts-Type1 psmisc
  
      The gtk2, libXtst, and xorg-x11-fonts-Type1 packages are
  required for graphical IBM Installation Manager and Profile
  Management tool support. The psmisc package provides support
  for basic installation and profile creation.
      On POWER systems, ensure that the kernel level is set to a
  minimum of 3.10.0-123.6.3.el7. Run the following command:
  
      uname -r
  
      For POWER ? ? Little Endian (LE), review the following
  platform-specific limitations:
          Edge Caching Proxy is not supported on this
  architecture.
          Load Balancer for IPv4 and IPv6 components Content
  Based Routing (CBR) and Site Selector are not supported.
          Load Balancer for IPv4 and IPv6 requires the IBM ? ?
  Advanced Toolchain 7.1 runtime packages. For more information,
  see the IBM Advance Toolchain for PowerLinux ? »   ¢ ? documenta
  
  Results
  
  If you do not install all of the required packages, the
  installation does not complete correctly. Error messages
  indicate missing libraries, the inability to load graphical
  interfaces, or other errors that occur during the installation.
  
  This new topic will also be part of the V9.0 knowledge center.
  ------
  
  ID: #1944
  Problem:  The client was having the issue with running this
  servlet,  IBMTrackerDebug. Topic
  HTTP session manager troubleshooting tips,  indicates to access
  the servlet by using its servlet class name, but this is a
  security vulnerability so is no longer allowed by default.
  The client needs to use the web container custom
  property
  "com.ibm.ws.webcontainer.disallowserveservletsbyclassname=false"
   as a workaround.  This property is not documented in the
  knowledge center and should be.
  Resolution: Topic, HTTP session manager troubleshooting tips,
  updated by adding the following sentence under the link in the
  topic,  link
  http://localhost:9080/servlet/com.ibm.ws.webcontainer.httpsessio
  n.IBMTrackerDebug.  The sentence reads:
  To enable serve by class name feature, please set Web
  container custom property
  "com.ibm.ws.webcontainer.disallowserveservletsbyclassname=false"
  .
  
  This update also applies to the V9.0 knowledge center.
  -----
  
  ID: #1692 (GHE)
  Problem: Customer is at V8.5.5.15 and ran the logviewer using
  the -format parameter with json and it FAILED. Customer is
  using the V8.5.5.15 level of the knowledge center and the
  json parameter is documented. When the customer issued
  logviewer.sh -help format, the json parameter
  is not included - the knowledge center should clarify at what
  fixpack level the json parameter is valid to use.
  Resolution: Topic, LogViewer command-line tool, is update the
  -format parameter is updated to read:
  -format basic | advanced | cbe-1.0.1 | [8.5.5.16 or later]json
      Specifies the output format. Supported formats include
  basic, advanced, [8.5.5.16 or later]JSON, and the CBE-1.0.1
  format. If you do not provide this information, the output is
  in basic format.
  
  This Topic is similarly updated for V9.0 and the 9.0.0.10
  icon is used to qualify the use of the JSON option.
  -------
  

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