PQ53951: NEW COMMAND LINE PARM FOR THE WASPOSTUPGRADE MIGRATE TOOL FOR WS4.0, CALLED 'WEBMODULEADDITIONALCLASSPATH'

APAR status
Closed as program error.

Error description
Abstract:
Classpath not migrated correctly from 3.5 to 4.0
.
Operating System:  SUN
Product Group:  WAS AE SUN 350
.
Environment:
WAS 3.5.4
Solaris 2.7
Sybase 12
iPlanet 4.1sp8
.
Problem:
When using the standard WASPostUpgrade script to migrate
the applications from 3.5.x to 4.0, all the classpath
entries from a 3.5 webapp are being copied into the WAR
file (classes/ and lib/ subdirectories).
.
This is not always applicable in our environment since
most applications depend on external libraries that are
centrally available, so we want those *not* to be copied
and end up in the "additionalClasspath" provided by IBM
J2EE extension mechanism.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 who migrate web applications where the web   *
*                 application's classpath attribute path       *
*                 entries point to any files that are          *
*                 centrally located and used by multiple web   *
*                 applications.                                *
****************************************************************
* PROBLEM DESCRIPTION: Centrally located files used by         *
*                      multiple web applications were being    *
*                      copied into the WAR file When migrating *
*                      from WebSphere 3.x to 4.0.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When migrating from WebSphere 3.x to 4.0, the classpath
attribute of the web application in 3.x is used as a pointer to
the servlet code for the web application.  All files found
under each path entry are normally copied into the WAR file's
class or lib subdirectory.  This would include any files that
multiple web applications use that are centrally located if
they are included as a classpath path entry of the web
application.  The centrally located files should not have been
copied into the WAR file.
Problem conclusion
A new command line parameter has been added to WASPostUpgrade
called -webModuleAdditionalClasspath. This parameter will allow
users to specify the path and file names of specific files that
they do not want copied into the WAR files.  Instead, the
specific file(s) specified by the -webModuleAdditionalClasspath
will be added to the Web Module's extension (ibm-web-ext.xmi)
additionalClassPath attribute based on each web app's classpath
entries.  In addition, the user may specify directories
that contain files that they do not want copied into the WAR
file.  All files in the specified directory and any
subdirectories will not be copied into the WAR file.  Instead,
any jar file that is found in the specified directory or any of
it's subdirectories will be added to the Web Module's
additionalClassPath attribute based on each web app's classpath
entries.
Temporary fix
Test fix sent to Jeff Stratford 10/29/2001
Comments
APAR information
APAR number PQ53951
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-10-24
Closed date 2001-11-30
Last modified date 2001-11-30

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 SO
Fixed component ID 5630A2202

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 #: PQ53951
IBM Group: Software Group
Modified date: Nov 30, 2001