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. To start using an integration, see our Integration Quickstart Guides and the specific integration's documentation.
For additional best practices, see Data Integration and General Agents in the TetraConnect Hub. For access, see Access the TetraConnect Hub.
IMPORTANTIt'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 |
---|---|---|---|
Instruments |
|
| |
Instruments |
|
| |
File sharing |
|
| |
Connectivity middleware |
|
| |
File sharing |
|
| |
Connectivity middleware |
|
| |
Connectivity middleware |
|
| |
Instruments |
|
|
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.
NOTEFeedback 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 5 days ago