Fix (APAR): PK74534 Status: Fix Release: 6.1.0.21 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: 553563 Byte size of APAR: 14861 Date: 2008-11-21 Abstract: When copying the security information from V6.0 to V6.1 a FileNotFoundException is thrown. Description/symptom of problem: PK74534 resolves the following problem: ERROR DESCRIPTION:? Migration from WebSphere Process Server V6022 to V62. After migrating the dmgr profile, start the Dmgr. Then migrate Custom profiles using command line. Using command line to migrate the stopped profile Custom Node1(Machine Solaris). This one is successfully without exception. Using Using GUI wizard(wbi_migration.sh) to migrate the stopped profile Custom Node2(Machine Suse). This one is successfully but with an FileNotFoundException of the event server. java.io.FileNotFoundException: IWAE0036E URI Name: /opt/WPS62/profiles/Custom01/config/cells/zhangjbpcCell01/ applications/EventServer.ear/deployments/EventServer; File name: /opt/WPS62/profiles/Custom01/config/cells/zhangjbpcCell01/ applications/EventServer.ear/deployments/EventServer java.io.FileNotFoundException: IWAE0036E URI Name: /opt/WPS62/profiles/Custom01/config/cells/zhangjbpcCell01/ applications/EventServer.ear/deployments/EventServer; File name: /opt/WPS62/profiles/Custom01/config/cells/zhangjbpcCell01/ applications/EventServer.ear/deployments/EventServer LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: Users that are migrating Custom Profiles of WebSphere Process Server or WebSphere Application Server with Common Event Infrastructure (CEI) installed from V6.0 to V6.1 PROBLEM DESCRIPTION: When copying the security information from V6.0 to V6.1 a FileNotFoundException is thrown. RECOMMENDATION: None Exceptions are thrown during custom node migration when trying to copy the security information to the new profile. The path to the EventService is incorrectly detected when trying to modify the security in the new profile. PROBLEM CONCLUSION:? The migration code has been modified so that the path to the new CEI application is correct when copying the security from the old application. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.23. 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: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.1.0.13 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 For detailed instructions to Extract the Update Installer see the following Technote: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to 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) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) 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 (PKxxxxx.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: