Fix (APAR): PK86307 Status: Fix Release: 6.1.0.21,6.1.0.19,6.1.0.17,6.1.0.15,6.1.0.13,6.0.2.31,6.0.2.29,6.0.2.27,6.0.2.25,5.1.1.19 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: PK83335 AND PK72036 CMVC Defect: PK86307 Byte size of APAR: 439650 Date: 2009-06-01 Abstract: Error may occur when uninstalling PK83335 interim fixes for WebSphere Application Server v6.1, depending on uninstall option. Description/symptom of problem: PK86307 resolves the following problem: ERROR DESCRIPTION: The interim fix IFPK83335 for WebSphere Application Server v6.1 was created with a mismatch in the file name and its internal name reference. As a result, an attempt to uninstall the interim fix in silent mode with "-W backup.package" option may fail. In GUI mode, the displayed package name is incorrect. LOCAL FIX: Provide customer instructions on how to uninstall the iFix on a per-PMR basis. PROBLEM SUMMARY USERS AFFECTED: Users of IBM WebSphere Application Server interim fix install and users of IBM WebSphere Application Server admin console. PROBLEM DESCRIPTION: Error may occur when uninstalling PK83335 interim fixes for WebSphere Application Server v6.1, depending on uninstall option. RECOMMENDATION: If the uninstall process does not remove PK83335 interim fix as expected, the interim fix may be uninstalled in silent mode as follows: To uninstall 6.1.0.21-WS-WAS-IFPK83335.pak, uninstall in silent mode with "-W backup.package="6.1.21.0-WS-WAS-IFPK83335.pa k" in the response file. To uninstall 6.1.0.13-WS-WAS-IFPK83335.pak, uninstall in silent mode with "-W backup.package="6.1.13.0-WS-WAS-IFPK83335.pa k" in the response file. Uninstalling in GUI mode will display the incorrect package name for PK83335, but the uninstall of PK83335 will proceed. The interim fix files 6.1.0.21-WS-WAS-IFPK83335.pak and 6.1.0.13-WS-WAS-IFPK83335.pak contain incorrect internal names. 6.1.0.21-WS-WAS-IFPK83335.pak references 6.1.21.0-WS-WAS-IFPK83335 internally while 6.1.0.13-WS-WAS-IFPK83335.pak references 6.1.13.0-WS-WAS-IFPK83335.pak internally. PROBLEM CONCLUSION: PK86307 SUPERSEDES PK83335 and PK72036. The uninstall problem reported under PK86307 does not occur with the PK83335 interim fixes previously available for v5.1.1.19 or v6.0.2 releases. All PK83335 interim fixes have been replaced by PK86307 interim fixes. APARS PK86307 and PK83335 only relate to install or uninstall problems of interim fixes. Both APARs are intended to resolve an admin console vulnerability reported in PK72036. There are no issues with the changes for PK72036 that are already included in fix paks 6.0.2.33 and 6.1.0.23. To summarize, PK86307 addresses the following: 1) the original problem reported with PK72036 where the WebSphere Application Server admin console is prone to an arbitrary file retrieval vulnerability 2) possible interim fix installation errors that may have been reported when applying PK72036 on v6.1.0.21. An attempt to apply PK72036 on v6.1.0.21 would result in the following error message: "THIS FIX REQUIRES PK7095B" 3) failure to install PK83335 on ISC products where the install fails with "No component action is applicable to the target installation". 4) incorrect internal package naming that may cause errors when uninstalling the interim fix in GUI or silent mode with "-W backup.package" option. In most cases, PK86307 has a PK81332 prereq. If installing PK86307 interim fix for v6.1.0.21, PK81332 is not required. PK81332 has been included in fix paks 6.0.2.33 and 6.1.0.21 under PK70955. 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 6 X Application Server (Express or BASE) X 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 X 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 Note that there are two different methods for delivering iFixes, depending on the contents. The fix may be delivered either as a single file with a .pak extension (such as 6.1.0.11-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.11-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension. 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) Launch 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. 8) Please note that in the future, if a Feature Pack is installed or uninstalled, a different set of iFixes will be needed. Use the Update Installer again at that time, with the maintenance directory location where these maintenance packages are stored, to determine the required interim fixes for the new WebSphere and Feature Pack(s) combination. 9) The maintenance packages could have one of a set of names, and these names will help determine which maintenance package you need to install. The APAR name (PKxxxxx) should appear as part of the filename. Between the APAR number and the .pak extension there will be 0 to 2 characters added. The table below indicates the usage of each of the maintenance packages with respect to which Feature Packs, if any, are installed. |.pak File Names |No Feature Packs|EJB3 Only|WebServices Only| Both | |6.1.0.x-WS-WAS-IFPK12345 | X | X | X | X | |6.1.0.x-WS-WAS-IFPK12345C | X | | | | |6.1.0.x-WS-WAS-IFPK12345CE | | X | X | X | |6.1.0.x-WS-WAS-IFPK12345W | X | X | | | |6.1.0.x-WS-WAS-IFPK12345WE | | | X | X | |6.1.0.x-WS-WAS-IFPK12345E | X | | X | | |6.1.0.x-WS-WAS-IFPK12345EE | | X | | X | 10) 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) Select file name of the maintenance package to uninstall (for example, 6.1.0.11-WS-WAS-IFPK12345.pak). 6) Verify the Uninstallation Summary and continue with the uninstall. 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: