Creating publish destinations and transports: SFTP
What is a transport and destination?
Put simply, in Cascade's CMS, a transport is the vehicle that carries your content and the destination is where you want that content delivered. In the case of your site, your designated site administrator and manager have the ability to configure these options so your site can be published to the web.
Network and Firewall Settings
For client systems administrators that want to restrict SFTP access to their webserver (via a firewall, for example), note that the Cascade Web CMS SFTP communication will use only a single IP address: Cascade CMS Server IP:
The client system administrators can define the port used for SFTP communication as well. The default port is 22.
Create a Transport
- In Cascade, under the "Administration" tab, select "Transports."
- In the left panel, select "New Transport." Then select "FTP and SFTP" radio button and submit.
- Fill in the form with the appropriate SFTP information and submit:
- System name: a name/label for this transport (you could have more than one)
- Parent Container: the default is fine
- Server Name: the IP or DNS name of the SFTP server. If the server is the campus virtual webhosting service, the server name will be cpanel.ucdavis.edu.
- Server Port: usually 22
- Server Directory: an optional path to the directory where stuff will be published. Use this if you haven't constrained the destination directory on the SFTP server side (which is best)
- Username: the SFTP access user name
- Password/Confirm Password: password for the user
- Use Secure FTP (SFTP): make sure this is checked
- Use Passive FTP (PASV): should be unchecked
- Select your new transport in the left panel
- Select the "Test Transport" link and submit.
- If all is well, you should see: "Test Successful."
- If you get an error, contact your server administrator or the Web CMS team. Otherwise you can move on to creating a publish destination using the new transport.
Create a Destination
- In Cascade, under the "Administration" tab, select "Destinations."
- In the left panel, select "New Destination" and submit.
- Fill in the information for the publish destination and submit:
- Name: name or label to identify this destination (you could have more than one)
- Parent container: the default is fine.
- Directory: optional and probably not needed
- Transport: select the icon and choose the transport you created above in the popup window and submit
- Activation: enable destination should be checked
- All other values: no changes from the defaults
- Select your new destination in the left panel, select the "Test Destination" link and submit. **Currently there is a bug in this function and the destination can only be tested by the campus Web CMS team. Contact them (firstname.lastname@example.org) and they will test and will move on to the next section of assigning user groups if the test is successful.
- You may select any combination of parameters (including the default 0/100K) and submit. However, recommended test would be to select 1 file at 100K in size.
- You should see: "Test Successful."
- If you get an error, contact your server administrator or the Web CMS team. Otherwise you can move on to assigning users groups to be able to use the destination you just created to publish content.
Assign user groups that can use this destination
Once you have completed the other steps above, only Site administrators can publish content. Other user groups must be assigned to a publish destination in order to be able to publish content. The Web CMS team must perform this last step. When you are ready to allow other users assigned to the site to publish, contact the Web CMS team.
The Hannon Hill site has more information about this process: