Release Notes: IBM Aspera Virtual Catcher 2.4.6

Product Release: February 22, 2017

Release Notes Updated: February 24, 2017

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

NEW FEATURES

  • Users can now control file deletion in the Failed folder. When No is selected for this option in the configuration (Operational Parameters), Virtual Catcher doesn't delete files from the Failed folder; thus, users can manually reprocess files. When Yes—which is the default—is selected, files are deleted during cleanup.
  • There is a new option to receive notification only upon asset failure. When Yes is selected for this option in the configuration (Notification Parameters), Virtual Catcher only sends notifications for failure events. When No—which is the default—is selected,Virtual Catcher sends notifications for success, failure, and purge events in the usual manner.

ISSUES FIXED IN THIS RELEASE

ORC-1206 - File cleanup does not occur as expected when a value is entered for number of days before file deletion (in the Operational configuration parameters, Number of days after which all files on disk will deleted in the success and failure folders).

ORC-1202 - When the ADI.DTD file is not present in the asset package and the Always copy ADI.DTD file to CMS option (in the Operational parameters) has the value No, the Catcher workflow fails.

ORC-1200 - The File System Cleanup workflow errors when there is a folder that Virtual Catcher cannot delete (because of a lack of permissions, for example). This issue is caused by a parameter configured on the wrong step in the workfllow.

ORC-1199 - The notification workflow does not log confirmations of notifications that are sent or the results of those notifications.

ORC-1198 - The File System Cleanup workflow does not log files that are being deleted; it only logs the file count.

ORC-1197 - When an asset fails, only the files in the drop folder are moved to the failed folder; thus, the empty folder from the package remains in the drop folder.

ORC - 1196 - If an MDU ADI.xml file does not contain any <Asset> tags in the XML, the plugin fails.

ORC-1194 - In the File System Cleanup workflow, disk space calculations are made in KB, instead of bytes. This issue is the root cause of ORC-1193.

ORC-1193 - When Virtual Catcher cleans up (deletes) files from the success or failure directory—in the usual situation where the amount of free space goes below the minimum amount configured—it ignores the configured value for Number of minutes files will be retained and thus deletes all files, even file that were recently transferred or created.

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-2.4.6.139808-linux-64.tar
md5: 88d21114dea50361af9f2f408e499d43
sha1: ccbdff8530284e535efa24f6b022a6d14129835d
Windows: AsperaOrchestrator-VC-Bundle-Setup-2.4.6.139808-x86.exe
md5: 2ac4c96afc8b500ede3c38080cdcbd11
sha1: c0bbdb32d62149aff8df2445826b1351f8e9aa01

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