If you have installed a preview server, the Preview button will be available in Site Administration. When sites are created or modified, they can be displayed in preview mode, which shows the site as it would be presented to a given user on a specific page of a particular website. Additionally, the site context will be automatically passed to the preview launcher based on the site that is currently selected.
You must create the preview URL properties for each JSP that serves as a landing page for that Web application. The name
value of the properties file identifies the JSP as a landing page. This assists the site administrator by making landing page Preview URLs easily identifiable in the preview launcher.
Note: It is important that the site administrator work with the site developers to identify which preview URLs map to the page for the site that they wish to preview.
The following components are required for the preview launcher:
Preview User – The preview is based on a user and will display the site and landing page as it will appear for this user. The users who can be selected for the Preview User parameter are defined by the development team as part of the preview functionality.
Preview Site – In a multisite implementation any page or other ATG asset could appear on more than one site, so the site context for the preview must be determined.
Preview Landing Page – This is the JSP page that will be previewed. Each page that can be previewed has an associated preview URL properties file, which contains information that enables the system to preview that page.
For information on configuring a preview server and the necessary properties files, refer to the Business Control Center Administration and Development Guide. For information on using the Preview Server in the Business Control Center, refer to the Business Control Center User's Guide.