PQ56894: THE MIGRATION TOOLS, WASPOSTUPGRADE OR INSTALL, DID NOT ADD ALL THE .WARS WITH DUPULICATE WEB APP WEB PATHS.

APAR status
Closed as program error.

Error description
Some of the WebSphere 3.5 Web Application have the same Web Path
.  The root uri's are different only in that thay have different
 virtual host.  When migrating with either the Install process o
r WASPostUpgrade.sh only one WAS 3.5 Web App(i.e. only one .war)
 with duplicate Web Paths was added to the .ear.
The WAS 3.5 .xml shows the duplicate Web Paths for the different
Web Applications.
We were able to manually add the .war files to the .ear using
AAT.  The .war files were created by WASPostUpgrade.sh in the
backup directory.
Local fix
The .war files are created by the install/WASPostUpgrade in the
backup directory.  They can be manually added to the .ear files.
When adding the .war files it was allowed to use the same duplic
ate context root paths.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 who migrate when their WebSphere 3.x         *
*                 configuration contains Web Apps with root    *
*                 uris that have the same context root, but    *
*                 different virtual hosts.                     *
****************************************************************
* PROBLEM DESCRIPTION: War files created by migration are not  *
*                      being added to the ear file if there    *
*                      are already war files in ear files      *
*                      with the same context root.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When migrating from WebSphere 3.x to 4.0, migration
is creating a list containing the context root of
war files that have been added to an ear file and
checking that list before adding a new war file to
an ear file.  If the war file's context root matches
a context root on the list it will not be added to an
ear file.  The war file will not be added even if the
virtual host is different then the virtual host of
the war file with the same context root.  The war file's
virtual host and context root should be checked instead
of just the context root.
Problem conclusion
Code has been added that adds the virtual host and
context root or root uri of war files that have been
added to an ear file to the list, instead of just the
context root.  This change will allow war files with
the same context root but different virtual hosts to
be added to ear files.
Temporary fix Comments
APAR information
APAR number PQ56894
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-01-21
Closed date 2002-02-08
Last modified date 2002-02-08

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
MIGRATE          

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ56894
IBM Group: Software Group
Modified date: Feb 8, 2002