We are very pleased to announce the general release of Aspera Console 3.0 for Linux and Windows available for download. Console 3.0 is a major advancement with a new internal architecture and many new features. Many important details on this release and how to take maximum advantage of its new capabilities are outlined below for you to get the most value from this release.
Console 3.0 New Architecture
The new Console 3.0 architecture offers many advantages for scalability and robustness due to a new approach that queries transfer reporting data from managed nodes using the Aspera node API, rather than pushing data to the Console via the asperacentral service as in the previous Console 2 generation. Key benefits include:
- Query Efficiency - The managed nodes store transfer reporting data locally, and Console retrieves this data in batches via the API, reducing the number of network round trips to get data.
- Timely Reporting under High Load - Updates to transfer status are not held up by file records waiting to enter the database, and session and file timestamps will no longer fall behind due to a reporting backlog
- Maintenance - Console can be taken down for maintenance without losing information about transfer activity and will catch up reporting when brought back online.
- Flexibility - Managed nodes can be monitored by multiple Consoles instead of logging to only one Console database.
- Security and Robustness - SSH tunnels are no longer required for secure management of logging data since all data is queried by Console (and is secured through SSL).
How to Take Advantage of the New Architecture
Console 2.X can be seamlessly upgraded to Console 3.0. However, upgrading alone is not enough to take full advantage of the new architecture! In order to take advantage of the new query architecture, managed node software (Enterprise Server, Point-to-Point, Connect Server, etc.) must be upgraded to at least version 3.4.6 and ideally to the latest version, 3.5.5. Furthermore these nodes must be converted to use the node API using the built-in ‘Convert’ option in the Console 3.0 Node edit screens. If a node is NOT converted to use the node API it will continue to report to Console using the existing mechanism. When you convert a node to use the node API you will also need to set the ACL feature on the node for full security. Console will prompt you to do this and the Console 3.0 documentation provides easy instructions on how to do this.
- Managed nodes added to a Console version prior to 3.0 still continue to report to Console 3.0 using asperacentral to “push” to Console. They are annotated as “Legacy Nodes” in the nodes list.
- These existing managed nodes running Enterprise Server or Point-to-Point version 3.4.6 or higher can be converted to use the new Aspera node API with the 'Convert' to use node poller option in the Node edit screens. If converted, these nodes will be queried by Console using the new node API method.
- This means you will want to upgrade your nodes to at least version 3.4.6 and ideally to the latest version 3.5.5 in order to take advantage of the scalability this new Console architecture offers.
Key New Features in Console 3.0
The Aspera team has worked hard to bring you over thirty new and significant features to Console 3.0, which are covered in detail in the product Release Notes. The most asked-for highlights include the following:
- Dramatically expanded email notification with new options to define rulesets to send transfer start, success, and failure notifications based on address, file paths, users, and transfer tags.
- Ability to add unmanaged nodes with domain names in addition to IP addresses.
- New node cluster groups for Console smart transfers with built-in options for load balancing and fail over.
- Expanded reports including support for transfer session tags set by Faspex SAML sign on and other Aspera APIs, new fields for transfer paths, Faspex metadata and transfer users, and new report templates for activity summary by contact, bandwidth peak usage per node per day, billing summary by month and contact, Faspex activity summary by day.
- Enhanced Smart Transfers including full support for automating transfer with ascp4, the new ultra-fast binary, including initiation, dynamic pause/resume and bandwidth control and reporting.
- New options to archive files after transfer, exclude newer-than options, preserve UID and GID, and other advanced options, and ability for admins to edit each other’s transfer templates.
- Support for naming and sorting Smart Transfers by descriptive tags in the Console display.
- Expanded live Search on transfer history including search on file name, tags, session ID, SSH user, source/destination path, and node address.
- Many new features to view raw session details and statistics.
- New account options for users to reset forgotten passwords, change their passwords, and control password complexity.
- New active console database space monitoring and warning.
How To Upgrade
Console 3.0 is available for download, and details on how to upgrade to are available in the Console administrator’s guide online. Aspera support stands by ready to help you as needed with upgrades. If you have any questions or would like upgrade assistance, please contact firstname.lastname@example.org.