The Illumina MiSeqDx Integration Package v1.10.0 supports MiSeqDx instruments running in Diagnostic mode. For MiSeqDx instruments running in Research mode, install the MiSeq Integration Package. For more information, refer to MiSeq Integration v8.2.0 Installation.
Compatibility
MiSeqDx Integration v1.10.0 is compatible with the following software:
Clarity LIMS v6.2 and later
Secret Util v1.0 and later
IPP v2.6 and later
Prerequisites
MiSeqDx Integration v1.10.0 has the following prerequisites:
Mount run data network-attached storage (NAS) share
IPP is installed
Prerequisite 1: Mount Run Data NAS Share
Mounting the NAS share of run data are needed to capture and generate files associated with the sequencing run. To mount NAS shares that contain data from the Clarity LIMS server, use Read/Write privileges as the glsjboss user. The following data can be mounted to the NAS share:
Run data (e.g., \\network-storage\run_data)
Clarity LIMS-created events triggered by the End Run event of the Illumina sequencing run (e.g., \\network-storage\illumina\gls_events)
With Read access, the Clarity LIMS server reads the following information in individual sequencing run data folders:
MiSeqDx Integration Package v1.10.0 depends on the QC Protocols configuration provided in IPP (v2.6 and later) for Clarity LIMS v6.2 and later.
If the base configuration is not installed, then install it on the Clarity LIMS server that is being used for the MiSeqDx integration. For details on IPP v2.6 installation and configuration, refer to the Illumina Preset Protocols documentation.
If you are upgrading the base configuration, make sure that the IPP package is compatible with the version of Clarity LIMS you are installing (in this case, IPP v2.6 for Clarity LIMS v6.2).
If you do not have QC Protocols, then install them as follows.
As a glsjboss user, run the following command to view the complete list of IPP workflows:
/opt/gls/clarity/config/illumina-preset-protocols-installer.sh -o list
To install the dependent QC Protocols, run the following command:
MiSeqDx Integration v1.10.0 supports both on-premise and cloud integrations. This integration is distributed as the following RPM packages:
BaseSpaceLIMS-miseqdx-extensions
BaseSpaceLIMS-miseqdx-sequencing-service
The BaseSpaceLIMS-miseqdx-extensions RPM installs the following items:
Protocols and workflows
Database properties that configure the service
Placement pattern files that determine reagent index assignment
miseqdx-extensions.jar
miseqdx-sequencing-report.jar
The BaseSpaceLIMS-miseqdx-sequencing-service RPM installs the following items:
If not found, user configuration (the glsjboss user and the glsjdk8 and claritylims user groups)
If not installed, Java 8
Bash scripts to run the miseqdx_seqservice
miseqdx-sequencing.jar
The gls_events_mos_rta.bat batch file that configures RTA
Smoke test directories
On-Premise Installation
Use the following instructions to install the BaseSpaceLIMS-miseqdx-extensions and BaseSpaceLIMS-miseqdx-sequencing-service RPMs on the Clarity LIMS server.
Install the RPMs
On the Clarity LIMS server, log in as the root user.
Run the following yum commands to install the RPMs:
When prompted by the RPM instructions to configure the sequencing service (which includes database properties with default values set for the integration), run the following command as the glsjboss user:
For more information on the properties that must be configured, refer to Installed Components.
Start the Sequencing Service
Run the following command to start the sequencing service:
systemctl start miseq_seqservice-v8
Cloud Installation
The BaseSpaceLIMS-miseqdx-extensions RPM must be installed on the Clarity LIMS server. The BaseSpaceLIMS-miseqdx-sequencing-service RPM can be installed remotely on another server within the network.
Specifications
The following hardware, operating system, and network specifications must be met to install the BaseSpaceLIMS-miseqdx-sequencing-service RPM:
Hardware requirements:
64-bit processor (dual core 2.0 GHz)
OS requirements, plus at least an additional 512 MB RAM
When prompted by the RPM instructions to configure the sequencing service (which includes database properties with default values set for the integration), run the following command as the glsjboss user:
The instrument software is divided into the following modules:
MiSeqDx Operating Software (MOS) — Controls the instrument operation, including various configuration settings. This software is installed and runs on the instrument.
MiSeqDx Reporting Software (MRS) — Performs the following secondary analysis functions:
Demultiplexing
Alignment
Variant calling
Report generation
The specific functions that are supported vary by the kit. This software is installed on or off the instrument.
Real-Time Analysis (RTA) — Performs image processing and base calling (primary analysis). The software makes sure that data files are created and copied to the final destination folder and is installed and runs on the instrument.
Illumina User Management (IUM) — Contains a user database file that is used with the MiSeqDx instrument. This file controls user passwords and privileges for MOS.
For more information on the MiSeqDx software, refer to the MiSeqDx documentation at support.illumina.com.
Instrument Integration
Illumina provides a supported mechanism for using custom scripts on key events during a sequencing run. The Clarity LIMS support team has created batch files that plugs into these events. When the batch file is used, it reads the event information and writes it in a TXT event file at the same network share location that the instrument uses to write the run data. Another process running on the server where the sequencing service RPM is installed receives the event files and takes the appropriate actions.
The sequencing service monitors the following events (the actual event names may be different):
End Run — This event is used to update the sequencing steps in Clarity LIMS, captures key process data and files, and parses run statistics for output custom fields.
Begin Secondary Analysis — Indicates that secondary analysis in the MRS has started so that the sequencing service can start to monitor for results. After secondary analysis is complete, the VCF files are uploaded to Clarity LIMS.
Configure Batch Files
When the instrument is running, the final destination for the run data are a network storage path. The software is configured with a network storage path root (e.g., \\network-storage\illumina). Each sequencing run generates a unique run ID, which is appended to create a unique data run directory (e.g., \\network-storage\illumina\110419_InstrumentName_0001_ARG1234567).
The Clarity LIMS batch files must be configured to write to a directory within the network storage path root. This directory is typically named gls_events, but the directory name can be different as long as no spaces are used.
To avoid inadvertently removing or overwriting the batch file when updating the instrument software, the batch file can be placed in its own directory on the instrument computer.
Before configuring the batch files, do the following:
Back up the MiSeq.Configuration.xml configuration file to
C:\Illumina\RTA\Configs\
Make sure that the instrument is idle.
Shut down MOS.
Set up the directory structure as follows.
Create a directory (C:\Illumina\gls is recommended) on the local PC to hold the batch file.
Create a directory (e.g., gls_events) on the NAS to hold the event files.
Configure the batch file as follows
Determine the site or instrument specific network storage path root.
Change the DESTINATION_PATH line to use the storage path root and the name of the event file directory.
set DESTINATION_PATH=\\network-storage\illumina\gls_events\
Copy the DESTINATION_PATH and paste it into the Windows Explorer address bar.
Make sure that the network location is accessible and that it opens from the instrument.
Deploy the batch file as follows
On the server where the sequencing service RPM is installed, copy the batch file from /opt/gls/clarity/extensions/miseqdx/InstrumentIntegrations to C:\Illumina\gls on the local computer.
If necessary, create the gls_events_mos_rta.bat batch file in C:\Illumina\gls. For more information, contact Illumina Support.
From the command prompt, list the contents on the C:\Illumina\gls directory using the following command:
dir C:\Illumina\gls\
Make sure that the name of the batch file you created does not contain any special (hidden) characters.
Configure RTA
Update the MOS configuration files as follows.
Turn off the instrument and restart the instrument computer.
Using Task Manager, make sure that MOS is not auto-launched by Windows.
[Optional] If MOS is auto-launched, remove it from the auto-launch list and restart the computer.
Edit the file to connect to the RTA End Run event as follows.
Open the MiSeq.Configuration.xml file at
C:\Illumina\RTA\Configs\
Update the following content within the <RTAConfiguration> tags:
If the validation is successful, the following message displays:
Error: No run info file found in input directory .\RunInfo.xml
If the configuration files contain an error, the command returns specifics about the problem. The following example shows an error that occurs when a <GLS> key is added to the file at line 83:
Error: While loading Configuration "c:\illumina\rta\configs\MiSeq.Configuration.xml"
There is an error in XML document <83, 5>
Error loading xml file: Unknown node 'GLS' at line 83 pos 5
Start MOS.
Open the MiSeq.Configuration.xml file and make sure that the changes were saved.
The instrument sequencing run test validates that the Clarity LIMS batch file is connected properly and invoked on the instrument events. Before validating the batch file, make sure that you have the following prerequisites are met:
You have access to the NAS share.
The default configuration has been successfully imported.
Manual invocation of the event files has been validated. This validation checks for the following information:
The DESTINATION_PATH is configured correctly.
The instrument computer can access and write to the DESTINATION_PATH.
There are no syntax errors in the Clarity LIMS batch file.
The sequencing service processes and archives event files, which can cause validation issues while the service is running. You can make the following changes to avoid losing the event files that you are attempting to validate:
Modify the FINAL_EXTENSION value in the Clarity LIMS batch file so that the file extension is .test instead of .txt. The service only processes and archives TXT files. Make sure that you change FINAL_EXTENSION back to .txt after manual validation.
Monitor the MiSeqDxIntegrator.log file, which logs the file name and contents of each event file that is processed.
Validate the sequencing run as follows
During the run, monitor the contents of the gls_events directory.
After the run is completed and the RTA completes primary analysis, make sure that a final EndRun event displays (e.g., event-EndRun-11043279.txt).
If you are upgrading from an earlier version of the MiSeqDx integration package and the system is configured with the configure_extensions_miseqdx_workflow.sh and configure_extensions_miseqdx_sequencingservice.sh scripts, refer to Installed Components.
If you are upgrading from an earlier version of the MiSeqDx integration package and the system is configured with the configure_extensions_miseqdx_workflow.sh and configure_extensions_miseqdx_sequencingservice.sh scripts, refer to Installed Components.
For Windows 10, the folder must be under C:\Illumina instead of C:\Illumina\gls because of Windows software restriction policies. If the folder is not in that directory, the batch script does not run. For versions before Windows 10, C:\Illumina\gls is acceptable.
Make sure to include the trailing \ in the DESTINATION_PATH line. Refer to the following example:
