• 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

Workbench plugins

Plugins extend the functionality of CLC Workbenches and the CLC Genomics Server. Workbench plugins distributed by QIAGEN Aarhus can be downloaded via the Workbench Plugin Manager if the Workbench can connect to the external network. Alternatively, plugin files can be downloaded on a machine with external network access from https://digitalinsights.qiagen.com/products-overview/plugins/, and then copied to the machine with the Workbench and installed using the Install from File button at the bottom of the Plugin Manager (figure 4.1).

When a plugin is installed, it is put into a folder called plugins within the installation area of a Workbench. For a single Workbench, one would typically use the graphical Workbench Plugin Manager for installing plugins and modules. However, when administering a large number of Workbenches, it can be more efficient to:

• Install the desired plugins and modules on a single Workbench using the Workbench Plugin Manager.
• Copy the plugins folder and its contents from that Workbench's installation area to the same relative location on other machines running the same Workbench version.

Figure 4.1: The Plugin Manager.

Tools delivered as part of a module, i.e. a commercial Workbench plugin, require a module license to be available. Please see Licenses for more on licensing.

---