PQ60746: CUSTOMER ON WAS 3.5.5 UPGRADING TO WAS 4.01, MIGRATION PREREQ DOES NOT CHECK CORRECTLY FOR VERSIONS AT 3.5.5 OR HIGHER. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer is using WAS 3.5.5 on Solaris and is upgrading to WAS 4.01 and has had a problem with the migration prereq checker Apparently the checker will only look for installations up to the 3.5.4 level, if the customer is at PTF5 or higher then it does not detect the customer's configuration and does not work. The work around offered would be to back level down to 3.5.4 and then upgrade.Local fix Customer can uninstall their current fixpak and reinstall fixpak 4, then proceed with the migration process.Problem summary **************************************************************** * USERS AFFECTED: All WebSphere 4.0 Application Server, * * Advanced and Single Server edition, users * * migrating from 3.5.5 or higher (3.5 level) * * to 4.0.1. * **************************************************************** * PROBLEM DESCRIPTION: When installing WebSphere 4.0.1 AE/AEs * * the migration panel on the base install * * gui does not appear when WebSphere * * 3.5.5 or higher (3.5 level) is * * currently installed. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a user has WebSphere 3.5.5, 3.5.6, or higher 3.5 level presently installed on a machine and then try to install WebSphere 4.0.1, the migration panel of the base WebSphere gui install fails to appear and question the user whether they would like to migrate their 3.5.x version to 4.0.1. This will force the user to install WAS 4.0.1 and then manually migrate from 3.5 to 4.0.1.Problem conclusion This problem is a result of the WebSphere 4.0.1 prereq checking only looking for WebSphere 3.5 versions up to 3.5.4. The prereq.properties file was modified to add the presently released levels of 3.5 (3.5.5 and 3.5.6) along with higher levels that are not presently released and may never be released. By adding these levels will allow the prereq checker to accept 3.5.5 or higher as valid levels of the 3.5 release and will bring up the migration panel during a 4.0.1 gui install.Temporary fix The only way to fix this issue is to copy the contents of the WebSphere Application Server 4.0.1 CD on to the user's hard drive and then install the eFix. The eFix will replace the prereq.properties file. The user can not simply point to the new prereq.properties file as they normally would for disabling the prereq checker (./install.sh -prereqfile /tmp/prereq.properties) because the migration code does not check the prereq file that is specified at the command line, it always looks at the one that is in the same directory as install.sh. The only other way to get around this issue without installing this efix would be to go back to 3.5.4 and then run the install for 4.0.1 and it will recognize the 3.5.4 and ask the user if they wish to migrate or not.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ60746
IBM Group: Software Group
Modified date: May 31, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.