PQ56906: CLASSES/WEB RESOURCES NOT MIGRATED FROM 3.X TO 4.0 BY WASPOSTUPGRADE CLASSPATH/DOCUMENT ROOT DOESN'T USE FULLY QUALIFIED PATH. | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as documentation error. Error description Customer is using install/WASPostUpgrade process to migrate from WebSphere 3.x to 4.0. After migration is completed they cannot find their servlet classes, .jsps and web resources. They have configured a working directory on the Application Server. The document root and the classpath uses a path relative to the Working Directory. When using install/WASPostUpgrade to migrate from 3.x to 4.0.x, files and webresources are not moved to the WAS 4.0 environment.Local fix The user may workaround the issue by either of the following methods. 1) You may edit WebSphere 3.x document root and classpath to contain the fully qualified classpath then perform migration process again. 2) After running the migration process, you may modify the WAS 3.x xml to use the fully qualified document root and classpath. Then you may continue with the migration upgrade by either executing install or WASPostUpgrade depending on your situation. Use the install if WAS 4.0 requires installing or WASPostUpgade if WAS 4.0 is already installed.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * who migrate when their WebSphere 3.x * * configuration contains a working directory * * on an Application Server and the document * * root and classpath use paths that are * * relative to the working directory. * **************************************************************** * PROBLEM DESCRIPTION: Files that are pointed to by a Web * * App's document root and classpath are * * not being copied into war files. * **************************************************************** * RECOMMENDATION: * **************************************************************** When migrating from WebSphere 3.x to 4.0, the document root and classpath attributes of Web Apps in 3.x are used as pointers to the files that are copied into the war file. Migration assumes that the these paths are either fully qualified paths or symbolic links. Therefore, when the paths are relative to the Working Directory on the Application Server the files are not being copied over into the war file.Problem conclusion When the document root and classpath entries are relative to the working directory path defined on an Application Server, the entries must be modified to contain the fully qualified path or symbolic link. The entries can be changed before WASPreUpgrade has been run or by modifying the websphere_3x_backup.xml file after WASPreUpgrade has been completed but before running WASPostUpgrade.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ56906
IBM Group: Software Group
Modified date: Feb 14, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.