Release Notes: IBM Aspera Virtual Catcher 2.4.2

Product Release:

Release Notes Updated: June 7, 2016


This release of IBM Aspera Virtual Catcher for Windows and Linux provides the new features, fixes, and other changes listed below.

New Features

  • New CORBA plugin support with runtime inputs and configuration options enables CORBA calls to CMS to initiate an ingest.
  • In addition to individual installers for Linux and Windows, Aspera Virtual Catcher now comes with a bundle installer for Linux—which installs Aspera Virtual Catcher, Aspera Cargo and Aspera Point-to-Point—for ease of setup.
  • A visual dashboard is now available to track the progress of a package through the system.

Other Improvements

  • Email notification support is now available in addition to Rest API notifications.
  • There is support for Windows in this release.
  • The cleanup process now only deletes the success, fail, and staging directories.
  • The AVC workflow now waits for the XML file to confirm the list of sent files. Once all files are received (and not before then), it updates the Dashboard; then it performs verification to ensure the files conform to the ADI standard.
  • The timeout allowance for the CORBA call has been increased to 10 minutes.
  • Files can now be copied to a dropbox using Aspera FASP.
  • Additional configuration options (values indicated are the default value):
    • Ingest frequency is configurable and is set for pickup of an incoming asset per 60 seconds.
    • Concurrent asset processing is 10 at a time.
    • Failed, Orphaned and Successful file retention is now 60 minutes.
  • The ADI.DTD file is moved to the CMS dropbox folders and the staging folders.
  • The asset dashboard includes filtering based on package status.
  • The asset dashboard includes a link to the Work Order.
  • Assets moved to the Success folder now have a unique naming convention to help prevent overrides.


RPM uninstall fails.

Entering the IP address does not redirect to the product pages; instead, it shows a static Apache page.

Empty directories are left in the drop folder.

CSS does not load consistently in Windows browsers.

There are issues with files with the same name coming from different packages.

A workflow has issues when it encounters files with the same name as other files which come from different packages.

The staging directory is deleted during a high-concurrency situation.

Heartbeat needs to be disabled by default, with an option to enable it.

REST posts have an invalid POST body.

Time stamps have an invalid format. Invalid authentication tokens are being sent to REST calls.

An authentication token is never renewed.

No "TRANSMISSION success" message appears after the asset is deemed complete.

Plugins are not recognized after an automatic (default) installation.


Windows 64-bit: 2008r2, 2012r2, 7, 8, 10
Browsers: Firefox 27-48, Google Chrome 40-50

Linux 64-bit: RHEL 6-7, CentOS 6-7.
Browsers: Firefox 27-48, Google Chrome 40-50


Linux 64-bit (rpm): aspera-orchestrator-vc-
md5: b0011343b81bebeef20ed13f256525e2
sha1: 0454a6d990c9e5beadc1d0c593e8311923e01c79
Windows: AsperaOrchestrator-VC-Setup-
md5: fa4f76a8d7bb8352c1bec7f22c7346c7
sha1: 743b1421c9feca181647bde17cead80f931ac80a


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk