Aspera Virtual Catcher handles the complex catcher steps and interactions supported by traditional satellite pitcher-catcher systems, in the service of media distributors and content providers who need to transfer ADI 1.1-compliant media packages. It contains a set of purpose-built workflows combined with configuration and status screens to track the process.
Once package files are received by either Aspera Cargo or Aspera Point-to-Point, Virtual Catcher picks up the files that were transferred and performs the following operations:
- Validates that the received XML file is compliant with the ADI 1.1 specification.
- Verifies that the package and its contents have been delivered in its entirety, the metadata file is in correct format, and the package’s contents match the file size and checksum specified in the metadata file.
- Sends confirmation of package validation success or validation failure via email or REST call notifications to the pitcher and system users.
- Hands off the files to the recipient’s content management system (CMS).
The following diagram illustrates this process.
- Send the files to a local CMS.
- Deposit the package files into a watchfolder interface to be picked up by the CMS.
- FTP the files to the CMS.
- Invokes a CORBA call to notify the CMS of an available package that Virtual Catcher has staged on an FTP server.
The pitching system for Virtual Catcher can use Aspera Faspex, Enterprise Server, or Connect Server (all of which contain Aspera's FASP transport technology) for sending package files to the recipient systems. Pitches can also be initiated with Aspera Console or through Aspera API calls. On the catching end, Virtual Catcher utilizes Aspera Cargo or Point-to-Point to monitor the status of received packages.
The solution is installed on the receiver sites, but it is owned and licensed by the media distributor or a content provider.