PH03442: CORRECTIONS ARE NEEDED TO THE DOCUMENTATION IN THE KNOWLEDGE CENTER 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 knowledge center updates in October, 2018.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the documentation issues for Oct., 2018     *
  *                  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: #779 (GHE)
  Problem: The topic, Liberty: Default port numbers, needs links
  to the endpoint details to make both the topic and the linked
  to topic more useable.
  Resolution: Topic,  Liberty: Default port numbers, is updated
  Specifics:
  (1) rtcomm-1.0 is removed from Table 1. Default port
  numbers of Liberty features
  (2) Links are placed into this topic for
  a. httpEndpoint - HTTP Endpoint (httpEndpoint) is linked to
  topic, HTTP Endpoint (httpEndpoint)
  
  b. sipEndpoint - SIP Endpoint (sipEndpoint) is linked to
  topic, SIP Endpoint (sipEndpoint)
  
  c. wasJmsEndpoint - WAS JMS Endpoint (wasJmsEndpoint) is
  linked to the topic, WAS JMS Endpoint (wasJmsEndpoint)
  
  -------
  
  ID: #782 (GHE)
  Problem: The customer is having trouble and
  runs into issues when their terminal emulator's session has the
  wrong Host code-page defined for their target server.
  Topic, securityUtility command, and topic,
  configUtility command, include the following CAUTION:
  CAUTION: Different operating system might treat some
  characters differently. For the Windows environment, if you
  have ! in your input string, it needs to be escaped by the ^
  character. For example,
  
  D:\Liberty\images\855\Liberty855\wlp\bin>configUtility
  createConfigFile="a^!"
  
  This CAUTION needs to add more details to help these issues.
  Resolution: Topic, securityUtility command, and topic,
  configUtility command, are updated with a replacement CAUTION
  that reads:
  CAUTION:
  Different operating systems and command line environments
  treat some characters differently. Many environments, such as
  Unix System Services on z/OS, allow you to redefine which
  characters are "special" and how they should behave.
  
  By default in the Windows environment, if you have an
  exclamation point (!) in your input string it needs to be
  escaped by the caret character (^).
  For example, encoding "a!" would be written as:
  D:\Liberty\images\855\Liberty855\wlp\bin>securityUtility
  encode "a^!"
  
  In other cases, or on other operating systems, you may need to
  use single quotes around the arguments being passed to the tool.
  Additionally, if you use a terminal emulator, make sure your
  session is configured to use the same code-page as your server.
  Please refer to your operating system, command shell, and
  terminalemulator's documentation about "special characters" and
  code-pages if you experience unexpected results.
  
  ------
  ID: #424 and 789427
  Problem: Topic,Host alias settings, documents a range for port
  settings of 0 - 65535.  However, when the port setting is set
  to zero "0" and error message occurs which says, "The field,
  Port, does not contain a valid value."  This topic needs to be
  update with the correct port range.
  Resolution: Topic, Host alias settings, is updated with the
  correct port value range for the port setting.  The port
  description of the range is updated to read:
  Range  1 - 65535 or the wildcard value (*)
  
  This update also applies to the V8.5 level of the knowledge
  center.
  
  ------
  
  ID: #434 (GHE)
  Problem: When migrating to V9.0 customer noticed that the
  administrative console displayed non-functional
  items that in V8.5 were functional. This anomolie only occurs
  in a unique URI authentication situation. Diagnosis with L3
  console support and security helped the customer with an
  adjustment script, which restored the items in the
  administrative console to functional. An update to the
  appropriate KC topic providing this "adjustment script" will
  serve customers in the future.
  Resolution: Topic, Web authentication settings, is updated.  A
  NOTE is added to the section entitled, Use available
  authentication data when an unprotected URI is accessed.  The
  Note reads as follows:
  
  Note: When this option is NOT selected and the Authenticate
  only when the URI is protected option is selected, the
  administrative console user interface can display several
  non-functional items that can be made functional by setting
  the enableSecurityIntegration flag to false. Follow these
  steps to correct this condition:
  
     (1) Save the following commands to a python file (for
  example,
  updateDeployment.py ) under the profile bin directory. The
  commands shown below sets the enableSecurityIntegration flag
  to false :
  
      isclite = AdminConfig.getid("/Deployment:isclite/")
      iscliteDepObject = AdminConfig.showAttribute(isclite,
  "deployedObject")
      attr1 = ['enableSecurityIntegration', 'false']
      attrs = [attr1]
      configs = AdminConfig.showAttribute (iscliteDepObject,
  "configs")
      appConfig = configs[1:len(configs)-1]
      SM = AdminConfig.showAttribute (appConfig,
  'sessionManagement')
      AdminConfig.modify (SM, attrs)
      AdminConfig.save()
  
     (2) Run wsadmin.bat -f your_script_name.py from the same
  profile bin directory.
     (3) Restart the server and verify that the administrative
  console displays correctly.
  
  -------
  ID: #898 (GHE)
  Problem: WebSphere Application Server-traditional topic is
  showing up in the Liberty knowledge center and causing
  confusion.
  Resolution: The WebSphere Application Server-
  traditional topic, Examples to migrate to EE Concurrency from
  Asynchronous beans and CommonJ, has the same content as the
  Liberty topic, Example API tasks that implement Concurrency
  Utilities for Java EE, and the CommonJ Timer and Work Manager
  are not available in Liberty.  Therefore, the liberty topic,
  Example API tasks that implement Concurrency
  Utilities for Java EE, is removed the Liberty knowledge
  center.
  
  --------
  ID: #319
  Problem:  There is need to clarify Apache Install options
  when moving from IHS V8.5, Apache 2.2 to z/OS V2R3 and WAS
  9.0.0.8.  in the knowledge center.
  Resolution:
  

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