Technote

(troubleshooting)
Errors when updating a WebSphere Commerce Version 6.0 application
Problem(Abstract)
Updating a WebSphere Commerce application fails if the update includes special characters.
Cause Updating a WebSphere Commerce application using the following tools may fail if the application (EAR) contains a file with a name containing special characters (for example, Arabic):


When adding a file with a file name that contains special characters, unpredictable results can occur. The tool may indicate that the update was successful, however the update will not appear properly in the store front.

In the case of WebSphere Commerce attachments you may be able to see the attachment from the Commerce Tooling, even though you cannot see the attachment from the storefront.

Detailed technical description.

For attachments, the attachment is first stored in the database. The WebSphere Commerce tooling retrieves the attachment from the database. The attachment path and content is stored correctly in the WebSphere Commerce database. Since the tooling uses the this database, the file can be shown correct.

After a period of time, the attachment is added to the WebSphere Commerce Enterprise Application (EAR) using the WebSphere Application Server Application Update Feature.

The WAS Application Update Feature is also used for other purposes, such as logo update and store publishing.

The WAS Application Update Feature adds this file to the collapsed copy of the EAR file inside the WAS configuration repository. It then sends the updated EAR file to all nodes that are running the application along with a manifest of the files that have changed in the EAR. The Node then expands the updated file assets from the collapsed EAR into the application binaries directory (the installedApps directory). Due to a bug in the JDK, the extraction of the changed file assets fails. Thus the file is not available from the store front because the storefront uses the files from the installedApps directory. Resolving the problem There is no fix available. Refer to the following URL for more information on this problem:


To avoid this problem do not use these special characters in files that will get added to the WebSphere Commerce Enterprise Application..
Cross Reference information
Segment Product Component Platform Version Edition
Commerce WebSphere Commerce Enterprise Configuration AIX, i5/OS, Linux, Linux iSeries, Linux pSeries, Linux xSeries, Linux zSeries, Solaris, Windows 6.0 All Editions
Commerce WebSphere Commerce Professional Edition Configuration AIX, i5/OS, Linux, Linux iSeries, Linux pSeries, Linux xSeries, Linux zSeries, OS/390, Solaris, Windows 6.0 Professional Edition
Commerce WebSphere Commerce - Express Configuration i5/OS, Linux, Windows 6.0 Express
   

Document Information

Current web document: http://www.ibm.com/support/docview.wss?uid=swg21236357