Clarity LIMS
Illumina Connected Software
Clarity LIMS v6.3 & Lablink v2.5
Clarity LIMS v6.3 & Lablink v2.5
  • Release Notes Clarity LIMS v6.3
    • Release Notes Clarity LIMS v6.3.1
    • Release Notes Clarity LIMS v6.3.0
  • Technical Overview
    • Technical Requirements
  • Installation
    • Installation Procedure
    • Guide to Secret Management
    • Install/Upgrade Secret Management for Integration Modules
    • Change the Clarity LIMS Hostname
    • Update Server Passwords and Database Connection Details
  • On-Premise Deployments
    • Pre-installation Requirements
      • Install a Purchased SSL/TLS Certificate
      • Configure Your HashiCorp Vault
    • On Premise to On Premise Upgrade Procedures
    • On Premise to On Premise In-place Upgrade Procedures
    • On Premise to Hosted Upgrade Procedures
    • Hosted to On Premise Upgrade Procedures
  • Administration
    • Database Cleanup Procedure
    • Backup and Restore Procedure
    • Receiving and Decrypting Cloud Backup Data
    • LDAP Integration
      • Using the LDAP Checker Tool
    • Illumina Connected Software Platform Integration
    • Clarity LIMS Log Files
    • Customize the Term Used for Projects
    • Enforcing Unique Sample Names Within a Project
    • Container Name Uniqueness
    • Configure Electronic Signatures
    • Creating Enrypted Passwords
    • Config Slicer Tool
      • Managing Configurations with Config Slicer
      • Upgrading a configuration package/manifest file for compatibility with Config Slicer v3.0.x
      • Config Slicer Use Cases
      • Troubleshooting Config Slicer
    • Audit Trail
      • Enabling, Validating and Disabling Audit Trail
    • System Settings
    • Automation Worker Nodes
      • Troubleshooting Automation Worker
  • Clarity LIMS v6.3 Reference Guide
    • Dashboards
      • Overview Dashboard
      • Projects Dashboard
    • Projects and Samples
      • Projects
      • Samples Accessioning
        • Sample List for Batch Import
        • Guidelines and Tips for Batch Sample Import
      • Assign and Process Samples
    • Lab View
      • Requeue and Rework Samples
      • Storing Sample Aliquots for Later Use
      • Modifying Completed Step Details
      • Alert Notifications
    • Configuration
      • Lab Work
        • Steps and Master Steps
          • Step Milestones
          • Derived Sample Naming Convention Tokens
        • Protocols
        • Workflows
      • Consumables
        • Reagents
          • Reagent Kit Lot Manifest for Batch Import
        • Controls
        • Instruments
        • Labels
        • Containers
      • Custom Fields
      • User Management
        • Manage User Access
        • User Roles
        • Configured Role-Based Permissions
        • User and Profile Page
      • Automations
        • Automation Trigger Configuration
        • Copy Custom Fields from Step Input to Output
        • Template Files Associated With Automations
    • Automated Quality Control
      • Configure a QC System
    • Search
      • Basic Search
      • Advanced Search
    • Genealogy View
    • System Performance
      • Queue Performance and Usability
      • Demultiplexing API Endpoint Performance
    • Terms and Definitions
  • LabLink v2.5 Reference Guide
    • Project
      • Email Notifications for Notes
    • Resource Materials & Contact Us
    • Users
    • Configuration
    • Publishing Files and Progress
Powered by GitBook
On this page
  • Production Server Requirements
  • Server Operating System Requirements
  • Database Requirements
  • Web Client Requirements
  • Automation Worker Requirements

Was this helpful?

Export as PDF
  1. Technical Overview

Technical Requirements

The following information is a summary of the technical requirements for an on-premise or based deployment of Clarity LIMS v6 and later. To install and use Clarity LIMS, the client and server systems must meet these requirements. Clarity LIMS is designed to run on standard commodity hardware. The requirements provide general guidelines for your hardware configuration. You can obtain specific configuration quotes from the hardware vendor of your choice.

Before installing Clarity LIMS, you must also organize, install, and/or configure some essential components. For details on these components and installation and configuration instructions, refer to the Pre-installation Requirements

Allow enough time for the procurement of your hardware and software. Make sure that all components are installed and configured before proceeding with the installation of Clarity LIMS.

Production Server Requirements

