Release Notes: IBM Aspera Orchestrator 2.7.0

Product Release: February 3, 2017

Release Notes Updated: February 3, 2017

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

NEW FEATURES

Journals
  • The journal portlet feature can now be configured inline (by right-clicking a step in the workflow).
  • On the Journals screen (Work Orders > Journals), the workflow name (ID) and the package name are now displayed.
API
  • A new API call lists all queues in Orchestrator for which the user has permissions.
  • A new API method allows the user to reset a work order from a particular work step.
Plugins
  • The array fan-out plugin supports restart of a failed step during execution of a loop.
  • New plugins: Quasar File QC
  • The FaspControl plugin has a new option, Adjust Rate, for adjusting the target rate of an ongoing session.. The user enters the rate (in kbps) and has the option to share this value across all sessions found.
General
  • Improvements to the engine avoid the use of database transactions in order to improve performance.
  • The engine heartbeat is now handled in such a way that a higher number of work orders does not cause a high value for the heartbeat.
  • Additional parameters added to the database.yml file cause database queries to perform faster. The following are two of these new parameters, with their default values:
    • wait_timeout: 1
    • pool: 10
  • The Work Orders pages in the UI contain enhancements to load pages faster and more effectively.
  • The mechanism for work orders to be destroyed has been improved to avoid potential deadlocks with multiple resources during cleanup.
  • Idle synchronous workers poll asynchronous tasks.
  • Synchronous and asynchronous plugins are identified in workflow actions.
  • The parameter configuration now supports a new type, Password. This new type is also available in Custom Ruby and other plugins.
  • On the Help page, an updated links allow user to view the admin and user guides directly from the Aspera website. There is also a clickable link for download of a PDF of these guides.
  • Remote node editing permission has been added, so only admins who create the remote node can see the Edit Node button, and thus have the ability to edit the users and passwords.

Other Changes

  • For high availability installations, the Orchestrator database adaptor for MySQL does not break when the database increment level is something other than "1" (for example, non-sequential values).nh
  • [Windows] When upgrading Orchestrator, it is no longer necessary to uninstall the older version.
  • The UI method for importing a capsule has been streamlined; the user now clicks Engine > Capsules > Import capsule.
  • [Windows] The parameter max_worker_size is now set in KB.

ISSUES FIXED IN THIS RELEASE

ORC-1186 - Engine debug mode should provide user-friendly statistics for Engine loop and work order data.

ORC-1185 - The Work Orders page loads slowly, due to a high volume of data returned in the database query.

ORC-1184 - In the Orchestrator GUI, the Engine Processes page no longer displays the work step link being executed by a worker.

ORC-1080 - (Windows) Uninstall sometimes fails.

ORC-1079 - When a journal portlet is created with a new journal book other than miscellaneous, it does not recognized the value in the keywords field; also, the dynamic search (Dashboard > Journals) with keywords does not work.

ORC-1176 - Under Work Orders, when the user clicks Filter by, then clicks All, no workflows are displayed.

ORC-1053 - Orchestrator is vulnerable to denial-of-service attacks when used with Faspex. (CIM-260)

ORC-1046 - When an element within a fan-out loop fails, and this element is restarted with the Restart from this step (arrow icon) or the Reset button, other elements within the loop are restarted as well. This causes serious problems for other elements in the loop that are already complete and should not be restarted.

ORC-1043 - When the notification sub-workflow that is called for complete, fail, or error states is configured with the mandatory runtime parameter last_executed_steps, it fails. Even if that parameter is set to be optional, it gets a value of "[ ]" or "{ }" (empty) instead of the actual value.

ORC-1034 - Restarting a work order doesn't change the work order end time.

ORC-1033 - Importing a workflow with a dependency (for example, a sub-workflows), results in duplication of the step action templates referenced in each.

ORC-1026 - On a Chrome browser, on the WorkOrder Filters page, the Status and Workflows fields are sometimes not shown.

ORC-1025 - On relaunch of a work order, the tags associated with it are merged into a single string instead of a comma-separated string.

ORC-1023 - With the exception of miscellaneous journals, the order of displayed journals is reversed, with the latest at the end.

ORC-1022 - After an upgrade from an older version of Orchestrator, users can see their entries in the new Journals screens, but the status bar is empty.

ORC-1021 - When a non-admin user with access to the workflow screen tries to run a bulk restart from the work orders page, the action fails because permission check is for a work order, not a workflow.

ORC-1018 - Workflow names which include "< >" are not encoded properly; this occurs both on the workflows page and work order filters page.

ORC-1008 - A remote file watcher 2.0.2 returns the following error message when a folder in the watcher directory has a trailing space at the end of the folder name:
Error (Action status check failed: #<RuntimeError: Scanning errors:
{"directory_name"=>"(2) No such file or directory\000"} 

ORC-1007 - During an upgrade of Orchestrator to 2.6.1, images saved in the earlier installation (in /opt/aspera/var/config/orchestrator/images/) are not automatically pulled into the new installation and must be added manually.

ORC-991 - The ClamAV plugin is producing incorrect results.

ORC-990 - The Clear Queue feature is not working.

ORC-987 - In Managed Queues, the pausing a queue feature is not working.

ORC-982 - . On the work order filter screen, instead of the default behavior to display only the completed, errored and failed work orders from the previous day, all work orders are displaying.

ORC-973 - XML strings stored in parameters are altered by the system after save and publish.

ORC-932 - Mount Manager and Net Use Manager tables are missing present in Snapshot.

The Work Orders page displays sub-workflow details for the workflow that is displayed.

SYSTEM REQUIREMENTS

Windows 64-bit: 2008 R2, 2012, 2012 R2, 2016
Microsoft Visual C++ 2008 Redistributable Package 9.0 64-bit
Browsers: Microsoft Edge, Firefox 27–49, Google Chrome 40–49

Linux 64-bit: RHEL 6.0-6.7, 7.0-7.2; CentOS 6.0-6.7, 7.0-7 (1511), SLES 12
Aspera Common Components 1.4.0
Browsers: Firefox 27–49, Safari 6–9, and Google Chrome 40–49

PACKAGE INFORMATION

Linux 64-bit (rpm): aspera-orchestrator-2.7.0.138940-0.x86_64.rpm
md5: 1862dd3dfedabfe33b82c14df13dae57
sha1: c63e31f4f1e0dccbfaebd303db0ca7061418288c

KNOWN ISSUES

ORC-1187 - The Map to input values for the File parameter in the Journal Configuration dialog are not working. Only the Map to Output values currently work.

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