Configuration

Adapter for Azure Event Hubs provides configuration of data source and data selection

The examples in the configuration topics use cURL, a commonly available tool on both Windows and Linux. You can configure the adapter with any programming language or tool that supports making REST calls or with the EdgeCmd utility. For more information, see the EdgeCmd utility documentation.

To validate successful configurations, you can perform data retrieval (GET commands) with a browser, if available, on your device.

For more information on AVEVA Adapter configuration tools, see Configuration tools.

Quick Start

This Quick Start guides you through setup of each configuration file available for the Adapter for Azure Event Hubs. As you complete each step, perform each configuration to establish a data flow from a data source to one or more endpoints. Some configurations are optional.

Important: If you want to complete the optional configurations in each step below, complete those tasks before the required tasks.

1. Configure one or more Azure Event Hubs system components.

   See System components.

2. Configure an Azure Event Hubs data source for each Azure Event Hubs device.

   See Configure Data source.

3. Optional: Configure client settings.

   See Optional: Configure Client settings.

4. Configure an Azure Event Hubs data selection for each Azure Event Hubs data source

   See Configure Data selection

5. Optional: Configure data filtersǡ diagnostics and metadata, buffering, and logging.

   See the following topics

   • Data filters

   • Diagnostics and metadata

   • Buffering

   • Optional: Configure Logging

6. Configure one or more egress and health endpoints. If there is a proxy between the adapter and your egress endpoints, define it.

   • Egress endpoints

   • Configure a network proxy

   • Health endpoints