For on-premise deployments, Clarity LIMS has two levels of recommended hardware. For larger labs in full production, we strongly suggest the high-throughput requirements.

The production server must be configured in US locale.

Recommended

  • Server class 64-bit CPU with at least eight cores at 2.9 GHz

  • 20 MB shared cache (L3) memory

  • 32 GB RAM

    • 6 GB allocated to Tomcat

    • 6 GB allocated to the database

    • 2 GB allocated to ElasticSearch

  • 100 GB hard disk drive space for the operating system, application, and log storage

  • 1 Gbps Ethernet network or faster

High-throughput:

  • Server class 64-bit CPU with at least 16 cores at 2.9 GHz

  • 20 MB shared cache (L3) memory

  • 64 GB RAM

    • 12 GB allocated to Tomcat

    • 12 GB allocated to the database

    • 4 GB allocated to ElasticSearch

  • 100 GB hard disk drive space for the operating system, application, and log storage

  • 1 Gbps Ethernet network or faster

  • Memory requirements must be discussed at the beginning of the project, before ordering hardware.

  • The amount of hard disk drive space required is contingent on the frequency and amount of data generated in your lab. We recommend that you take inventory of all instruments that will be used with Clarity LIMS and calculate the amount of data generated for each of them.

  • To make sure that your data are protected, we recommend that your Clarity LIMS server contain redundant storage and that you perform regular backups.

  • For robust network performance, make sure that there are no bottlenecks lower than 100 Mbps on any connected network devices (routers, firewalls, switches). This is especially important when handling the large amounts of data produced by certain instruments.

  • The physical hardware specifications described are also valid for Virtual Machine (VM) environments. If you have questions about your VM architecture, contact Illumina Support.

For hosted deployments, Illumina sizes the system accordingly for system load. We reserve the right to archive auditing information to maintain system performance as the data set grows.

If your subscription is not renewed for your hosted deployment, at your request, we will supply you with an export of all user data. In practice, we will provide a database dump and details on the database schema for you to pull out any data you need going forward.

Server Operating System Requirements

For on-premise deployments, Clarity LIMS has been qualified to run with the following server operating systems versions:

  • RedHat Enterprise Linux v8.10 (64-bit)

  • Oracle Linux v8.10 (64-bit)

SELinux is not supported and must be set to either permissive or disabled mode.

For hosted deployments, Illumina uses the latest qualified Oracle Linux version.

Database Requirements

For on-premise deployments, Clarity LIMS has been qualified to run with PostgreSQL 15.7.

For hosted deployments, Illumina uses the latest qualified PostgreSQL version.

Web Client Requirements

The following client requirements apply to both on-premise and hosted deployments.

Hardware

  • 64-bit processor (dual-core 3.0 GHz)

  • 8 GB RAM

Operating Systems

  • Windows (10 or later)

Microsoft Surface Pro support is for all operations only when a mouse is used. Touch screen support is for read-only lab work. Running samples through steps is not supported.

  • Linux (restricted to the server-supported versions listed previously)

  • Macintosh OS (13 Venture or later)

  • iOS (17 or later) on iPad running Safari browser

iPad support is for read-only lab work. Running samples through steps is not supported.

Web Browsers

  • Google Chrome (latest update)

  • Mozilla Firefox (latest update)

  • Apple Safari on iPad only (latest update)

Other Requirements

  • 1280 x 800 or higher

  • Cookies and JavaScript must be enabled

For both on-premise and hosted deployments, a 20 Mbs network connection speed from client to server is required. If remote access via VPN is needed for LDAP or instrument integrations, we recommend 100 Mb/s network connection speed between your site and the hosted instance.

Automation Worker Requirements

The following requirements apply to automation workers installed on premise, for both on premise deployments and hosted deployments, to support instrument integrations.

Hardware

  • 64-bit processor

  • 2 Gb RAM

  • Hard disk drive space equivalent to twice the size of the largest file you are planning to transfer

Operating Systems

  • Windows 10 (or Windows Server 2016/2022)

  • RedHat Enterprise Linux v8.10

  • Oracle Linux v8.10

Applications

  • Linux – Illumina installs Java Open JDK 8.0 update 362 (1.8.0_362)

  • Windows – Clients must install Java Open JDK 8.0 update 362 (1.8.0_292)

PreviousTechnical OverviewNextInstallation

Last updated 6 months ago

Was this helpful?