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.
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:
- On-premises—requires the use of a Tetra Data Hub for Legacy Connectors, or a Tetra Hub for Pluggable Connectors. To deploy an on-premises Connector, see Add a Connector to a Data Hub and Add a Connector to a Hub.
- Cloud—allows connectors to run in the AWS Cloud, without the use of a Tetra 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 |
|---|---|---|---|
| Tetra Cellario Connector v1 | Connectivity middleware | - Pulls order data from Cellario and uploads it to the TDP | Cloud -or- On-premises (Tetra Data Hub) |
| Tetra IDBS E-Workbook Connector | ELN | - Pulls data from IDBS E-Workbook and uploads it to the TDP - Searches data in the TDP and downloads the results to IDBS E-Workbook | Cloud -or- On-premises (Tetra Data Hub) |
| Tetra SDC Connector v1 | Connectivity middleware | - Pulls measurements from SDC and then uploads them to the TDP - Accepts measurement requests and sends them to SDC | Cloud only |
| Tetra Solace Connector | Connectivity middleware | - Integrates the TDP with the Solace PubSub+ Platform | Cloud -or- On-premises (Tetra Data Hub) |
| Tetra Signals Connector | ELN | - Pulls data from Signals and uploads it to the TDP - Searches data in the TDP and downloads the results to Signals | Cloud only |
| Tetra Egnyte Connector | File sharing | - Monitors Egnyte folders for new and modified files and automatically uploads them to the TDP | Cloud only |
| Tetra Box Connector | File sharing | - Monitors Box folders for new and modified files and automatically uploads them to the TDP | Cloud only |
Supported Pluggable Connectors
NOTE
You 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 |
|---|---|---|
| Tetra Benchling Connector v1 | Connectivity middleware | - Pulls events from Benchling and uploads it to the TDP - Can use self-signed SSL/TLS certificates |
| 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 |
| 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 |
| Tetra KEPServerEX Connector | Connectivity middleware | - Pulls data from KEPServerEX and uploads it to the TDP |
Updated 3 days ago