PH39083: CORRECTIONS ARE NEEDED TO THE DOCUMENTATION FOR IBM WEBSPHERE APPLICATION SERVER VERSION 9.0

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 documentation updates in July
  2021.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the documentation issues for July 2021      *
  *                  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) and skill     *
  *                      cases. 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/skill cases, 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 https://www.ibm.com/docs/en/was-nd/9.0.5 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: 2238 (GHE) - Liberty
  
  Problem: The WebSphere Application Server Liberty for z/OS
  introduced a feature, automatic restart management for
  20.0.0.5 and the documentation was missing information:
  1) An addition to the topic, Liberty features, to identify the
  automatic restart management feature
  2) An important note to indicate that inorder to enable and
  activate the automatic restart management feature - you need
  to first install the feature using the intallUtility command.
  
  Resolution: Two documentation topics were updated:
  1) Topic, Liberty features, to identify the
  zosautomaticrestartmanger-1.0 feature
  2) Topic, Enabling the automatic restart management (ARM)
  feature on a server instance, that adds a note to remind the
  user that you need to install the ARM feature with the
  installUtility command before enabling and activating ARM on
  the system.
  
  -----------
  
  ID: 2387 (GHE) - Liberty
  
  Problem: WebSphere Application Server Liberty cannot
  support loading a resource adapter class from a shared library
  class loader. There is no way to associate the shared library
  with the resource adapter.
  This is the behavior as designed in WAS Liberty. The
  documentation should make this information known so as to keep
  from client errors.
  Resolution: Topic, Shared libraries, is updated. The opening
  paragraph of this topic will read:
  Shared libraries are files used by multiple applications. You
  can use shared libraries and global libraries to reduce the
  number of duplicate library files on your system. When
  properly configured, applications and resource adapters may
  access classes and resources of libraries, but the opposite is
  not true, libraries have no access to application or resource
  adapter classes or resources.
  
  ---------
  
  ID: 2429 (GHE)
  Problem: Liberty Server ARM function must have UPDATE access
  to the IXCARM.elementType.elementName entity when enabling the
  automatic restart managment (ARM) feature on a server instance
  the documentation does not indicate this fact.
  Resolution: Topic, Enabling the automatic restart management
  (ARM)feature on a server instance, is updated in the Before
  you begin section with a sentence that reads:
  You must have access to the couple data set format utility,
  IXCL1DSU, in SYS1.MIGLIB and have UPDATE access to the
  IXCARM.elementType.elementName entity.
  
  This update also applies to V8.5 documentation.
  -----------
  
  ID: 4732 (GHE)
  Problem: The customer is running on the Solaris platform and
  wanting to use protocol TLSv1.3 for connections.  The
  documentation does not explicitly identify the Solaris
  platform and its ability to support TLSv1.3
  Resolution: Topic, Creating a Secure Sockets Layer
  configuration, is updated. a third bullet to the note in
  step 14 is added that reads:
  
  TLSv1.3 is supported on AIX ? ?, Windows, and Linux ? ?. For
  Solaris, where your application server id is running on a JVM,
  the TLSv1.3 protocol is NOT supported.
  
  This update also applies to the V8.5 documentation.
  ----------
  
  ID: 4879 (GHE)
  Problem: Topic, Enabling Java EE applications to use mail
  resource
  with JavaMail, has an incorrect example in step 2 and needs
  correction.
  Resolution: Topic, Enabling Java EE applications to use mail
  resource with JavaMail, is updated
  
  1) The paragraph just before the example in step 2 now reads:
  When you create this reference, be sure that the name of the
  reference matches the name used in the code. For example, the
  previous code
  java:comp/env/mail/MailSession3 in its lookup. Therefore the
  name of
  this reference must be mail/MailSession3, and the type of the
  resource must be javax.mail.Session. After configuration, the
  deployment descriptor contains the following entry for the mail
  resource reference:
  
  2) The example is corrected and reads:
  <resource-ref>
     <description>description</description>
     <res-ref-name>mail/MailSession3</res-ref-name>
     <res-type>javax.mail.Session</res-type>
     <res-auth>Container</res-auth>
  </resource-ref>
  
  This update also applies to Version 8.5 level of the
  documentation.
  
  _______
  
  ID: 4889 (GHE)
  Problem: The documentation for  the setTraceSpecification
  configuration setting does not include the -persist optional
  parameter and a description of its use.
  
  Resolution: Two topics are updated to include the -persist
  parameter
  1) Server settings configuration scripts
  2) ServerManagement command group for the AdminTask object
  
  Topic (1)
  Under the section setTraceSpecification the -persist parameter
  is
  added to table 19 to read:
  persist
  Optionally, specifies how long the trace specification is to
  last.
  The
  default is -persist false and is only applied at JVM runtime. If
  JVM is restarted the trace specification is automatically
  removed.
  If you want the trace specification to continue even when the
  JVM is
  restarted, then you specify -persist true.
  
  Topic (2)
  Under the section setTraceSpecification the optional parameter s
  section is added and a description of the -persist parameter rea
  -persist
  Specifies how long the trace specification is to last. The defau
  -persist false and is only applied at JVM runtime. If the JVM is
  restarted the trace specification is automatically removed. If
  you
  want the trace specification to continue even when the JVM is
  restarted, then you specify -persist true. (String, optional)
  
  Batch mode examples are added for -persist, using JACL, Jython,
  Jython list as follows:
  Using Jacl with -persist:
  $AdminTask setTraceSpecification {-serverName server1 -nodeName
   -traceSpecification  com.ibm.*=all=enabled} -persist true
  
  Using Jython string with -persist :
  AdminTask.setTraceSpecification('[-serverName server1 -nodeName
   -traceSpecification  com.ibm.*=all=enabled  persist true]')
  
  Using Jython list with -persist:
  AdminTask.setTraceSpecification(['-serverName', 'server1',
    '-nodeName', 'node1',
        '-traceSpecification',  'com.ibm.*=all=enabled',
  '-persist',
  'true']}
  
  This update also applies to the Version 8.5 level of
  the documentation.
  
  ---------
  
  ID: 2424 (WebSphere Liberty)
  Problem: Missing information in topic, securityUtility command,
  needs to identify the use of AES-128 encryption.
  Resolution: Topic, securityUtility command, is updated.
  Parameter --
  encoding=encoding_type description adds a sentence that says,
  Currently, the aes type uses AES-128 encryption.
  Topic, Liberty: The limits to protection through password
  encryption, is updated with a first sentence that reads:
  Liberty supports AES-128 encryption for passwords that are
  stored in the server.xml file.
  
  ID: 4534 (Open Liberty)
  Problem: Missing information. Topic, Password encryption
  limitations
  needs to add text to indicate AES-128 encryption is supported.
  Resolution:
  (1) Topic, Password encryption limitations, is updated. The
  first paragraph has an additional sentence that reads:
  Currently,
  Open Liberty supports AES-128 encryption.
  (2) Topic, securityUtility encode command is updated.
  Parameter,--encoding=encoding_type description is updated to
  add the sentence,
  Currently, Open Liberty supports AES-128 encryption.
  (3) Topic, Server configuration security hardening, is updated.
  Under the section, Password encryption. The first paragraph is
  updated to add the sentence. Currently, Open Liberty supports
  AES-128 encryption.
  
  ID: 4699 (WebSphere Application Server)
  Problem: Missing information about the support of AES-128
  encryption.
  Resolution: Topic, Enabling AES password encryption for the
  server environment, is updated. the first paragraph of the
  topic has an addedd sentence that reads: Currently, Open
  Liberty supports AES-128 encryption.
  This update also applies to V8.5 level 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