Combining Media Shuttle and Jet in Workflows

Jet system-to-system automated transfers can be combined with Media Shuttle to send and receive content within and between organizations. Combining both applications can help extend workflows from internal company systems to other companies, partners, and customers.

Sending Content

When sending content in a distribution workflow, transfers driven by Jet can send content from an internal system to Media Shuttle users by transferring data to an SDCX server that also functions as portal storage. This allows content to transfer from an internal asset management system to recipients in distributed locations. Jet can also be used with a Share portal to distribute files that are part of a larger workflow that provides access to a common storage location.

A Jet to Media Shuttle distribution workflow includes:

• A Jet job that has its source endpoint on the company's internal network and its destination endpoint in the perimeter network
• A Send or Share portal with a storage path that points to the same location as the destination endpoint for the Jet job

The Media Shuttle System-to-Person Automation API can also be used to integrate both Signiant applications. When a Jet job transfers content to the destination endpoint in the perimeter network, that content also becomes available within the portal storage. The System-to-Person API can be used to create a Media Shuttle package with the content, then sends a generated URL to a user who can then download the content.

Receiving Content

Media Shuttle and Jet can be integrated to receive content from Media Shuttle portal members and transfer uploaded content to another storage location using Jet. When content is uploaded to a Media Shuttle portal, it is added to a source directory for a Jet job, which starts based on its trigger type.

A Media Shuttle to Jet receiving workflow includes:

• A Share or Submit portal with a storage path that points to the same location as the source endpoint for the Jet job
• A Jet job that has its destination endpoint on the company's internal network, and its source endpoint in the perimeter network

By transferring files through a common location, typically in a perimeter network, submitted content can move directly into a Jet workflow that transfers to a secure server within a corporate network, or by using a partner job to send content to another organization.

Note: Transferring a large data set in Media Shuttle generates #work_file# and #chkpt_file# temporary files while transferring to storage. Hot folder jobs may transfer these files during a Media Shuttle upload. Once all transfers are complete, these files can be safely deleted on the receiving endpoint.

Linking Media Shuttle to Jet

To link a Media Shuttle portal to a Jet job:

1. In the Jet Administration Console, create a storage profile on the SDCX Server to use as a source folder.
2. In the Media Shuttle IT Administration Console, Assign the same SDCX Server as a storage location for a Media Shuttle portal.
3. Configure the Path to match the storage profile directory created in the Jet Administration Console.
4. Click Save Changes.
5. In the Jet Administration Console, create a job using the associated Media Shuttle storage profile.

As files are transferred to and from Media Shuttle portals by portal members, Jet will determine when to send files to the receiving endpoint based on the job trigger type.