Transport
Digest
A Transport represents a server to which content can be published. Transports can be used by one or more Destinations. Destinations provide an extra layer of abstraction on top of Transports that allow users to publish content to different locations on the same Transport. Basically, a Transport is "how" the content gets there and Destination is "where" it goes.
Transports can transfer content to an FTP/SFTP server, a file system location, or a MySQL database.
Technical
Types of Transports
File System – File system Transports can push out content to a location on the CMS server’s hard drive or to a mapped network location. In order to successfully publish using a Transport that points to a mapped network location, the operating system level user executing the Cascade system process must have the appropriate privileges to write to and create new files in the network publish location. Read more about File System Transports.
FTP/SFTP – FTP/SFTP Transports push content to a remote server via the FTP or SFTP protocol. The account specified in the Transport's settings must have appropriate privileges on the remote server to navigate through the folder structure, write, and create to ensure that publish operations do not encounter errors. Read more about FTP/SFTP Transports.
Database – Database Transports push content to a MySQL database that uses a specific database schema. Live reads can then be performed on the published content by a separate application. Read more about Database Publishing.
Transport Diagnostic Utility
The diagnostic utility allows users with the "Run Transports and Destination diagnostic tests" Role ability and read access to the Transport to test its connectivity without invoking a publish.
To run a Transport test:
- Navigate to Administration > Transports
- Select the Transport you wish to test.
- Click Test Transport link above the list of Transports in the left-hand navigation menu.
- On the resulting screen, click Submit to test the connectivity of the Transport. If there are no errors, the screen will indicate "Test Successful!" If errors are found, the screen will identify the problem that occurred.
Cross-Site Relationships
Transports can be created for Sites individually but can also be shared across Sites. Sharing of Transports is accomplished by assigning a Transport that lives in one Site to a Destination that lives in another Site. On the Destination create/edit screen, a Transport chooser is used to assign a Transport to a Destination. The chooser window that pops up after clicking the chooser link will contain a Site dropdown at the top (assuming the current user has access to more than one Site). This Site dropdown can be used to switch into another Site and choose a Transport that does not live in the current Site.
For more information on Cross-Site relationships for Transports, check out our Cross-Site relationship rules page.