PQ73494: DTD files not created during install when installing only a plug-in.

 A fix is available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
Scenario: Customer runs custom installation of WebSphre 5.0 and
opts only to install a plug-in. (i.e., iPlanet plug-in).  This
is a typical scenario when a customer runs the webserver on a
remote server.

The install does not create necessary files in the
<WAS_HOME>/properties/version/dtd directory.  The plug-in will
operate normally, and everything may seem to function correctly
without these files.  However, the updateInstaller (the utility
which applies interim fixes and Fix Packs) will fail in this
situation.  It will claim that the product is not installed,
even when the correct installation directory is specified.
See PMR 25241,379,000
Local fix
The DTD files need to be present in order for the
updateInstaller to function properly.  It appears to be a defect
that these files are not created during a custom (plug-in only)
installation.

Customers may work around this situation by copying the files
from the corresponding directory on full AppServer installation
to the <WAS_HOME>/properties/version/dtd directory on the
webserver.

A different APAR, 
PQ73493, addresses the issue that the
updateInstaller should handle this situation more gracefully.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users           *
*                 installing the WebSphere UpdateInstaller on  *
*                 a remote web server machine where they only  *
*                 have the web server plugin and web server,   *
*                 e.g. IBM HTTP Server, installed.             *
****************************************************************
* PROBLEM DESCRIPTION: The WebSphere UpdateInstaller will      *
*                      fail to install on a machine where      *
*                      the WAS_HOME/properties/version/dtd     *
*                      directory is not present.  A scenario   *
*                      in which this would occur is on a       *
*                      remote web server machine where the     *
*                      WebSphere web server plugin and web     *
*                      server are only installed.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When installing a customer install, in which the web server
plugin was only selected to be installed, the
WAS_HOME/properties/version/dtd directory was not installed.
This directory and it contents should have been installed.

Workaround:
To have the WebSphere UpdateInstaller run successfully, copy
the WAS_HOME/properties/version/dtd directory from the
WebSphere machine where the base WebSphere Application Server
v5.0 is installed to the web server machine.
Problem conclusion
The WebSphere full install, will now install the missing dtd
directory and contents when a custom plugin-only install
is selected.
Temporary fix Comments
APAR information
APAR number PQ73494
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-04-23
Closed date 2003-06-09
Last modified date 2003-09-11

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
Install          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ73494
IBM Group: Software Group
Modified date: Sep 11, 2003