PI08804: THE LOCATION AND NAME ALUES OF THE IHS HTTPD.CONF CONFIGURATION FILE IS HARD CODED IN THE SETUPADM.ANT SCRIPT.

APAR status

• Closed as documentation error.

Error description

• Corrections are needed to the documentation in the IBM
  WebSphere Application Server version 8.5 Information Center
  
  For the configuration for PCT, the default httpd.conf file
  within the <IHS_HOME>/conf/ directory is used.
  
  The location value and name for the httpd.conf file is hard
  coded in the SetupADM.ant script, as follows:
  
  <exec dir="${IHS_HOME}/bin"
  executable="${IHS_HOME}/bin/setupadm"
  append="true"
  failonerror="false"
  output="${IHS_HOME}/logs/postinstall/setupadm.log"
  resultproperty="setupadm.result">
  <arg value='-create'/>
  <arg value='-usr'/>
  <arg value='${ADMUSER}'/>
  <arg value='-grp'/>
  <arg value='${ADMGRP}'/>
  <arg value='-cfg'/>
  <arg value='${IHS_HOME}/conf/httpd.conf'/>
  <arg value='-adm'/>
  <arg value='${IHS_HOME}/conf/admin.conf'/>
  </exec>
  
  This restricts the user from using a customized IBM HTTP Server
  configuration file with a different name or location.
  
  The behavior cannot be changed to allow an input parameter of
  the configuration file that is being specified by PCT.
  
  Corrections are needed in the test connection sample code.
  
  Currently the separator in the resURI specification is a colon
  ":"
  The system will error if this character is used
  The separator needs to be a vertical bar "|" -
  for instance:
  "cells/cat/nodes/cat:resources.xml#DataSource_1";
  should be
  "cells/cat/nodes/cat|resources.xml#DataSource_1";
  
  If a customer copies the code testConnection sample code
  from the Information Center, the resulting code will compile,
  however it will fail to execute.
  

