PH55032: CORRECTIONS ARE NEEDED TO THE DOCUMENTATION 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 documentation updates in June, 2023.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the                                         *
  *                  documentation issues for June 2023 that     *
  *                  affect                                      *
  *                  users of IBM WebSphere Application Server   *
  *                  Version 8.5.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Documentation for WebSphere         *
  *                      Application Server Version 8.5 need to  *
  *                      reflect customer enhancement requests   *
  *                      received in skill cases or 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 skill cases or PMRs,
  and
  the documentation change or changes that will address these
  issues.
  

Problem conclusion

• Note: As we update our documentation, 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/docs/en/was-nd/8.5.5 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: #6655
  Problem: Topic, Connection pool custom property,
  globalConnectionTypeOverride, is missing detailed information on
  how to add this connection pool property.  This missing
  information is causing customers to make errors and produce
  failed processing.
  Resolution: Topic, Connection pool custom properties, is updated
  for the globalConnectionTypeOverride property with the specifica
  naviation instructions to add connection pool properties.
  
  These instructions now read:
  Important:
  To set this property correctly, follow these navigation details
  using the administrative console.
  Click Resources > JDBC > Data sources > Select the data source >
  Under Additional Properties, click Connection pool properties >
  Under Additional Properties, click Connection pool custom
  properties > click New to add globalConnectionTypeOverride > OR
  click > globalConnectionTypeOverride to update its current value
  as appropriate.
  
  This property must be set in the Connection pool custom
  properties and NOT the general Custom properties on the data
  source.
  If you specify values for both the defaultConnectionTypeOverride
  and the globalConnectionTypeOverride properties, only the value
  that is specified for the globalConnectionTypeOverride property
  is used to determine the connection sharing type.
  
  Also, the topic, Tuning connection pools, is update with the
  details instructions for setting the connection pool properties.
  Under the step - Control connection pool sharing. the following
  is added
  (1)
  Important: If you specify values for both the
  defaultConnectionTypeOverride and the
  globalConnectionTypeOverride properties, only the values
  specified for the globalConnectionTypeOverride property are used
  to determine connection sharing type.
  
  (2)
  To add these new custom properties to the settings for a data
  source or connection factory connection pool, a new connection
  pool custom property must be created.
  To add one of these properties to a data source, use the
  administrative console. Click Resources > JDBC > Data sources.
  Select your data source from the list. Then under Additional
  Properties, click Connection pool properties > Connection pool
  custom properties > New. Now specify
  defaultConnectionTypeOverride or globalConnectionTypeOverride in
  the Name field and shared or unshared in the Value field.
  For other J2C or JMS connection factories, navigate to the
  connection factory definition in the administrative console.
  Then under Additional Properties, click Connection pool >
  Connection pool custom properties > New. Now specify
  defaultConnectionTypeOverride or globalConnectionTypeOverride in
  the Name field and shared or unshared in the Value field.
  Important: The properties must be set in the Connection pool
  custom properties and NOT the general Custom properties on the
  data source or connection factory.
  
  This update also applies to the V9.0 level of the documentation.
  -------
  
  ID: #6681
  Problem: Customer asks - Is there a way to check in wsadmin. we
  are planning to implement below to resume to job if the
  connection is paused, want to status without going to admin
  console.??
  Resolution: Topic, Managing the message endpoint lifecycle using
  wsadmin scripting,
  Procedure steps are added as follows:
  - Reactivate the message endpoint or activate a message endpoint
  that started out in a deactivated state.
  Use the following commands to cache the instance and reactivate
  the message endpoint:
  objectName=AdminControl.queryNames('*:name=JMSMDB_MessageEndpoin
  t,*')
  AdminControl.invoke(objectName, 'resume')
  
  The command returns the following output:
  Message Endpoint JMSMDB_J2CMessageEndpoint is activated
  
  - Query the status of the message endpoint.
  Use the following commands to cache the instance and query the
  status of the message endpoint:
  
  objectName=AdminControl.queryNames('*:name=JMSMDB_MessageEndpoin
  t,*')
  AdminControl.invoke(objectName, 'getStatus')
  
  The command returns the status of 1 if the message endpoint is
  running and 2 if the message endpoint is paused.
  
  This update is also made for the V9.0 level of the
  documentation.
  -------
  
  ID: 6841
  Problem: Topic, Scheduler daemon, is missing information on the
  number of tasks that the scheduler daemon can process.
  Resolution: Topic, Scheduler daemon, is updated with the
  following information: The number of tasks that the scheduler
  daemon can process depends on various factors. The performance
  of the environment must be high enough and the poll cycle
  must be long enough so that all the tasks are read within the
  poll cycle. The server and the database must also be able to
  handle the load within the poll cycle. The scheduler daemon
  caps the number of tasks that can be read within a poll cycle
  to a value that is far more than needed in typical usage.
  
  This update is also made for the V9.0 level of the
  documentation.
  -------
  
  ID:
  

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