For the latest information regarding technology support for the Coronavirus situation, please visit UCI TechPrep.

Create Transports and Destinations

Work with a Systems Administrator to Prepare the Site for Publication

Specific information will need to be acquired from your systems administrator before the site can be published from Cascade to the desired server/web url. These details include the following:

  • For the Transport
    • Server name
    • Server port
    • Directory pathway where the files will be stored
    • User name access to the server
    • Password used to access the server
  • For the Destination
    • Directory pathway where the files will be stored

Create a transport

Transports are the mechanisms that move content from Cascade Server to the contents final, published location; generally a web server or database. A site can have more than one transport and destination, which makes it ideal if the site needs to be published to a development/staging area before being sent on to the production/web server.

Create the (S)FTP transport

  1. Click Administration on the menu bar.
  2. Select Transports in the side bar.
  3. Click New Transport in the Transports section.
  4. Select FTP and SFTP for the Transport Type and click Submit.
  5. Provide an identifying name in the System Name field.
  6. Leave the Parent Container at its default setting.
  7. Input the Server Name, Server Port, Server Directory, Username and Password information as provided by your systems administrator.
  8. Check the Use Secure FTP (SFTP) box.
  9. Type FTP Server into the System Name field.
  10. When finished, click Submit to create the new transport.

Create a destination

Destinations simply serve as an intermediary between Transport and assets that need publishing. This separation allows for the reuse and easy maintenance of Transport. Without Destinations, a change to the server being published would require updating every Transport that published to that server. These changes could be a credentials change, server host name, port number, etc. By using Destinations as an intermediary, then a change to a server would only require one change to its Transport with no need to modify the various Destinations.

This separation is also useful when publishing to different directories on the same server. In this case, only one Transport is created for the server, but multiple Destinations are created each containing a different directory path; and once again, should any change be made to the server, only one change would need to be made to the transport.

Lastly, Transports can be shared between Sites, so a common repository of transports can exist in one Site for use across all Sites in the system. In this setup, only Destinations need to be created for all your Sites and they would use Transports from the common repository.

Test the destination

  1. Click Administration in the menu bar.
  2. Click Destinations in the left.
  3. Click New Destination in the Destinations section.
  4. Provide a clear explanatory name in the Name field, such as ‘YourWebSite Dev’.
  5. Input the directory pathway used in your Transport in the Directory field.
  6. Click on the Transport icon and select the transport previously created.
  7. In Applicable for Groups, scroll through the list and select the groups which should be affiliated with the ability to publish out the website the server specified in the transport.
  8. When finished, click Submit to create the new destination.
Scroll Up