Tetra Agents
Tetra Agents provide built-in data integration with specific instruments or systems. They offer similar functionality as Tetra Connectors, but are Windows based and run exclusively on-premises. After the data is uploaded to the Tetra Data Platform (TDP), it can then be processed by a pipeline, translated into a Tetra Data model, and integrated with other systems.
For more information about the different types of Tetra Integrations, see Tetra Integrations. For additional best practices, see Data Integration and General Agents in the TetraConnect Hub. For access, see Access the TetraConnect Hub.
IMPORTANT
It's recommended that you set up separate Tetra Agent instances for test and production environments. For more information, see Best Practices for Setting Up Agents in Test and Production Environments .
Supported Tetra Agents
The TDP currently supports the following Agents. All Tetra Agents require additional third-party licenses and/or infrastructure.
For information about which Agent versions are eligible for patches and customer engineering support, see Tetra Integrations Support.
Agent | Source Type | Capabilities | Required Licenses and Infrastructure |
---|---|---|---|
Tetra Chromeleon Agent | Instruments | - Pulls data from Chromeleon and uploads it to the TDP | - Chromeleon account - Windows host machine See details |
Tetra Empower Agent | Instruments | - Pulls data from Waters Empower 3 and uploads it to the TDP | - Empower 3 or Service Release 2(SR2) account or higher - Windows host machine See details |
Tetra File-Log Agent | File sharing | - Monitors Windows file system folders for new and modified files and automatically uploads them to the TDP | - Windows host machine See details |
Tetra HTTP Relay Agent | Connectivity middleware | - Allows Tetra Data Pipelines and other TetraScience components to communicate with customers' on-premises systems, even when a customer's firewall blocks incoming network traffic from the TDP | - Linux host machine See details |
Tetra IoT Agent | File sharing | - Supports direct integrations with simple instruments, such as balances and pH meters, by using a hardware interface supplied by TetraScience | - IoT Agent Box (edge device) - Tetra IoT Layer See details |
Tetra LabX Agent | Connectivity middleware | - Pulls data from LabX and uploads it to the TDP | - LabX account - (Purchased separately) Mettler Toledo System Integration license key - Windows host machine See details |
Tetra OpenLab Agent | Connectivity middleware | - Pulls data from Agilent OpenLab and uploads it to the TDP | - OpenLab CDS account - Agilent OpenLab CDS Software Data Analysis Module - Windows host machine See details |
Tetra UNICORN Agent | Instruments | - Pulls AKTA instrument batch data and uploads it to the TDP | - UNICORN account - Windows host machine See details |
Install or Upgrade an Agent
To install an Agent, see that Agent's installation Guide. To download an Agent for installation, see Tetra Agent & Connector Installers in the TetraConnect Hub.
To upgrade an Agent from a previous version, see Upgrade an Agent.
Connection Types
Agents require network access to TDP and AWS endpoints. There are two connection options for these endpoints:
- TDP (No Connector): Connects Agents directly to the TDP and AWS APIs, or through a proxy that you configure in the Agent host server's settings.
- Tetra Hub: Uses an on-premises Tetra Hub to proxy connections to TDP and AWS APIs.
For more information, see Agent Deployment Options. For additional networking best practices, see Recommended Architectures for Network Connectivity to Private Cloud and On-Premises Components in the TetraConnect Hub.
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.
Updated 3 days ago