PM55216: CORRECTIONS ARE NEEDED TO THE DOCUMENTATION IN THE INFORMATION CENTER FOR IBM WEBSPHERE APPLICATION SERVER VERSION 7.0.

APAR status

• Closed as documentation error.

Error description

• IBM WebSphere Application Server Version 7.0. These issues were
  resolved as information center updates in February, 2012.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the documentation issues for January        *
  *                  2012 that affect users of IBM WebSphere     *
  *                  Application Server Version 7.0.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Information Centers for WebSphere   *
  *                      Application Server Version 7.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: We update our information centers monthly. The following
  Version 7.0 modifications will be available in the
  February 2012 update to the Information 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 7.0 issues will be addressed:
  
  ID: PM55216
  Problem: During the Application Server shutdown procecess,
  com.ibm.ejs.util.am._Alarm might launch new threads that cause
  unnecessary exceptions from varied components. The fact
  that These exceptions can be ignored is not documented.
  
  Resolution: The following information will be added to the
  "About this task" section of the topic "Stopping an
  application server":
  
  Avoid Trouble: During the Application Server shutdown
  procecess, com.ibm.ejs.util.am._Alarm might launch new threads
  that cause unnecessary exceptions from varied components. For
  example, you might receive the following Connection Pool
  Manager exception:
  
  J2CA0020E: Connection Pool Manager could not allocate a
  Managed Connection:
  java.lang.IllegalStateException: Internal
  Error: cannot find the PoolManager Reference.
  
  These exceptions might occur because an application server
  must shut down all of the components under that application
  server's control before the stop process can complete. You can
  ignore these exceptions. After the application server stops,
  all running threads from the application server automatically
  end.
  
  This same change will be made to the Version 8.0 Information
  Center.
  --------------
  ID: 725451
  Problem: Under the item "Policy class name", the topic,
  "External Java Authorization Contract for Containers provi
  settings" states:
  
  "The class file must reside in the class path of each
  application server process. These processes include the
  application server, node agents and the deployment manager."
  
  This statement does not specifically state where the class
  file resides and can lead to confusion in its use.
  
  Resolution: This statement will be updated as follows:
  
  The class file for the custom JACC provider must reside in the
  WAS-INSTALL/lib/ext directory. This enables the application
  server, node agents, and the deployment manager to operate
  correctly.
  
  This same change will be made to the Version 8.0 Information
  Center.
  ---------------
  ID: 726380
  Problem: System output for the http_error.log is not showing a
  local timestamp; where http_access.log shows a local
  timestamp.  This inconsistency can be confusing when reviewing
  these logs.
  
  Resolution:  This inconsistent condition is how WebSphere
  Application Server is designed to work.  However, to highlight
  this condition, topic, "HTTP error, FRCA, and NCSA access
  settings" is updated as follows.
  
  The following information is added for the NCSA access log:
  
  - Entries in the NCSA access log contain a local time stamp.
  
  The following information is added for the HTTP error log:
  
  - HTTP error log format
      Entries in the HTTP error log contain a Greenwich Mean
  Time (GMT + 0) time stamp.
  
  This same change will be made to the Version 8.0 Information
  Center.
  --------------
  ID:726392
  Problem: It is not clear how to set the optional environment
  property integer, wasStartupPriority, which specifies the
  start order of multiple startup beans in the same Java Archive
  (JAR) file.  This environment property integer cannot be set
  with a command or through the administrative console.  A
  description of how to set this integer is needed.
  
  Resolution: Step 3 in the topic, "Using startup beans" is
  expanded with the following note:
  
  Note: The wasStartupPriority environment property integer
  cannot be set through either a command or the administrative
  console. This environment property integer is an EJB
  environment entry that is to be set by an application
  developer not an administrator. You set the integer value in
  the ejb-jar.xml file as shown in the example below:
  <env-entry>
    <env-entry-name>wasStartupPriority</env-entry-name>
    <env-entry-type>java.lang.Integer</env-entry-type>
    <env-entry-value>3</env-entry-value>
  </env-entry>
  
  As with any other EJB environment entry, you set a separate
  wasStartupPriority value for each EJB.
  
  This same change will be made to the Version 8.0 Information
  Center.
  ----------------
  ID: 726640
  Problem:  The following notification is possible after
  finishing a WebSphere Application Server migration and
  restarting the nodeagents:
  
  BBOO0220E: WMSG1623E: The WebSphere MQ messaging provider
  installed at
  /WAS70MUPS/N01/AppServer/profiles/default/installedConnectors/wm
  q.jmsra.rar has been updated and an application server restart
  is required to pick up this update. The WebSphere MQ messaging
  provider has been disabled.
  
  Resolution: To ensure that all steps in this migration are
  performed, Optional step 6 in the topic, "Installing WebSp
  MQ to interoperate with WebSphere Application Server" is
  expanded to add the following reminder concerning the MQ
  product.
  
  For any change in the MQ product (such as a PTF upgrade), you
  must restart the WebSphere Application Server and all nodes.
  
  This same change will be made to the Version 8.0 Information
  Center.
  
  -----------------
  ID: 726975
  
  Problem: Although the ibm-webservicesclient-bnd.xmi file has a
  property that can be used for JAX-WS web services, the
  information center states that this file is only used with
  Java API for XML-based RPC (JAX-RPC) Web services.
  
  Resolution: The topic "ibm-webservicesclient-bnd.xmi assembly
  properties for JAX applications" will be updated to address
  this issue:
  
  1. The title will be revised to reflect the applicability of
  JAX-WS services.
  
  2. The following note will be added at the beginning of the
  "Assembly properties" section:
     "Avoid trouble: The overriddenEndpointURI property is the
  only property that is applicable for Java API for XML-Based
  Web Services (JAX-WS) Web services."
  
  3. The following property will be added to the list of
  assembly properties:
     "overriddenEndpointURI: A property that specifies the
  final URL to which requests will be sent. When the client is
  run to invoke the web service, the request is sent to this
  property's URL, which takes precedence over the address given
  in the WSDL file and the client code. This property is the
  only property in the ibm-webservicesclient-bnd.xmi file which
  is applicable to JAX-WS services."
  
  These changes will also be made in the Version 8.0 information
  center.
  -------------------
  ID: 726194
  
  Problem: The LDAP URI advisor for Edge Components Load
  Balancer product uses a custom string for LDAP requests, which
  allows you to send the password in the request string. This
  request string is not RFC2255 compliant, though, but the
  information center states that the string should be compliant.
  
  Resolution: The "Configuring the LDAP URI advisor" topic in
  the Load Balancer Administration Guide, which is in the Edge
  Components information center, will be updated to read as
  follows:
  
  The string you use for the advisorrequest field must be
  compliant with the RFC2255 - The LDAP URL Format, but you need
  to format the string differently to work with Load Balancer.
  Specifically, RFC2255 does not allow for a password to be
  provided on the URL line, so Load Balancer has to take a
  modified string in the advisorrequest field, and convert that
  string to an RFC2255 compliant request.
  
  For example, a typical LDAP request might look like this:
     ldapsearch -x -H ldap://bluepages.ibm.com:389 -D
  "uid=973524897,c=us,ou=bluepages,o=ibm.com" -w MYPASS -b
  "ou=bluepages,o=ibm.com" mail=user@us.ibm.com
  
  To use this in Load Balancer's advisorrequest field, you
  should modify the string to look like this:
  
  ldap://bluepages.ibm.com:389/ou=bluepages,o=ibm.com??sub?(mail=u
  ser@us.ibm.com)?bindname=uid=973524897,c=us,ou=bluepages,o=ibm.c
  om?!bindpass=MYPASS
  
  To use this advisorrequest string with the dscontrol server
  command, your command would look like this:
     dscontrol server set cluster@server@port advisorrequest
  "ldap://bluepages.ibm.com:389/ou=bluepages,o=ibm.com??sub?(mail=
  user@us.ibm.com)?bindname=uid=973524897,c=us,ou=bluepages,o=ibm.
  com?!bindpass=MYPASS"
  
  Avoid Trouble: Be aware of the ?!bindpass=MYPASS extension
  that is used above. Replace MYPASS with the password that is
  used to authenticate the LDAP request.
  
  This topic will also be updated in the information center for
  Version 8.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