Tetra Connectors
Tetra Connectors provide built-in data integration with specific instruments or systems. They offer similar functionality as Tetra Agents, but are containerized applications that can run either on-premises or in the cloud. After the data is uploaded to the Tetra Scientific Data and AI Cloud, 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 in the TetraConnect Hub. For access, see Access the TetraConnect Hub.
Connector Types
The TDP currently supports two Connector types, which offer the same functionality, but different levels of customization:
- Legacy Connectors are tightly coupled with the TDP and must be upgraded in conjunction with TDP releases.
- Pluggable Connectors can be deployed independent of a TDP release. For more information, see Create, Configure, and Update Pluggable Connectors.
Connector Deployment Options
You can deploy Connectors in two ways:
- Cloud: Allows Connectors to run in the cloud and provides network access directly to the TDP and AWS APIs.
- Hub: Uses an on-premises Tetra Hub for Pluggable Connectors, or a Tetra Data Hub for Legacy Connectors, to proxy connections to TDP and AWS APIs. For more information, see Add a Connector to a Hub and Add a Connector to a Data Hub.
For more TDP networking best practices, see Recommended Architectures for Network Connectivity to Private Cloud and On-Premises Components in the TetraConnect Hub. For access, see Access the TetraConnect Hub.
Supported Tetra Connectors
The TDP currently supports the following Legacy Connectors. For information about which Connector versions are eligible for patches and customer engineering support, see Tetra Integrations Support.
Connector | Source Type | Capabilities | Supported Deployment Types | Required Licenses and Infrastructure |
|---|---|---|---|---|
Connectivity middleware |
| Cloud |
| |
ELN |
| Cloud |
| |
Connectivity middleware |
| Cloud only |
| |
Connectivity middleware |
| Cloud |
| |
ELN |
| Cloud only |
| |
File sharing |
| Cloud only |
| |
File sharing |
| Cloud only |
|
Supported Pluggable Connectors
NOTEYou can add Pluggable Connectors to an on-premises Tetra Hub or cloud deployment only. For more information, see Create, Configure, and Update Pluggable Connectors.
The TDP currently supports the following Pluggable Connectors. For information about which Connector versions are eligible for patches and customer engineering support, see Tetra Integrations Support.
| Pluggable Connector | Source Type | Description | Required Licenses and Infrastructure |
|---|---|---|---|
| Tetra Amazon S3 Connector | File sharing | • Monitors Amazon S3 folders for new and modified files and automatically uploads them to the TDP | • AWS account • Amazon S3 bucket • Amazon SQS Queue • Amazon SNS topic • IAM role • AWS CLI See details |
| Tetra Benchling Connector | Connectivity middleware | • Pulls events from Benchling and uploads it to the TDP • Can use self-signed SSL/TLS certificates | • Benchling Notebook account See details |
| Tetra Biacore Insight Connector | Connectivity middleware | • Pulls data from Cytiva Biacore Insight and uploads it to the TDP | • Biacore Insight account See details |
| Tetra Cellario Connector v2 | Connectivity middleware | • Pulls order data from Cellario and uploads it to the TDP • Uploads historical data to the TDP • Can use self-signed SSL/TLS certificates | • Cellario account • Cellario instance, installed and running See details |
| Tetra SDC Connector v2 | Connectivity middleware | • Pulls measurements from SDC and then uploads them to the TDP • Accepts measurement requests and sends them to SDC | • AGU SDC account See details |
| Tetra SharePoint Online Connector | File sharing | • Monitors SharePoint folders for new and modified files and automatically uploads them to the TDP | • SharePoint Online account • Microsoft enterprise application See details |
| Tetra KEPServerEX Connector | Connectivity middleware | • Pulls data from KEPServerEX and uploads it to the TDP | • KEPServerEX account • IoT Gateway plugin (licensed separately from KEPServerEX) • An MQTT broker run on the same machine as KEPServerEX • (Recommended) Tetra Hub See details |
| Tetra LabX Connector | Connectivity middleware | • Pulls data from multiple LabX instances and uploads it to the TDP | • LabX account • Linux host machine See details |
Updated 11 days ago
