Catalog and marketing attachments
For the catalog and marketing components, an attachment consists of one or more files associated with a catalog or marketing asset. A catalog or marketing asset can also have multiple attachments.
When an attachment consists of multiple files, the files in the attachment are differentiated by language. That is, each file in the attachment applies to a different language or set of languages. Two files in the same attachment cannot apply to the same language.
The same file cannot be used in different attachments. To use the same file in different attachments, you must use copies of the files in the different attachments.
In addition to the files it contains, an attachment has the following properties:
- Usage
- The usage defines the use of an attachment and can be used by a JSP application developer to determine which attachments to display. You are provided with an initial set of usages and you can add more usages as required.
- Sequence
- The sequence value determines the order in which the attachments will be displayed for a specific usage.
Some uses for attachments include:
- Using one link on a product's display page to provide access to user manuals in different languages. When users click the link to the manual, they view it in the same language in which they are viewing the site.
- Providing a marketing activity with a URL that links to a promotional movie about a campaign.
By default, the types of files that can be used as attachments is limited. Some common file attachments include:
- Flash or Shockwave animation files
- GIF, JPEG, and TIFF image files
- PDF document files
Tools available in WebSphere Commerce Accelerator allow you to create attachments, change attachments, and upload files that you can use as attachments. Any file uploaded using the attachment tools in WebSphere Commerce Accelerator becomes a managed file. When a managed file is assigned to a catalog or marketing asset, the file becomes an attachment.
Managed files are initially written to the WebSphere Commerce database. Once certain criteria are met, managed files are copied from the database to the WebSphere Commerce EAR file. In a federated environment, all copies of the WebSphere Commerce EAR file are updated automatically.
You cannot view the attachment file in a store page until the attachment file is available in the WebSphere Commerce EAR file. While the attachment file is available only in the WebSphere Commerce database, you can view the file only in a store page using the preview function.
A JSP application developer references attachments when designing a store using the Attachment code snippet and the attachment data bean. WebSphere Commerce ensures that the correct attachment asset displays, depending on the language of the user when browsing the store.
Catalog and marketing attachment assets are not managed using the Manage Files menu item in WebSphere Commerce Accelerator.