Release Notes: IBM Aspera Virtual Catcher 3.0.0

Product Release: 06/19/17
Release Notes Updated: June 19, 2017

This release of IBM Aspera Virtual Catcher provides the new features, fixes, and other changes listed below. Additional sections cover system requirements and available documentation.

NEW FEATURES

Dashboards and Configuration

  • A new dashboard, Faspex Package Status, displays the download status for packages.
    Note: The Faspex Package Status dashboard is not activated by default. To activate this dashboard, do the following:
    1. Open the Virtual Catcher Config dashboard.
    2. Under the Common "OperationalParams", set Sync with Faspex of content provider to Yes.
    3. Refresh the web page.
  • The following improvements have been added to the Assets Status dashboard:
    • Dashboard displays status for multiple CMS targets
    • Users can relaunch a transfer session for a particular CMS from the dashboard
    • Dashboard displays license start and end dates
  • Files can now be sent from a single server to multiple CMS locations. This new feature can be configured in avc.yml and the UI.

Workflows, Work Orders, and Automation Processes

  • Users can now transfer files from a single server to multiple CMS targets.
  • CMS-specific workflow content is now split into smaller sub-workflows for easier analysis and debugging, and is no longer in the ToCMS workflow.
  • Notifications now include ADI version information for packages.
  • The improved Work Orders page reduces the necessity for "drill-down" to find necessary information by displaying work order instances next to the corresponding workflows.
  • Multi-layer folder cleanup of empty directories is now available in the asset drop directory.
  • All work orders related to an asset are now assigned specific naming conventions:<xml_file_name><asset_id><provider_id>, and <folder_name>.
  • There is an improved data display in the Notification Queue.

Other Changes

  • The ADI parser tag <content> is now optional.

ISSUES FIXED IN THIS RELEASE

The reprocessing of assets upon upgrade does not function properly following a change in the workflow ID (on which persistence scope depends).

When MDUs are sent to CORBA, the wrong file name is selected because the staging XML file is not updated in the database.

The asset directory for failed transfers is not functioning properly.

The cleanup of empty directories in the asset drop directory is not functioning properly.

File cleanup does not properly consider the age of the files. For example, in some cases, files older than 60 minutes are not respected: all are deleted.

SYSTEM REQUIREMENTS

Windows 64-bit: 2008 R2, 2012 R2, 7, 8, 10
Browsers: Firefox 40-50, Google Chrome 50-56

Linux 64-bit: RHEL 6.0-6.7, 7.0-7.2; CentOS 6.0-6.7, 7.0-7 (1511).
Aspera Common Components 1.2.19
Browsers: Firefox 40-50, Google Chrome 50-56

PACKAGE INFORMATION

Linux 64-bit (rpm): aspera-orchestrator-vc-bundle-3.0.0.144843-linux-64.tar
md5: 0da407719e339c7d314fc66c0eb68363
sha1: 5c50f0d434aef7e6a5d50e4a31de016344fbd442
Windows: AsperaOrchestrator-VC-Setup-3.0.0.144843-x86.exe
md5: a620e4c8ce6f366b15bb4a7bee490df7
sha1: 95e168ea431622e34a49819903ebf71aa39ea880

PRODUCT SUPPORT

For online 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

0 Comments

Please sign in to leave a comment.
Powered by Zendesk