Preview behavior
- Caching must be disabled for preview to function properly.
- When you click the preview button, the preview session refreshes.
- Preview runs in it's own web application, on a non-standard port so that it can be protected by a firewall.
- Only one store preview window opens at a time. If a preview window is open and you click OK on the Store Preview options page, the preview will open in the existing window.
- By default, the store preview options page displays the store home page URL of the store with which you are working in WebSphere Commerce Accelerator.
- You can enter any valid store URL in the What store URL do you want to preview? field. However, if you enter a URL for a store other than the store you are logged into in WebSphere Commerce Accelerator, the date, time, and inventory options you chose will not be reflected in the preview.
- While previewing your store, if you navigate away from the store you are logged into in WebSphere Commerce Accelerator, the preview context is lost. The loss of preview context means that the date, time and inventory options set on the store preview options page will not be reflected in the preview. If you navigate back to the store you are logged into in WebSphere Commerce Accelerator, the preview context will not be restored.
- If you change your store selection within WebSphere Commerce Accelerator, and the preview window is open, the preview window remains on the page it was on before you changed stores. At this point, if you navigate to the Store Preview options page, the new store's URL displays in the What store URL do you want to preview? field. If you do not make modifications to the URL and click OK, the new Store preview page will display in the same window the existing store preview page.
- When you launch preview, you are a guest user. If you enter a store URL that is not accessible by a guest user, you might see an error page.
- You can disable commands from running within preview. For more information see Commands and view restrictions in preview.
- If you perform analytics on user traffic, someone testing the site using preview should not be logged since they are not an actual user. To avoid logging the user traffic of person using preview, user traffic logging is disabled within preview by default. If desired, you can configure caching to capture user traffic data.
- If you have created customized business contexts for the business context engine, you can use these business contexts within preview. For more information see adding customized business contexts to preview.
Related concepts
Related tasks
Feedback
(C) Copyright IBM Corporation 1996, 2005. All Rights Reserved.