Assets tool: Frequently asked questions (FAQ)
Find answers to some frequently asked questions about using certain features of the Assets tool and completing tasks.
Browse the Troubleshooting tab for answers to common problems that you might encounter when you are working with the Assets tool.
 |
 |
||||
 |
|||||
What types of files can I upload with the Assets tool?
You can upload files in any of the following
formats:
- Graphics (.gif, .jpe, .jpeg, .jpg, .png, .ico)
- Document (.doc, .pdf, .ps, .text, .txt)
- Presentation (.ppt)
- Spreadsheet (.xls)
- Archive (.zip, .gtar, .gz, .tar, .jar)
- Media (.avi, .mov, .mpeg, .mpg, .qt, .ra, .swf, .wav)
Important: You cannot include JavaScript in any managed files
that are uploaded for the store, for example, CSS files.
Should I use URLs or managed files for my assets?
It is recommended that you use URLs instead of managed files, because managed files are stored in a file package, that is called an enterprise archive, which can be updated frequently. This archive can grow large, which can cause performance issues for your servers if the archive is frequently updated.If you decide to upload managed files as assets with the Assets tool, here are some tips
to minimize or avoid performance issues:
- If you use workspaces and you want the contents of an asset to be a part of the approval process, you need to upload the asset as a managed file. If you upload the asset as a URL, only the URL assignment is a part of the approval process. The file or content that is referenced by the URL is not a part of the approval process and must be approved separately. If you do not need the contents of an asset to be approved, use a URL for the asset.
- If you use a remote web server in your WebSphere Commerce environment, it is recommended that you have an IT developer transfer static web assets to your remote web server. By transferring the assets to the web server, the assets are not deployed to the EAR and avoids consuming your WebSphere Commerce application resources.