Fix (APAR): PK72347 Status: Fix Release: 6.1.0.15,6.0.2.27 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: PK72347 Byte size of APAR: 19497 Date: 2008-09-24 Abstract: Partial application update fails when the partial application zip file contains files named in Chinese. Description/symptom of problem: PK72347 resolves the following problem: ERROR DESCRIPTION:? If user wants to add an image file into the deployed EAR. WebSphere Commerce provides a web-based GUI to do this. The file is temporarily stored on the file system in a zip file (Ex: tempPartialEAR.zip), then under the covers the file is installed to the EAR via API calls to com.ibm.websphere.management.application.AppManagement. The user uploads a file with Chinese name (??????.jpg) to Commerce Server via a web tool in WebSphere Commerce. The file can be successfully uploaded and stored in on the filesystem in the zip file. The error occurs when use AppManagement to install the file to the EAR. Files with English names are always able to be installed to the EAR (even after Chinese file fails) while files with Chinese names are never (not even first time) able to be installed to the EAR. LOCAL FIX:? N/A PROBLEM SUMMARY:? USERS AFFECTED: Users of IBM WebSphere Application Server versions 6.0.2, 6.1 and 7.0 who use the partial application update function PROBLEM DESCRIPTION: Partial application update fails when the partial application zip file contains files named in Chinese. RECOMMENDATION: None Update of an installed Java 2 Platform Enterprise Edition (J2EE) application with a partial application zip file, does not work as expected when the zip file contains files named in Chinese. There are no explicit failure messages. While the ear file in the configuration repository is updated with the files in the zip, the expanded ear in the binaries location will not contain the files named in Chinese. PROBLEM CONCLUSION:? The fix resolves this issue by encoding the file names correctly during deployment. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.33, 6.1.0.23 and 7.0.0.3 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.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) Release 6.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) Install Fix to: Method: _X_ Base Application Server Nodes _X_ Deployment Manager Nodes 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-IFPK12345C 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: