Fix (APAR): PK40912 Status: Fix Release: 6.1.0.7 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 10533 Date: 2007-04-27 Abstract: The Common Event Infrastructure (CEI) was incorrectly migrating the ODR configuration into the new version 6.1 installation and consequently causing migration to fail. Description/symptom of problem: PK40912 resolves the following problem: ERROR DESCRIPTION: While migrating a base application server from version 6 to version 6.1, the common event infrastructure migration migrates the On demand router, which is a WebSphere Extended Deployment artifact. Since this is not a base artifact, it is incorrectly or incompletely migrated which leaves the deployment in a state wherein the On Demand Router cannot be deleted, recreated or migrated. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: Users performing a WebSphere Extended Deployment migration operation from an existing (version 6.02) installation to a new (version 6.1) installation PROBLEM DESCRIPTION: The Common Event Infrastructure (CEI) was incorrectly migrating the ODR configuration into the new version 6.1 installation and consequently causing migration to fail. RECOMMENDATION: None When migrating a Network Deployment version 6.0.2 setup to version 6.1, the CEI component that is part of the version 6.1 setup will attempt to migrate version 6.0.2 Extended Deployment On-Demand Routers (ODRs) (or at least copy over the version 6.0.2 ODR definitions as is), which it is not supposed to do. This breaks the subsequent Extended Deployment version 6.0.2 -> 6.1 migration. With regard to migration, existing base WebSphere Application Server migration must not attempt to migrate configurations created by a stack product (in this case, Extended Deployment). PROBLEM CONCLUSION: The fix addresses the problem so that the CEI component leaves the ODR definitions alone, and the Extended Deployment version 6.0.2 -> 6.1 migration can migrate them as part of its regular process. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.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: 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.0.2.2 or newer of the Update Installer. 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-1.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: