Browse the manual

Introduction
- System requirements
- Licensing
- CLC Genomics Server
Installation
- Quick installation guide
- Installing and running the Server
  - Installing the Server software
- Installation modes - console and silent
- Upgrading an existing installation
  - Upgrading between major versions
- Allowing access through your firewall
- Downloading a license
  - Download a static license on a non-networked machine
- Starting and stopping the server
Basic configuration
- Logging into the administrative interface
- Server display name
- Adding locations for saving data
- Changing the listening port
- SSL and encryption
- Changing the tmp directory
  - Job node setup
- Setting the amount of memory available for the JVM
- Limiting the number of cpus available for use
- HTTP settings
- External network connections
- Proxy settings
Searching the web client
Managing users and groups
- Changing the root password
- User authentication for the CLC Server
Access privileges and permissions
- Controlling group access to CLC Server data
  - Setting permissions on folders
  - Technical notes about permissions and security
- Controlling access to the server, server tasks and external data
Job processing
- Introduction to servers setups
- Model I: Master server with dedicated job nodes
- Model II: Master server submitting to grid nodes
- Model III: Single Server setup
- Workflow settings
Working with external data locations
- Import/export directories
- Direct data transfer from client systems
- AWS Connections in the CLC Server
- AWS S3 public buckets
- Browse AWS S3 locations
- Illumina BaseSpace
Working with CLC Server File System Locations
- Browsing CLC Server File System Locations
- Searching CLC Server File System Locations
Workflows
- Installing and configuring workflows
- Executing workflows
- Updating workflows
- Reference data in server workflows
BLAST databases
Status and management
- Downloading a license via the web interface
- Server maintenance
- User statistics
- System statistics
Queue
Audit log
Server plugins
External applications
- External application configurations
  - Configuring the containerized execution environment
- Configuring external applications
- Using consistent reference data in external applications
- Import and export of external application configurations
- Updating external application configurations
- Example: Velvet (standard external application)
- Example: Bowtie (standard external application)
- Example: Kraken2 (containerized external application)
  - Extending the Kraken2 external application for paired data
- Example: MAFFT (containerized external application)
- External applications in workflows
- Running external applications
  - Using a CLC Workbench to launch external applications
  - Using CLC Server Command Line Tools to launch external applications
- Troubleshooting external applications
CLC Genomics Cloud Access
Recycle bins
- Automatic cleanup of recycle bins
- Emptying and restoring data from recycle bins
- Recycle bin restrictions
Configuring CLC Workbench connections
Troubleshooting
- Check setup
- Bug reporting
Command line tools
Analysis automation
Appendix
- Use of multi-core computers
- Non-exclusive Algorithms
- DRMAA libraries
- Consumable Resources
- Server system communication diagrams
- Third party libraries
- Read Mapper Reference Caching
- Monitoring
Bibliography

File locations for job node set-ups

Job nodes write results directly to CLC Server File System Locations. Thus, the following is required for job nodes:

Job nodes must have access to the directories configured as CLC Server File System Locations.
The user running the CLC Server process on each job node must be the same as the user running the CLC Server process on the master node.

One relatively common problem is root squashing, which often needs to be disabled, because it prevents the servers from writing and accessing the files as the same user. Read more about this at https://nfs.sourceforge.net/#faq_b11.

Further details about job nodes is provided in Job processing.