Integrate and extend your AirVantage platform
Here we give you an overview of what you can do with the AirVantage Cloud Connector to send event to Microsoft Azure EventHub and getting messages from your EventHub.
We’ll explain all the technical aspects needed for a robust, secure & reliable interface:
- principles & best practices
- configuration & authentication
- how to get messages
This section explains when and why to use the Cloud connector, what it is and the available options.
The Azure EventHub Cloud Connector provides:
When you connect AirVantage to EventHub Streams, you have to define the type of notifications you want: operations, data, alert.
Moreover, you have to supply the connection string which identify where to send the messages.
This section explains how to configure your client. Please read carefully this section in order to supply correct information to enable the end point on the AirVantage side.
Set up a Microsoft Azure services account here .
The policies describes the rights allowed for a MS Azure account on a specific object (here an EventHub sream). The
connection string contains the policy and the targeted EventHub information to allow an application to send messages to an eventHub.
The next steps describe how to generate this connection string.
Step 1. Create an Azure EventHub stream in the customer’s Azure account, into which AirVantage will publish:
>and filter with Event Hub
Addin the Event Hub management page to add a namespace
Step 2. Create your Eventhub:
+Event Hubin the top
Step 3. Create a policy in the customer’s Azure account:
Shared access policies
Addto add a new policy for AirVantage
Step 4. Supply the following information using the CRM
You can check that the data received from AirVantage shows up in the stream monitoring provided by Microsoft. The graph that describes the number of incoming request lets you ensure that AirVantage is connected to your EventHub stream. If no data is shown, you need to check your configuration.
You can reach this graph in your EventHub’s verview section by scrolling to the bottom.
This section explains how to consume the messages from EventHub in order to support high volume messaging.
EventHub is limited to event lesser than 256k (see this page , section
Batch event send operations). So you may avoid to push over-sized data.
Other limitations can be applied according to the selected offer (see Event Hubs Pricing page).
You can follow this tutorial to start to consume your messages