Release Notes: IBM Aspera Virtual Catcher 2.4.4

Product Release: September 19, 2016

Release Notes Updated: September 19, 2016

WHAT'S NEW

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

New Features

  • The CORBA plugin timeout has been increased to 60 minutes (3600 seconds).
  • Virtual Catcher now supports multiple CORBA calls to the CMS; this is limited to 3 by default.

ISSUES FIXED IN THIS RELEASE

ORC-909 - Assets are not moved out of the staging directory after a successful CORBA pull.

ORC-887 - [Windows] The CORBA Plugin is unable to locate the .jar file.

ORC-884 - [Linux] During an upgrade from Virtual Catcher 2.4.2 or 2.4.3 to a newer version, the license file (/opt/aspera/etc/aspera-license) is deleted.

ORC-879 - The Ingest Status Dashboard is listing assets in the wrong order, with the most recent asset at the end of the list, instead of at the top.

ORC-878 - The Alternate Drop Directory does not support folders and files.

ORC-876 - The CORBA Plugin Log file path has the syntax of a Linux path rather than a Windows path.

ORC-865 - The system defaults to email notifications when the REST notification option is set in the configuration.

ORC-864 - When packages are dropped into the alternate drop watch folder location set in the configuration, they are not caught and processed.

ORC-846 - On Windows, the default parameter values for the staging, fail, and success directories in the Virtual Catcher configuration have Linux syntax; for example, /tmp/staging instead of C:/tmp/staging.

ORC-830 - Because the client-side binding port is statically written as 8844, multiple CORBA calls cannot be made from a Catcher to the ARRIS CMS; only one process can link to each port.

ORC-723 - The avcoperator user is able to view the configuration dashboard (Dashboard > Virtual Catcher Config), which is supposed to be hidden.

SYSTEM REQUIREMENTS

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

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.16
Browsers: Firefox 27-48, Google Chrome 40-50

PACKAGE INFORMATION

Linux 64-bit (rpm): aspera-orchestrator-vc-2.4.4.131801-0.x86_64.rpm
md5: 1b4dcfbdd9b7de2e5bba978addc1cf44
sha1: c919f2d0bfc5dea0090926982ce98339fa417d5e
Windows: AsperaOrchestrator-VC-Setup-2.4.4.131801-x86.exe
md5: f01a53ad03163b7400e9abc697531996
sha1: 8fbee21ba28cd21773f15c0cefc535d13d87ef1f

KNOWN ISSUES

ORC-913 - [CentOS and RHEL 7.2.1511 (Core)] Virtual Catcher does not start on reboot unless the systemd-sysv OS library version is systemd-sysv-219-19.el7_2.4.x86_64. Workaround: Run the following commands, as root:
rm -f /etc/init.d/AsperaOrchestrator
cp /opt/aspera/orchestrator/bin/AsperaOrchestrator /etc/init.d/AsperaOrchestrator

PRODUCT SUPPORT

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

0 Comments

Please sign in to leave a comment.
Powered by Zendesk