PK96996; 7.0.0.7: systemapps.xml entries are not migrated

Download Description

PK96996 resolves the following problem:

ERROR DESCRIPTION:
Customers who migrate a node, which is a member of a cluster, from WebSphere Application Server version 6.1 to version 7.0 will encounter the following error(s) when starting that node:

WSVR0215W: Starting application, ManagementEJB, failed. The application is not installed. WSVR0100W: An error occurred initializing, ManagementEJB com.ibm.ws.exception.ConfigurationWarning: No cluster target found for application, ManagementEJB WSVR0215W: Starting application, filetransferSecured, failed. The application is not installed. WSVR0100W: An error occurred initializing, filetransferSecured
com.ibm.ws.exception.ConfigurationWarning: No cluster target found for application, filetransferSecured

This problem occurs because the new profile installs these system apps by default, then when the old profile is migrated over the systemapps.xml file is not being cleaned up.

LOCAL FIX:
These messages can be removed by editing the $profile_home/systemapp.xml and by removing the entries for the applications that should not be started.
-
Search Keywords: migrate preupgrade postupgrade cluster addnode WCS WPS

PROBLEM SUMMARY

USERS AFFECTED:
All users of IBM WebSphere Application Server who are using the migration tools.

PROBLEM DESCRIPTION:
When migrating from WebSphere Application Server version 6.1 to Version 7.0, the systemapps.xml is not being handled properly for the different situations.

RECOMMENDATION:
None

When migrating from WebSphere Application Server version 6.1 to Version 7.0, the systemapps.xml entries are not being migrated. If there weren't any entries in the previous version and the profile is migrated into a default profile the profile will now start a systemapp in the new version. If server1 is part of a cluster in the old, it will be in the new as well and the systemapps.xml entry will not be valid, causing an application start error:


WSVR0215W: Starting application, ManagementEJB, failed. The application is not installed.
WSVR0100W: An error occurred initializing, ManagementEJB com.ibm.ws.exception.ConfigurationWarning: No cluster target found for application, ManagementEJB
WSVR0215W: Starting application, filetransferSecured, failed. The application is not installed.
WSVR0100W: An error occurred initializing, filetransferSecured com.ibm.ws.exception.ConfigurationWarning: No cluster target found for application, filetransferSecured

PROBLEM CONCLUSION:
Migration now handles the various scenarios of migrating of systemapps.xml and it's entries, with one exception. Migration will mimic the addNode behavior for system apps. During addNode, specific system applications will remain installed and are therefore automatically included in the systemapps.xml file. During migration of a federated node, even if no system apps existed in the old systemapps.xml, migration will retain the new systemapps settings of those system apps which are supposed to be configured in the new version.

The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.9. Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980