Local fix

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.5.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Information Centers for WebSphere   *
  *                      Application Server Version 8.5 need     *
  *                      to reflect customer enhancement         *
  *                      requests received in problem            *
  *                      management records (PMRs). These        *
  *                      enhancements can include fixing         *
  *                      technical inaccuracies or clarifying    *
  *                      vague information.                      *
  ****************************************************************
  * RECOMMENDATION:  Add documentation stating that the          *
  *                  httpd.conf file must not be removed under   *
  *                  the <IHS_HOME>/conf directory.              *
  ****************************************************************
  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 8.5 modifications will be available in the month_year
  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.
  
  ID: PI08804
  Problem :  The setupadm.sh script is used to configure IBM
  HTTP Server.  The configuration file httpd.conf is hard coded
  in this script file and cannot be altered by the user.  Users
  must be informed of this restriction.
  
  Resolution: Topic,  Configuring IBM HTTP Server, is updated
  with the following restriction statement:
  Restriction: To successfully configure the server, the name of
  the configuration file must be retained as httpd.conf.
  
  Topic, Configuring a web server plug-in using the pct tool, is
  updated with following restriction statement when specifying
  the webServerConfigFile1 parameter:
  Restriction: To successfully configure the server, the name of
  the configuration file must be retained as httpd.conf.
  -----------
  ID: 756807
  Problem: Topic, rprf_sipdatacounter bad xref has several
  erroneous cross reference links that need to be fixed.
   Resolution: Topic, rprf_sipdatacounter is updated to fix
  these
  erroneous links.
  -----------
  ID: 756981
  Problem :  Topic, Test connection service, has a code example
  that has error in its specification.  Specifically,
  ines that specify "resURI" have a separator between the node
  name and the  resources file that should be a vertical bar "|"
  and not a  colon  ?? ? ??  ?   This can cause errors in usage
  and needs to be corrected.
  
  Resolution: Topic,   Test connection service, is updated.  The
  sample code with lines for resURI are corrected as follows:
  // eg a configuration ID for DataSource declared at the node
  level for Base private static final String resURI =
  
  "cells/cat/nodes/cat|resources.xml#DataSource_1";
  
  // eg a 4.0 DataSource declared at the node level for Base
  //    private static final String resURI =
  "cells/cat/nodes/cat|resources.xml#WAS40DataSource_1";
  
  // eg Apache Derby DataSource declared at the server level for
  Base
  //private static final String resURI =
  "cells/cat/nodes/cat/servers/server1/resources.xml#DataSource_6"
  ;
  // eg node level DataSource for ND
  //private static final String resURI =
  "cells/catNetwork/nodes/cat|resources.xml#DataSource_1";
  
  // eg server level DataSource for ND
  //private static final String resURI =
  "cells/catNetwork/nodes/cat/servers/server1|resources.xml#DataSo
  urce_4 ";
  
  // eg cell level DataSource for ND
  //private static final String resURI =
  "cells/catNetwork|resources.xml#DataSource_1";
  
  This update also applies to version 7.0 and version 8.0 of the
  information center.
  ----------
  ID: RTC 131404
  Problem :  Topic, Customizing the Liberty profile environment,
  describes Liberty profile environment specific variable,
  WLP_OUTPUT_DIR, but the description does not clairfy the types
  of files that are sent to the output directory.  This
  information needs to be added to this description. ??
  
  Resolution: Topic, Customizing the Liberty profile
  environment, is updated.  Specifically the description of the
  Liberty profile enviornment specific varible, WLP_OUTPUT_DIR
  now reads:
  This environment variable can be used to specify an
  alternative location for server generated output such as logs,
  the workarea directory, and generated files. Files in the logs
  directory can include console.log, messages.log, and any
  generated FFDC files. Generated files can include server dumps
  that are created with the server dump or server javadump
  command. This variable must be an absolute path. If this
  environment variable is specified, ${server.output.dir} is set
  to the equivalent of WLP_OUTPUT_DIR/serverName. If this
  environment variable is not specified, ${server.output.dir} is
  the same as ${server.config.dir}.
  When the server command is used, the server process uses the
  output directory as its current working directory.
  -------
  ID: 757163
  Problem :  When using the IBM Installation Manager and the
  default installation directory
  for this product is "C:\Program Files (x86)".  The
  documentation for the Silent Install shows this parameter in
  the Response File as:
  
  <profile id='IBM HTTP Server V8.0'
   installLocation='C:\Program Files\IBM\HTTPServer'>
  
  Are spaces allowed in the specification of the installation
  directory or not.  Topic, Installing IBM HTTP Server using the
  GUI, does not give the user any guidance.  Erros can result.
  
  Resolution: Topic, Installing IBM HTTP Server using the GUI,
  is updated.  The Restrictions section of step 5 now includes
  the following:
  
   Be careful on using spaces in the name of the installation
  directory. Some operating systems allow spaces in the
  specification of the installation directory. Other operating
  systems do not allow spaces.
  
  C:\Porgram Files (x86)    Windows supported
  /opt/IBM/HTTP Server      Unix NOT supported
  /opt/IBM/HTTPServer       Unix supported
  OK - C:\Program Files (x86)
  Not OK - /opt/IBM/HTTP Server
  OK - /opt/IBM/HTTPServer
  
  This update also applies to version 7.0 and version 8.0 of the
  information center.
  ---------
  ID: 757162
  Problem :  Topic, Data source minimum required settings for
  DB2 with the application server on AIX, HP-UX, Linux, Solaris,
  or Windows, does not mention anything explicitly about the
  database alias. The database alias according to the DB2
  specification is an alternate name to a database name.
  In the link, it mentions that the databaseName is the actual
  databasename or even to a cataloged database name for a type
  2. This statement needs to include information about the
  database alias.
  
  Resolution: Topic, Data source minimum required settings for
  DB2 with the application server on AIX, HP-UX, Linux, Solaris,
  or Windows is updated.  In each section:
      DB2 Using IBM ??JCC Driver
      DB2 Using IBM JCC Driver (XA)
      DB2 Universal JDBC Driver provider
      DB2 Universal JDBC Driver provider (XA)
  The follow is documented.
  databaseName - This is an actual database name  (or a database
  alias)  if the driverType is set to 4, or a locally cataloged
  database name if the driverType is set to 2.
  Note: A database alias is an alternate name to an actual
  database name. You can use a database alias for the
  databaseName when driverType is set to 4.
  
  This update also applies to version 7.0 and version 8.0 of the
  information center.
  ---------
  ID: 757143
  Problem :  Topic, Intelligent Management: middleware
  application administrative tasks, has incorrect syntax for the
  listMiddlewareApps command.  This needs to be corrected.
  
  Resolution: Topic, Intelligent Management: middleware
  application administrative tasks, is updated for the
  listMiddlewareApps command with corrected syntax as follows:
  
  Using Jython string:
  
  AdminTask.listMiddlewareApps()
  
  Using Jython list:
  
  AdminTask.listMiddlewareApps()
  ---------
  ID: 757141
  Problem :  When trace is set to
  com.ibm.ws.websvcs.trace.MessageTrace=all, an
  inbound http response to a JAX-WS webservice client is not
  logged in trace.   Topic, Tracing web services, does not
  adequately document how to capture this inbound http response
  to JAX-WS webservice client in the trace.
  
  Resolution: Topic, Tracing web services, is updated by adding
  a  note, which reads:
  Note: For JAX-WS web service, there are two ways (normal level
  and minimal level) to print out both the Outbound HTTP SOAP
  message and the Inbound HTTP SOAP message in the trace file.
  
  Normal level by setting
      com.ibm.ws.websvcs.trace.*=all
  Minimal level by setting
  com.ibm.ws.websvcs.trace.MessageTrace=all:com.ibm.ws.websvcs.tra
  ce.LogFilterInputStream=all.
  
  This update also applies to version 7.0 and version 8.0 of the
  information center.
  ---------
  ID: 757140
  Problem :  Topic, Web container custom properties, is missing
  the documentation of property,
  com.ibm.ws.webcontainer.invokeFilterAfterService.   When the
  web container calls the failing flush() when the OutputStream
  is closed, an error occurs.  This undocumented property
  ensures that the web container does not call the failing
  flush() when the OutputStream is closed.
  
  Resolution: Topic, Web container custom properties, is updated
  with a description of the
  com.ibm.ws.webcontainer.invokeFilterAfterService property as
  follows:
  com.ibm.ws.webcontainer.invokeFilterAfterService
  
  The com.ibm.ws.webcontainer.invokeFilterAfterService custom
  property ensures the web container does not call the failing
  flush() when the OutputStream is closed.
  Name  Default value
  com.ibm.ws.webcontainer.invokeFilterAfterService  true
  
  This update also applies to version 8.0 of the information
  center.
  ----------
  ID: 757026
  Problem :Topic, Enabling security for the IBM WebSphere SNMP
  Capability, If a customer uses the Administrative Console to
  create the keystore and truststore, the default key database
  type will be PKCS12 with the .p12 extension. (There is a drop
  down where JKS can be selected). The documentation needs to
  state clearly that the key database type has to be JKS for
  both the keystore and trustore used by the SNMPAgent
  (configured in the jmxConfig.xml file).  Errors will occur if
  JKS is not selected.
  
  Resolution: Topic, Enabling security for the IBM WebSphere
  SNMP Capability, is updated.
  1)In the introduction to this topic, the following statements
  is made:
  You need not follow these steps if global security is not
  enabled on WebSphere Application Server.
  2)The third paragraph in , Before you begin ??  ?now reads:
  You should enable security on the IBM WebSphere Snmp Agent
  after first enabling global security. Verify that the
  connection is established successfully and you are able to
  obtain the metrics and traps.
  
  3)Step 9 is updated to read as follows:
  Go to Key Database File > open.  The truststore you use should
  be the JKS file. PKCS12 should not be used.  For the default
  truststore use key database type = jks, filename =
  DummyClientTrustFile.jks and location = <was_profile>/etc.
  Note: The key database type must be JKS for both the keystore
  and trustore used by the SNMPAgent (as configured in the
  jmxConfig.xml file).
  Once you click ok, you are prompted for the password. Enter
  the password as WebAS.
  ----------
  ID: RTC 129440
  Problem:  OSGi application startup appears to be slow with
  significant time spent in annotation scanning.  Some
  additional information is needed to help the user specify a
  reasonable scan.
  
  Resolution: Topic,   Converting a web application archive file
  to an OSGi web application bundle, is updated.  The step:
  Specify the bundle classpath by adding a Bundle-Classpath
  header to the bundle manifest file has the following
  added.
  You must set the value of the Bundle-Classpath header to a
  comma-separated list of the names of all the JAR files and
  class subfolders that are contained in the WEB-INF/lib folder
  of the WAR file. Using a value of ./ can be an expensive
  operation. Making the path more explicit, for example by
  specifying WEB-INF/classes or WEB-INF/lib/acme.jar, rather
  than ./, can improve performance.
  ---------
  ID:757304
  Problem :  Topic, Base in-memory session pool size, in
  section, Overflow in non-distributed sessions, describes
  when overflow is disallowed and says that the Session
  Management facility still returns a session with the
  HttpServletRequest getSession(true) method when the memory
  limit is reached, and this is an invalid session that is not
  saved.  The consequences of using this invalid session are not
  described and should be added to this explanation.
  
  Resolution: Topic,  Topic, Base in-memory session pool size,
  in section, Overflow in non-distributed sessions, is updated,
  specifically the third paragraph, which now reads:
  When overflow is disallowed, the Session Management facility
  still returns a session with the HttpServletRequest
  getSession(true) method when the memory limit is reached, and
  this is an invalid session that is not saved.  Any attempt to
  use the session will result in a
  java.lang.IllegalStateException.
  This update also applies to version 7.0 and version 8.0 of the
  information center.
  

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