Installing Aspera Orchestrator with Virtual Catcher Workflows
With IBM announcing the end of support for Aspera Virtual Catcher (AVC), many long-time users and customers of the product may be wondering what options they have for their AVC workflows. Fortunately for the Aspera customer base, there is a long-term solution and PacGenesis has built the tech to make the transition easy.
Aspera Virtual Catcher is technically a stripped-down version of Aspera Orchestrator with predefined workflows. However, migrating from AVC to Aspera Orchestrator has never been as simple as clicking a button or running a single command, until now.
The technical team at PacGenesis has automated the installation and configuration of Aspera Orchestrator with AVC workflows, making the migration off of AVC to Orchestrator quick and easy. The process consists of just a few easy steps:
- Run PacGenesis proprietary automation utility
chmod a+x install_avc
- Copy in your Aspera Orchestrator License
cp orchestrator-xxx.aspera-license /opt/aspera/var/config/orchestrator/license
- Configure Aspera Cargo for your particular use case
These simple steps will have you up and running in minutes with a fully functional Aspera Orchestrator install configured for your AVC workflows. If you’re still using Aspera Virtual Catcher unsupported, please reach out to firstname.lastname@example.org to discuss licensing requirements and to get access to our proprietary automation utility.
To learn more about PacGenesis, follow @PacGenesis on Facebook, Twitter, and LinkedIn, or visit us at pacgenesis.com.