APAR status
Closed as program error.
Error description
Customer tried migrating a profile from WAS 8.5.5.x base to WAS 9.0.5.x , and used "Create the target profile" instead of using an existing profile from the target installation, I noticed that new server 1 is created along with the server from source and when I tried to access the console but got an error,(used migration wizard) SRVE0255E: A WebGroup/Virtual Host to handle /ibm/console has not been defined.SRVE0255E: A WebGroup/Virtual Host to handle localhost:9047 has not been defined.I can see isclite.ear (adminconsole) mapped to server1 that has following ports based on serverindex.xml and virtualhost admin_host ports not matching. Here are my findings regarding the WAS console issue: isclite.ear (adminconsole) mapped to server1 that has following ports based on serverindex.xml <specialEndpoints xmi:id="NamedEndPoint_1183122129646" endPointName="WC_adminhost"> <endPoint xmi:id="EndPoint_1183122129646" host="*" port="9068"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_1183122129649" endPointName="WC_adminhost_secure"> <endPoint xmi:id="EndPoint_1183122129649" host="*" port="9051"/> but virtualhost admin_host ports not matching... <aliases xmi:id="HostAlias_1638795941792" hostname="*" port="9064"/> <aliases xmi:id="HostAlias_1638795941793" hostname="*" port="9047"/>
Local fix
This doesn?t necessarily appear related to the use of the migration wizard, but rather it appears that WASPostUpgrade doesn?t handle migrating a standalone application server into a profile that contains a server with a different server name than was found in the old environment. For now, they should use the instructions provided by how to use the profile management wizard to create a profile with a server that has the same name as the server in the old environment and then migrate into that profile
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * version to version migration tools * **************************************************************** * PROBLEM DESCRIPTION: Migrating a standalone server profile * * with server not named server1 to * * version * * 9 causes issues * **************************************************************** * RECOMMENDATION: * **************************************************************** When a standalone application server profile is migrated using WASPostUpgrade, the server name of the source and target profile must match in order for the users configuration and applications to be migrated into the existing server that contains the admin console, system apps, and default configuration. If the names do not match, the result is a profile with both server1, containing the admin console, and the server from the source profile, containing only the user's apps.
Problem conclusion
Migration was updated to issue a warning in both WASPreUpgrade a WASPostUpgrade if the server has a non-default name. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.14. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Delete the destination profile and create a new one, specifying server name matching the server of the source profile.
Comments
APAR Information
APAR number
PH42947
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-12-20
Closed date
2022-10-03
Last modified date
2022-10-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 October 2022