Libelium Meshlium Xtreme, Техническое руководство

Страница: 79 / 214

-79- v7.3
Cloud Connectors
Meshlium
X
treme
12.1.3.4. Configuration
As result of previous steps, we should have a namespace , a directive name , a directive key and an event hub
name . These are the main properties we should set in the Manager System to configure an Event Hub connection.
Now we can access the Meshlium Manager and fulfill the Azure Event Hub fields with the previously obtained
configuration.
Figure: Configuring Azure Event Hubs in Meshlium
•
Namespace: Name of the space created in the Azure service cloud.
•
Directive name: Name of the directive created in Azure.
•
Directive key: Key of the directive associated to the previous name.
•
Name: Name of the Event Hub established in Azure.
•
Template file: Users can define their own data structure using these wild-cards (as you can see in the previous
figure):
-
#ID# : Unique identifier for data
-
#ID_WASP#: Identifies the Waspmote unit
-
#ID_SECRET#: Secret identifier
-
#SENSOR#: Identifies the sensor
-
#VALUE#: Value obtained from the sensor
#TS(“c”)#: Date with custom format. The parameter passed in this wild-card corresponds to the same ones you
can use in PHP date function (see format parameters in http://php.net/manual/es/function.date.php#refsect1-
function.date-parameters) .