• Product manuals

Browse the manual

• Introduction
  • Deployment strategies
  • Java
  • System requirements
• Installation of Workbenches
  • Getting Workbench installers
  • What a Workbench installer does when launched
  • Installation modes - console and silent
  • Uninstalling a Workbench
• Licenses
  • Connecting to a CLC Network License Manager from Workbenches
• Workbench plugins
• Workflows
• Connecting to a CLC Server
• Security policies
• Storing and backing up data
  • Default Workbench data storage
  • Temporary data
  • Backup of Workbench information
  • Disk space requirements
• System resources
  • Setting the amount of memory available for the JVM
  • Setting the number of cores to use
• Overview - where do we put things?
  • Per-computer Workbench information
  • Per-user Workbench information
  • Per CLC Data Location information

What a Workbench installer does when launched

When a Workbench installer is run, it performs the following tasks:

1. Extracts and copies files to the installation directory The Workbench software is installed into a directory. It is self contained. The suggested folder name to install into reflects the software name and the major version line. For example, for a CLC Genomics Workbench with major version 25, the default installation location offered on each platform would be:

   Windows

   C:\Program files\CLC Genomics Workbench 25

   macOS

   /Applications/CLC Genomics Workbench 25

   Linux

   /opt/CLCGenomicsWorkbench 25

   To install the software into central locations, like those listed above, generally requires administrator rights. Administrator rights will also be needed to install licenses and plugins for installations in central locations. The software can be installed to another location, if desired. When only a single person will use the software, this can be useful. Installing to an area they have permission to write to means that licenses and plugins can then be installed without needing administrator rights.

   General recommendations for installation locations

   • For minor updates, you will be asked whether you wish to:
     • Update the existing installation Generally recommended for minor updates. New files will be installed into the same directory as the existing installation. Licensing information and installed plugins remain in place from the installation already present.

       OR

     • Install to a different directory. Configuration will be needed after installation. E.g. licensing needs to be configured, any desired plugins will need to be installed, etc.

   • For major updates. The suggested installation directory will reflect the new major version number of the software. Please do not install a new major version into the same folder as an existing, older version of the Workbench. Configuration will be needed after installation. E.g. licensing needs to be configured, any desired plugins will need to be installed, etc.

2. Sets the amount of memory The installer investigates the amount of RAM on the machine during installation and sets the amount of memory that the Workbench can use.

3. Establishes shortcuts (optional) On Windows and Mac systems, an option is provided during installation to create a shortcut for starting the Workbench. On Linux systems, this option is also presented, but it has no effect.

On Macs without Rosetta present on the system, the option of installing it is offered during the installation process. Rosetta enables Intel-based features to run on Apple Silicon Macs. While not needed for the majority of tools, some require it, for example De Novo Assembly, BLAST, Sample Reads and tools for analyzing small RNA.

Read more about memory settings in Setting the amount of memory available for the JVM.

---