APAR status
Closed as program error.
Error description
After migration to WAS V9 using the -clone option the app server does not start. From the admin console servers > servername > Installed applications does not show any applications. Looking at the <profile_home>/config/cells/cellname/applicatons all of the applications from the DMGR are in this folder, instead of just the ones deployed to this node. - A combination of issues caused this problem to occur: 1. The Communication Enabled Application (CEA) is no longer shipped as part of WebSphere v9. They have a system app called commsvc, which is installed on all nodes in prior releases. 2. The CEA config migration was removed from the migration code in V9, however, the commsvc application is still being brought forward in the serverindex.xml file. 3. This non-existent application causes syncNode to throw an exception which then bypasses filtering the list of applications that are synced to the node from the dmgr. Thus the federated node gets all applications.
Local fix
As for the workaround, until we get an iFix, here is what I suggest. 1. Migrate the Dmgr using the -includeApps script parameter. 2. Migrate all federated nodes. 3. In the Dmgr's config tree, you will need to remove the following from each node's serverindex.xml file. <deployedApplications>commsvc.ear/d eployments/commsvc</deployedApplications> 4. start the Dmgr, and nodeagens and sync the config. 5. Run WASMigrationAppInstaller from the new Dmgr's bin directory pointing it to the Dmgr's migration backup dir. 6. Sync all the node's again. Keywords: waspostmigration waspremigration syncNode
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * Migration to v9 * **************************************************************** * PROBLEM DESCRIPTION: All applications are migrated to a * * federated node when migrating to * * WebSphere Application Server v9 * **************************************************************** * RECOMMENDATION: * **************************************************************** The commsvc.ear (CEA) system application was removed in WebSphere Application Server v9, but the migration tooling still migrates the application to v9. The presence of this application, which doesn't actually exist in v9, causes syncNode to sync all of the applications in the cell to the federated node, even those that are not deployed to that node. Although the applications exist in the federated node's folder structure, the applications are not visible in the admin console.
Problem conclusion
The migration tooling will no longer migrate the CEA Application to WebSphere Application Server version 9.0. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.5. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Comments
APAR Information
APAR number
PH26093
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-06-04
Closed date
2020-06-30
Last modified date
2020-06-30
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021