If your environment includes remote preview (that is, the preview application is deployed on ATG servers that do not run the Business Control Center), you must specify a preview domain or host name.
If your environment uses a domain name-based URL strategy, both the remote preview application and the publishing server must run in the same domain. When merchandisers launch a preview session, Merchandising attempts to obtain the domain from the server name in the preview URL. To ensure the correct domain is used, specify a preview domain with the previewDomain property of the atg/dynamo/service/preview/PreviewManager component. For example:
# PreviewManager.properties # Explicitly sets the document.domain property in both the BCC page and the #preview page to "oracle.com" previewDomain=oracle.com
Configuring Browser Security Settings for Merchandising Users
If your environment includes remote preview, configure all browsers from which users access Merchandising to automatically accept, or prompt for acceptance of, third-party cookies. Alternately, specify the preview domain as a trusted domain from which cookies are always accepted. This type of configuration is recommended for all supported browsers but is required for Microsoft Internet Explorer 9.
To configure Microsoft Internet Explorer 9 to accept cookies from the preview server, complete the following steps. Note that this procedure configures an individual installation of Internet Explorer 9. You can also configure multiple installations with a Group Policy.
In Internet Explorer, click the Tools button, then click Internet options.
Click the Privacy tab, then move the slider to a position between the top and bottom, neither blocking all nor allowing all cookies.
Click Sites.
In the Address of website box, type the name of the preview server, including the domain name, then click Allow.
Click OK.
Visual Merchandising allows Merchandising users to select assets to organize and edit directly from a preview session. Visual Merchandising then automatically updates the preview session with the merchandiser’s saved changes.
Visual Merchandising works through sensors, which detect specific elements encountered in a JSP when rendering an HTML page in a preview session launched in Merchandising. These sensors fire events that are detected by event listeners, which then insert CSS classes, called item identifiers, to class tag attributes when the HTML page is rendered. Item identifiers contain the repository item type and repository ID of the most recently accessed category, product, or SKU. When Merchandising users right-click a marked asset in a preview session, these classes are used to display the Visual Merchandising pop-up-menu.
You can configure Visual Merchandising to automatically insert item identifiers, but we recommend that you explicitly tag JSP pages for use with Visual Merchandising so you can more precisely control where item identifiers are inserted. You tag JSP pages for Visual Merchandising by inserting <preview:repositoryItem> tags in JSP pages.
The <preview:repositoryItem> tags work through calls to the setExplicitIdentifier method of the /atg/dynamo/service/preview/PreviewTaggingUtils component. PreviewTaggingUtils invokes the setExplicitIdentifier method of the /atg/dynamo/service/preview/fluoroscope/sensor/PreviewTaggingSensor component that fires events of type PreviewTaggingSensor.ExplicitIdentifierPreviewTaggingSensorEvent. This event updates the class attribute of a tagged page element (category or product) with an item identifier that starts with atgRepo-atgrep:/ and include an asset URI composed of the repository name, item descriptor name, and repository ID. For example, the following class string identifies a specific product: atgRepo-atgrep:/ProductCatalog/product/xprod2015. Merchandising uses the item identifier to display the Visual Merchandising menu when a Merchandising user right-clicks the asset during a preview session.
For more information, see Tagging Pages for Visual Merchandising.
