--- title: Aveva DataHub slug: litmusedge/product-features/integration/integration-connectors/aveva/aveva-datahub docTags: createdAt: 2026-09-08T18:21:17.585Z --- The AVEVA DataHub integration enables Litmus Edge to connect with AVEVA DataHub. ## Supported communication - Outbound (Publish data from Edge to AVEVA DataHub) - Yes - Inbound (Subscribe data from AVEVA DataHub to Edge) - Yes ## Configurations | **Field** | **Details** | **Required** | | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | Name | Connector instance name. | Yes | | Description | Description for the connector instance. | No | | Endpoint | Regional AVEVA DataHub service URL this connector sends to. Found under **Security** > **Clients**. | Yes | | Client Id | Client ID of the credentials used to authenticate this connection. Found under **Security** > **Clients**. | Yes | | Client Secret | Secret paired with the Client Id. oth are required to authenticate. Created under **Security** > **Clients**. | Yes | | Tenant Id | Identifier of the AVEVA DataHub tenant that owns the target namespace and stream. Found under **Security** > **Clients**. | Yes | | Stream Id | Default Sequential Data Store (SDS) stream that outbound data is written to. Found under Data Management. | Yes | | Namespace | Namespace within the tenant that contains the target SDS stream. | Yes | | Parallel Publish Count | The number of simultaneously publishing messages. | No | | Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No | ## Persistent storage configurations | **Field** | **Details** | **Required** | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No | | Persistent storage size limit | Set the size limit for storing persisted data in GB. | No | | Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) sends the earliest message first. Selecting LIFO (Last In First Out) sends the latest message first. | No | ## Related topics - [Aveva Data Hub Integration Guide](docId\:AXo-gzLsGg9cb06YKhGeU) - [Add a Connector](docId:4YVfCEP7GYScJHMKYFCuM) - [Manage Connectors](docId\:tQoP7QtquSQqDq9yhbJ34)