Read Message from Event Hub activity

An activity that reads a device-to-cloud message from Event Hub that is registered in Microsoft Azure IoT.


Read Message from Event Hub activity

Configure the Read Message from Event Hub activity

To configure the Read Message from Event Hub activity, do the procedure in this topic.

Prerequisites

Good to Know

How to Start

  1. On the Application Explorer screen, do one of these:
  2. Do one of these:
    • Add an activity:
      1. In the Process Builder, in the Activity Library open the Microsoft Azure IoT Microsoft Azure IoT icon tab.
      2. On the Microsoft Azure IoT Microsoft Azure IoT icon tab, drag the Read Message From Event Hub Read Message From Event Hub icon activity onto your process.
    • Change an activity:
      1. In your process, double-click your activity.

General Configuration

Specifies the basic settings for the Read Message from Event Hub activity.

Figure: General Configuration screen

General Configuration screen

Fields

Field Name Definition

Display Name

Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data Variables:
No
Example:
Refer to:

Description

Function:
Specifies an optional text description for your activity.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
No

Read Message from Event Hub Configuration

Configures how to store the message from Event Hub.

Figure: Read Message from Event Hub Configuration screen

Read Message from Event Hub Configuration screen

Fields

Field Name Definition

Microsoft Azure IoT

Function:
Specifies the access token that connects to your Microsoft Azure IoT service.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Process Data Variables:
No

Add Token Add Token icon

Opens this Screen:
Access Token for Microsoft Azure IoT
Function of this Screen:
Configure an access token to connect to Microsoft Azure IoT.

Device ID

Function:
Specifies the device ID for your IoT device to read message.
Accepted Values:
A device ID from Microsoft Azure IoT.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Retry Count

Function:
Specifies the number of times Microsoft Azure IoT tries to read messages from Event Hub.
Accepted Values:
A positive integer.
Default Value:
60
Accepts Process Data Variables:
Yes

Delay Between Retry (milliseconds)

Function:
Specifies a time interval in milliseconds between each retry.
Accepted Values:
A positive integer.
Default Value:
1000
Accepts Process Data Variables:
Yes

Payload

Function:
Specifies the payload to store at runtime.
Accepted Values:
  • Save Response to This Variable - Specifies a process data variable to store the JSON payload at runtime.
  • Map Response to Process Schema - Connects the values in your payload with your AgilePoint schema.

    Click Map Schema button to open the Schema Mapper. Use this screen to connect the response to process schema.

Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Sample Payload JSON

Function:
Specifies a JSON code snippet that connects your payload to the schema.
To Open this Field:
  1. On the Read Message from Event Hub Configuration screen, click Map Response to Process Schema.
Accepted Values:
A JSON code snippet.
Default Value:
None
Accepts Process Data Variables:
No

Map Schema Map Schema icon

Opens this Screen:
Schema Mapper
To Open this Field:
  1. On the Read Message from Event Hub Configuration screen, click Map Response to Process Schema.
Function of this Screen:
Maps SharePoint fields, form fields, web methods, or other input sources to an XML schema..
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?