{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}} {\*\generator Msftedit 5.41.21.2500;}\viewkind4\uc1\pard\f0\fs20 Fix (APAR): PK55641\par \par Status: Fix\par \par Release: 6.1.0.9,6.1.0.13,6.1.0.11\par \par Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows\par \par Supersedes Fixes: PK52451 PK49061\par \par CMVC Defect: PK55641\par \par Byte size of APAR: 35377\par \par Date: 2007-11-05\par \par Abstract: The migration code was not designed to handle multiple nodes on a standalone configuration.\par \par Description/symptom of problem: \par PK55641 resolves the following problem:\par \par ERROR DESCRIPTION: \par Migrating from a V6.0 profile to a V6.1 profile fails under \par circumstances where the V6.0 profile contains multiple nodes. \par Typically, a V6.0 profile will contain multiple nodes when that \par node has one or more webserver definitions. \par \par The migrated V6.1 profile will only contain data from one of the\par nodes present in the V6.0 profile. The new profile may only \par contain webserver definition data, or may only contain the \par application server data with no webserver data. \par \par LOCAL FIX: \par In order to work-around the issue, it is necessary to either \par re-define the missing data in the V6.1 profile, or remove the \par webserver definition from the V6.0 profile prior to migration, \par then re-define it in the V6.1 node. \par \par PROBLEM SUMMARY\par \par USERS AFFECTED:\par WebSphere Application Server version 6.1\par users migrating configurations which\par contain unmanaged nodes on a standalone\par configuration.\par \par PROBLEM DESCRIPTION:\par The migration code was not designed to\par handle multiple nodes on a standalone\par configuration.\par \par \par RECOMMENDATION:\par None\par \par \par The migration failed to migrate information from the second\par node. The sort order of the filesystem (alphabetic on windows\par and creation date on other platforms) affected which node would\par be migrated. Only the first node located on the filesystem\par would be migrated forward, which created a configuration that\par would not work correctly.\par \par PROBLEM CONCLUSION: \par The webserver script has been updated in v6.1 to create the \par webservers on the same node as the default server. The \par migration code in this APAR will correctly merge the webserver \par into the default node. This will convert the non-recommended \par v6.0.2 configuration to the recommended configuration for v6.1. \par \par Users might need to manually regenerate the plugin after \par migration, as the generate plugin code will not resolve \par the new node name (if the default node in the new world is \par different from the webserver node in the old world). \par \par The fix for this APAR is currently targeted for inclusion in \par fixpack 6.1.0.15. Please refer to the Recommended Updates page \par for delivery information: \par http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 \par \par \par Directions to apply fix: \par NOTE: Choose the:\par 1) Release the fix applies to\par 2) The Editions that apply\par 3) Delete the Editions & Methods that do not apply and this Note\par \par Fix applies to Editions:\par Release 6.0\par __ Application Server (Express or BASE)\par __ Network Deployment (ND)\par __ WebSphere Business Integration Server Foundation (WBISF)\par __ Edge Components\par __ Developer\par __ Extended Deployment (XD)\par \par Install Fix to:\par Method:\par __ Application Server Nodes\par __ Deployment Manager Nodes\par __ Both\par \par NOTE:\par The user must:\par * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.\par * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.\par * 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.\par \par The Update Installer can be downloaded from the following link:\par http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991\par \par For detailed instructions to Extract the Update Installer see the following Technote:\par http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400\par \par 1) Copy PKxxxxx.pak file directly to the maintenance directory\par \par 2) Shutdown WebSphere\par Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.\par \par 3) Launch Update Installer\par \par 4) Enter the installation location of the WebSphere product you want to update.\par \par 5) Select the "Install maintenance package" operation.\par \par 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory).\par \par 7) Install the maintenance package.\par \par 8) Restart WebSphere\par \par \par \par \par \par Directions to remove fix: \par NOTE:\par * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.\par * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED\par * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED\par * YOU MAY REAPPLY ANY REMOVED FIX\par \par 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.\par \par 1) Shutdown WebSphere\par Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.\par \par 2) Start Update Installer\par \par 3) Enter the installation location of the WebSphere product you want to remove the fix.\par \par 4) Select "Uninstall maintenance package" operation.\par \par 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak).\par \par 6) UnInstall maintenance package.\par \par 7) Restart WebSphere\par \par \par \par \par \par Directions to re-apply fix: \par 1) Shutdown WebSphere.\par \par 2) Follow the Fix instructions to apply the fix.\par \par 3) Restart WebSphere.\par \par \par \par \par \par \par \par Additional Information: \par }