Release Notes: IBM Aspera Console 3.0.3
Release Notes: IBM Aspera Console 3.0.3

Release Notes: IBM Aspera Console 3.0.3

Product Release: December 10, 2015
Release Notes Updated: December 10, 2015

WHAT'S NEW

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

New Features

  • Watchfolders: A watchfolder is an automation of file transfers from a source to a destination system. Files placed into a source folder are automatically transferred to the destination. It runs on the client side only and does not require any additional software on the destination system. Adding a watchfolder-enabled node and the watchfolder instance to Console enables Console to monitor and report transfers initiated by the service. Watchfolder requires Enterprise Server 3.6.0+ with a watchfolder-enabled license.
  • License: Console now stores license information in the database, rather than in a file located at /opt/aspera/console/config/ (Linux) and C:\Program File (x86)\Aspera\Management Console\config (Windows). If a license is added to the directory before the upgrade script is run, the script migrates the license information from the file into the database and deletes the file.
  • Reports: Time information ("Actual start", "Finished", and "Total run time") now display at the bottom of the report screen.
  • Security: Upgrades to Ruby 2.0.0, Java 8, and OpenSSL 1.0.1p.

ISSUES FIXED IN THIS RELEASE

#32999 - Spaces in report field names contaminate table fields.

#33689 - Simple transfer API call fails if "archive_after_transfer" is missing from the JSON.

#33700 - Simple transfer API call fails if "file_exclude_by_timestamp" is missing from the JSON.

SYSTEM REQUIREMENTS

Windows: 2008r2, 2012

Linux 64-bit: RedHat 6-7, CentOS 6-7, SUSE 11
Aspera Common Components 1.2.15

Browsers: Firefox 27+, Safari 6+. Internet Explorer 8+. Chrome 40+

PACKAGE INFORMATION

AsperaCommonComponents: aspera-common-1.2.15.115916-0.x86_64.rpm
md5: 004a54a726172c9347c2981567efe715
sha1: df0076e99614572e3ee1ea53efd8f12b6736e552
Linux 64-bit (rpm): aspera-console-3.0.3.116932-0.x86_64.rpm
md5: f44aae7e81012bf91fa0fe8fb31885c4
sha1: a973d1ac1d32bf8f0c4709138f06d6289d1f65a4
Windows: AsperaConsole-3.0.3.116932-windows-32-msvc2012.exe
md5: eab87bcc89bbccc2b06ec4d7457ab734
sha1: f7995a766248099492d59b586275a049c1e8be98

KNOWN ISSUES

#31098 - (Linux Only) Upgrading the common components from version 1.2.9 to any newer version deletes the /usr/bin/asctl symlink. Workaround: Installing Console or Orchestrator after upgrading the common components will recreate the missing link during the installation process.

#27371 - ADFS SAML users running Chrome on a Windows machine are currently unable to log in. Workaround: Turn off "Extended Protection" in ADFS SAML IdP. After doing so, you may at first see ADFS SAML user login failures with an "Invalid SAML response" error and infinite redirects on login. After some time, however, the failures end.

#27236 - As of Console 2.5+, because Console now generates reports of the type XLSX (rather than XLS), any reports you completed before upgrading to this release of Console are no longer accessible through the web link. However, any reports that were not completed before the upgrade (such as scheduled reports) are unaffected. If a report was configured to generate XLS, when it next runs it will generate XLSX. Workaround: Click Rerun on a completed report.

#22396 - If email notifications are configured for specific transfer paths on a user’s Preferences > Email Notifications page, these settings are not honored when the user clicks the Rerun link on the Activity page on a transfer that started before Console was upgraded.

#22303 - Scheduled smart transfers that were created before upgrading from a version prior to 2.0.2 continue to use the old behavior, displaying dates/times using the timezone of the transfer requester, rather than trying to look up the recipient's time zone.

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.