PI76112: IHS9.0 SHOULD USE VARIABLE LDAPTIMEOUT INSTEAD OF LDAP.SEARCH.TIMEOUT

APAR status

• Closed as documentation error.

Error description

• http://www.ibm.com/support/knowledgecenter/SSEQTJ_9.0.0/com.ibm.
  webspher
  e.ihs.doc/ihs/tihs_convertmodibmldap.html
  
  Table 1. LDAP configuration directives conversion
  
  shows
  
  mod_ibm_ldap                mod_ldap
  
  ldap.search.timeout         LDAPSearchTimeout
  
  
  
  Now,
  
  http://www.ibm.com/support/knowledgecenter/SSEQTJ_9.0.0/com.ibm.
  webspher
  e.ihs.doc/ihs/tihs_convertmodibmldap.html
  
  indicates that the correct variable for a LDAP search timeout is
  
  LDAPTimeout Directive
  Description: Specifies the timeout for LDAP search and bind
  operations,
  in seconds
  Syntax: LDAPTimeout seconds
  Default: LDAPTimeout 60
  Context: server config
  Status: Extension
  Module: mod_ldap
  Compatibility: Apache HTTP Server 2.3.5 and later
  

Local fix

• Need fix on IHS v9.0
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the documentation issues for month_year     *
  *                  that affect users of IBM WebSphere          *
  *                  Application Server Version 8.0.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Knowledge Centers for WebSphere     *
  *                      Application Server Version 8.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

• CORRECTIONS ARE NEEDED TO THE DOCUMENTATION IN THE KNOWLEGE
  CENTER FOR IBM WEBSPHERE APPLICATION SERVER VERSION 8.0
  
  This APAR describes the issues that customers encountered with
  IBM WebSphere Application Server Version version_number. These
  issues were resolved as knowledge center updates in March,
  2017.
  
  Note: We update our knowledge centers monthly. The following
  Version 8.0 modifications will be available in August, 2017
  update to the Knowledge Centers. 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 8.0 issues will be addressed:
  
  ID: PI67112
  Problem: On a WebSphere Application Server V8.0 system, the
  customer detected an anomolie in a knowledge center topic.
  The topic, LDAP directive migration, for the V8.0 and
  V8.5 topic indicates to convert the ldap.search.timeout=10
  directive to LDAPSearchTimeout=10.  The customer is migrating
  to V9.0 and in the V9.0 version of the topic,  the same
  conversion is documented, but has changed for V9.0 to:
  Converting ldap.search.timeout=10 to LDAPTimeout=10.  This
  documentation error needs to be corrected for V9.0 only.
  Resolution:  The topic, LDAP directive migration, for the
  V9.0 is updated to that the ldap.search.timeout directive
  reads to convert  ldap.search.timeout=10 to LDAPTimeout=10.
  
  V8.0 and V8.5 levels of this topic remain as documentated.
  
  This update applies ONLY to V9.0 of the knowledge center.
  --------------
  ID: 779716
  Problem: Customer is not clear on handling two applications
  that have the same applicationname data source at scope
  independently.  The JNDI appears to be overwritten and this is
  unexpected.  Clarification of processing is required in the
  knowledge center. If two enhanced applications have
  application scope data source with the same name, unexpected
  overwrite will happen. When the second application is
  deployed, the resource for the 2nd application will be also
  used by the first application due to this unexpected
  overwrite. This behavior resulted into a product limitation and
  the two applications can't have the same jndi data source
  name.
  Resolution: Topic, Administrative console scope settings, is
  updated. In this topic, just before the explanation of "cell"
  the following note is inserted:
  AVOID TROUBLE: Two applications CANNOT have the same
  application name data source at the scope level and operate
  independently with that resource.  Specifically, having
  multiple applications use the same JNDI name with different
  resources can cause the overwriting of the resource's JNDI
  bindings.
  This update also applies to V8.5 and V9.0 of the
  knowledge
  center.
  ------------
  ID: 780010
  Problem: Topic, Operating and managing Load Balancer, contains
  a sentence as follows:
  You can change the FIN timeout using the dscontrol executor
  set fincount command. But the fincount command is deprecated
  and should be the  fintimeout command.
  Resolution: Topic, Operating and managing Load Balancer, is
  updated correcting the subject sentence to read:
  You can change the FIN timeout using the dscontrol executor
  set fintimeout command.
  
  This update also applies to V8.5 and V9.0
  ----------
  ID: 780436
  Problem: In the topic, Session management custom properties,
  the description of item:
  UseOracleBLOB  has the following sentence:
  --Due to an Oracle restriction, BLOB support requires use of
  the Oracle Call Interface (OCI) database driver for more than
  4000 bytes of data. --
  This information is obsolete and incorrect for V8.0
  releases as later and needs to be removed from the
  description.  The customer was confused about the content.
  Resolution: Topic, Session management custom properties, is
  updated.  The UseOracleBLOB description is changed and removes
  the incorrect sentence.
  
  This update also applies to V8.5.5 and V9.0 of the knowledge
  center.
  -----
  
  ID: 248933 (RTC) and 783783
  Problem: Customer is trying to use properties files to
  replicate or merge environments.  The knowledge center topic,
  PropertiesBasedConfiguration command group for the AdminTask
  object using wsadmin scripting, has the warning: Use
  properties files to customize, not replicate or merge
  environments. Do not extract an entire Cell, Node, Server, or
  ServerCluster to apply to a different environment.  Another
  appropriate topic, Applying portable properties
  files across multiple environments, should also have this
  warning.
  Resolution: topic, Applying portable properties files
  across multiple environments, is update with the AVOID TROUBLE
  note that reads:
  AVOID TROUBLE: Use the properties files to customize
  environments. Do not use properties files to replicate or
  merge environments. Do not extract an entire Cell, Node,
  Server, or Cluster to apply to a different environment.
  
  This update also applies to V8.5 and V9.0.
  ----
  
  ID: 782947
  Problem: Over several WAS releases, customers have tried using
  the manageprofiles command and the -restoreProfiles options to
  migration to another machine.  It has not been clear how to do
  this and clarification is necessary.
  Resolution: Topic, manageprofiles command, is updated.
  Specifically, in the section describing the -restoreProfile
  option - the following text is added at the end of this
  section:
  Attention: manageProfiles -restoreProfile is best used to
  restore a profile on the same machine, host, or install.
  However, you can use -restoreProfile on another machine where
  the is at the same service level as the source machine. In
  this case, ensure that the directory structure of the second
  machine is the same directory structure that existed on the
  source machine when the manageProfiles -restoreProfile command
  was used.
  
  This update also applies to V8.5 and V9.0
  ------
  
  ID: 784619 and 250141 (RTC)
  Problem: The Dynamic outbound endpoint SSL configuration
  settings, topic needs an update, because some specific
  information is missing to the hostname IP configuration
  settings.
  Resolution: TOpic, Dynamic outbound endpoint SSL configuration
  settings, is updated as follows:
  A CAUTION note is added to the Add connection section of this
  topic that reads:
  CAUTION: A text comparison is performed between the SSL Dynamic
  configuration and connection information that is obtained from
  the runtime. Although HTTP connections use host names, IIOP
  connection information is usually the IP address of the target
  host instead of the host name of the target host. The only
  exception is if you do IIOP HTTP tunneling. For more
  information, see the topic on enabling http tunneling. Create
  a configuration with the IP address for IIOP requests, unless
  you are doing tunneling.
  
  This update also applies to V8.5 and V9.0
  ----
  

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