Release Notes: IBM Virtual Catcher 2.4.5

Product Release: December 1, 2016

Release Notes Updated: December 14, 2016

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

NEW FEATURES

Product Installation

  • A bundle installer is now available for Virtual Catcher, containing the following:
    • Windows: Point-to-Point and CargoD as a service
    • Linux: Aspera Common Components, Point-to-Point, and CargoD as a service

Dashboard and Configuration

  • New enhancements have been added to the Virtual Catcher Assets Status dashboard:
    • Filter settings for filtering the dashboard view according the following parameters:
      • File status
      • Provider ID
      • Asset ID or name
      • A range "from" and "to" dates that a package is received
    • A UI button for cleaning up dashboard records after a set period of time (older than 7 days, for example).
    • A UI button for downloading (exporting) all filtered statuses to a CSV file.
    • Milestones markers (dots) in the progress bar that indicate completion of the various stages in the workflow. This enables the user to see what the previous status of the asset was before it arrived the current state.
    • A new search box for searching by asset ID, asset name, ADI XML name, or folder name.
    • Word wrapping on ADI file and folder names, for improved readability.
  • Dashboard data (Virtual Catcher Assets Status) is removed after 90 days. The entries can be restored from avc_data_dump.yml.
  • For Aspera Copy and Local Copy transfers, there is now an option in the configuration dashboard to create a folder in the dropbox with a name matching the package asset ID for all transfers.
  • For Aspera Copy and Local Copy transfers, there is now an option in the configuration dashboard to rename the *.XML (or <xxxxx>.XML) file back to ADI.XML during a transfer.
  • A new option in the configuration, when set to true, directs the system to include the ADI.DTD file within a package; it copies the ADI.DTD files into staging, where it is delivered with the package to the CMS.
  • A new configuration setting allows users to set the number of days after which all files will be removed from the success and failure folders.
  • A redesigned configuration dashboard organizes parameter settings by delivery type and operational and notification function.

Workflows and Automation Processes

  • Three new preconfigured workflows are available on the Workflow Designs page:
    • Catcher_MDU
    • Find_MDUs_to_process
  • Virtual Catcher has added support for metadata updates to assets. All files with these updates will either contain an .MDU or .mdu extension, or _MDU or _mdu within the file name. While files are in their staging folder (before the workflow sends them to the CMS), .MDU and .mdu file extensions are changed to .XML.
  • When a package is received by the Local Copy delivery mode, it creates a target transfer folder called deliveryLocalDirectory if it doesn't already exist.
  • In the Catcher and Catcher_MDU workflows, when parsing ADI for validation, Virtual Catcher now extracts information from the Package class of ADI, rather than from the Title class. This extracted data appears on the Virtual Catcher Assets Status page (Dashboard > Asset Ingest Status), in the Asset Name column.

Other Changes

  • [Windows] force_upgrade_avc.txt is now a valid file for triggering an upgrade of Virtual Catcher.

ISSUES FIXED IN THIS RELEASE

ORC-1010 - The notification workflow for thePlatform not functioning properly.

ORC-984 - Aspera Copy delivery mode fails with an error at the step Check Aspera (Filter).

ORC-955 - FTP folder creation fails if the remote FTP server is Filezilla.

ORC-948 - Folders that are moved to the success directory have characters missing in the folder name; this is only an issue when the staging and success folders do not have same number of characters.

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.

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

PACKAGE INFORMATION

Linux 64-bit (rpm): aspera-orchestrator-vc-2.4.5.136233-0.x86_64.rpm
md5: 40d5cf7fe0f5d178e2fcf7947209e2f5
sha1: a9b5d75c46329f7090e76533284356ce7a9f894e
Linux64-bit(rpm)-inc.Bundle: aspera-orchestrator-vc-bundle-2.4.5.136233-linux-64.tar
md5: 0d8a4fd402cc53913f135f50d9ec46d9
sha1: ead8570c2a932d015ef9ddc6459a4efb3e0e4a5d
Windows: AsperaOrchestrator-VC-Setup-2.4.5.136233-x86.exe
md5: af23e21dfe7555df619403a97fbb9ab1
sha1: 271fc4b79f537e608b0cede54fbb58e80f3b6127
Windows-inc.Bundle: AsperaOrchestrator-VC-Bundle-Setup-2.4.5.136233-x86.exe
md5: 2ad17357ef2124bb14a1ee949e053309
sha1: 380478c7785b08df6742768789e0405887abd00b

KNOWN ISSUES

ORC-1006 - [Windows] In the dashboard, setting a ProviderID that contains more than 200 characters causes an error.

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