The Tetra Metrohm OMNIS Connector is a standalone, containerized application that integrates Metrohm OMNIS laboratory systems with the Tetra Data Platform (TDP). The Connector receives analysis results pushed from OMNIS by using a webhook and uploads them to the TDP with full metadata. A background loop automatically detects and retries failed uploads by querying the OMNIS Integration API.

This page describes the Connector's ingestion and retry architecture, the Tetra Hub and Standalone deployment options it supports, and where to find the version-specific User Guides for installation, configuration, and OMNIS Operating Procedure setup instructions.

Design Overview

Architecture

The Tetra Metrohm OMNIS Connector uses a webhook-based ingestion model:

1. Webhook Ingestion: Metrohm OMNIS sends analysis results to the Connector by using the CALL WEB API command in an Operating Procedure. The Connector exposes a local HTTP endpoint that accepts the JSON payloads.

2. TDP Upload: The Connector uploads the data to the TDP with associated metadata. Upload status and history are visible in the TDP connector files panel.

3. Automatic Retry: OMNIS does not retry a failed CALL WEB API call. When OMNIS credentials are configured, a background loop recovers these uploads: it periodically queries the OMNIS Integration API for runs whose upload failed, then re-fetches the data and re-uploads it to TDP with exponential backoff. Items that cannot be recovered move to a dead-letter queue (DLQ).

   For more information, see the Tetra Metrohm OMNIS Connector User Guide (v1.0.x).

Deployment Options

The Connector supports the following deployment options:

• Tetra Hub: A software component that runs within your network and facilitates secure data transfer between the TDP and the Connector. For more information, see the Tetra Hub documentation.
• Standalone deployment: Runs Connectors on-premises by using a Docker container image and installation script. This option allows customers to install the Connector on any host server that can run Docker containers. For more information, see the Standalone Connector Installation and Upgrade Guide in the TetraConnect Hub. For access, see Access the TetraConnect Hub.

For more information about deployment options, see Connector Deployment Options. To learn about TDP networking best practices, see Recommended Architectures for Network Connectivity to Private Cloud and On-Premises Components in the TetraConnect Hub.

User Guides

For more information about how to install, configure, and use the Tetra Metrohm OMNIS Connector, see the latest user guide:

• Tetra Metrohm OMNIS Connector User Guide (v1.0.x)

Documentation Feedback

Do you have questions about our documentation or suggestions for how we can improve it? Start a discussion in TetraConnect Hub. For access, see Access the TetraConnect Hub.

📘

NOTE

Feedback isn't part of the official TetraScience product documentation. TetraScience doesn't warrant or make any guarantees about the feedback provided, including its accuracy, relevance, or reliability. All feedback is subject to the terms set forth in the TetraConnect Hub Community Guidelines.