Fix (APAR): PK96996 Status: Fix Release: 7.0.0.7 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: 590025 Byte size of APAR: 57411 Date: 2009-10-20 Abstract: When migrating Websphere Application Server version 6.1 to Version 7.0, the systemapps.xml entries are not migrated. Description/symptom of problem: PK96996 resolves the following problem: ERROR DESCRIPTION: The client is going through the migration steps to migrate their configuration from Websphere Application Server version 6.1 to Version 7.0. After they migrate a node that contains a cluster member the member shows these error when it is started: 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 is because the systemapps.xml containied these entries. The systemapps.xml on the migrated node was not updated from the Version 6 mode. LOCAL FIX: You can get rid of this messages by editting Profile_Home/systemapp.xml and 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 Websphere Application Server version 6.1 to Version 7.0, the systemapps.xml entries are not migrated. RECOMMENDATION: None When migrating Websphere Application Server version 6.1 to Version 7.0, the systemapps.xml entries are not 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 migration of systemapps.xml and it's entries, with one exception. Migration will proceed as federation of a node does during federated node migration. During federation, there are specific applications that remain installed as a system app and are therefore in the systemapps.xml file. If nothing existed in the old systemapps.xml, migration will still keep the systemapp that is supposed to remain after federation 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 Directions to apply fix: Fix applies to Editions: Release 7.0.0.7 __ Application Server (Express or BASE) X Network Deployment (ND) __ Edge Components __ Developer Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into the maintenance directory. 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PK96996.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: