• KB Home |
• Need Help?

Learning Levels

• Digest
• Concept
• Technical

Announcements

With the release of Cascade Server 6.0, there a two potential use cases for Destinations, at the system-level (in the Global Area), and on a per-site basis. When using Destinations in the Global Area, they will be linked to a system-wide target, whereas when used on a per-site basis, each Destination represents the link between a Site and the location to which site content is published.

At the Site-level:
A Destination defines the link between Site content and the location to which site content can be published. Destinations allow for publishing content on a schedule, and specifies encoding (UTF-8 or ASCII) for the published content. A Destination is associated with a single transport that defines the protocol and location of a remote server to use when publishing content out of the system. In other words, whereas a Destination defines the link between a Site and transport, a transport represents the physical location of a server which can be used for any number of Sites.

At the global-level:
A Destination represents a location to which a Target can be published, allows for publishing content on a schedule, and specifies encoding (UTF-8 or ASCII) for the published content.

Destinations are useful for controlling individual sites that may need different settings, or that publish on different schedules using different locations (represented by transports). Each Destination has a transport that represents a server where the Site's published content will reside. Destinations have access rights enabled that control who can view, create, edit, and delete the Destination itself. Destinations also have applicable groups which control who can publish to the Destination. Each of the aforementioned Destination features is modified by clicking "Edit" on the Destination itself.

When publishing a Site or site content (or a Target, when using destinations in the Global Area), Cascade Server allows the selection of the individual Destinations that are associated with that Site. This is generally used when content is to be published to a development or internal server for final quality assurance before being pushed to a live site.

A Site contains a collection of one or many Destinations; these Destinations define the locations where the Site can publish to. The location is defined by the transport associated with the Destination, and the transport represents a server location. The directory that is specified in the Destination will override the directory specified in the transport that the Destination uses.

Creating a new Destination at the global level

To create a Destination:

1. Select ‘Administration’ from the top navigation menu.
2. Select ‘Targets & Destinations’ in the left navigation pane.
3. Select the target to which a destination will be added.

    

4. Click ‘New Destination’.
5. Complete the following fields in the ‘General’ tab:
   
   
   1. Name – How the system identifies the destination.
   2. Directory – Generally, this value is inherited from the transport. An absolute path may be entered here if content needs to be directed to a different folder than the one identified in the transport.
   3. Transport – Use browse icon to select desired transport.
   4. Target – Use browse icon to select desired target.
   5. Activation – Allows users to temporarily deactivate certain destinations without having to delete and recreate them later.
   6. Output – Cascade Server publishes content in Unicode by default; this may be overridden by selecting the ASCII checkbox.
   7. Scheduled Publishing - Allows content to be automatically published on a recurring schedule. See Scheduled Publishing concept for more information.
   8. Applicable for Groups – Determines which groups may publish to the destination. Unless a group is defined here, this destination will not show up on an asset's list of available destinations on the publish screen for that group.
6. Click Submit to save the new destination.

When publishing content, destinations may be checked or unchecked to allow users added flexibility in regards to where to publish content on an ad hoc basis.

Creating a new Destination at the Site-level

1. Select 'Administration' from the top navigation menu.
2. Select 'Destinations' in the left navigation pane.
3. Select the target to which a destination will be added.
4. Click 'New Destination'.
5. Complete the following fields in the 'General' tab:
   1. Name - How the system identifies the destination.
   2. Directory - Generally, this value is inherited from the transport. An absolute path may be entered here if content needs to be directed to a different folder than the one identified in the transport. The following are three examples of how the directory field can be used:
      • If the Destination directory field is empty, the transport directory will be used to determine where content is published.
      • If the Destination directory contains an absolute path, the transport directory will not be used. The Destination directory will be used as the exact path where content is published.
      • If the Destination directory contains a folder name, then the folder supplied in that field is appended to the end of the transport directory where content will then be published. For example, if the Transport Directory points to the "test/main" folder on the server and "new/destination" is filled into the Destination Directory field. Content using this target and destination will be published to the "test/main/new/destination" folder.
   3. Activation - Allows users to temporarily deactivate certain destinations without having to delete and recreate them later.
   4. Output - Cascade Server publishes content in Unicode by default; this may be overridden by selecting the ASCII checkbox.
   5. Scheduled Publishing - Allows content to be automatically published on a recurring schedule. See Scheduled Publishing concept for more information.
   6. Applicable for Groups - Determines which groups may publish to the destination. Unless a group is defined here, this destination will not show up on an asset's list of available destinations on the publish screen for that group.
   7. Web URL - A base URL which will be used for linking to configurations which are associated with this destination on its content type (see "Link Rewriting with Destination URLs").
6. Click Submit to save the new destination.
7. 
   When publishing content, Destinations may be checked or unchecked to allow users added flexibility in regards to where to publish content on an ad-hoc basis.

© 2001-2012 Hannon Hill Corporation

Site Index | HH Internet | KB Feedback

Contact Us: Online Form | +1.678.904.6900