Skip to content

Commit f5c08c4

Browse files
Merge pull request #230916 from kgremban/mar15-metarefresh-c2d
Metadata and filename refresh - c2d, file upload, jobs
2 parents 13bcf05 + 3c65e78 commit f5c08c4

27 files changed

+211
-140
lines changed

articles/iot-hub/.openpublishing.redirection.iot-hub.json

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,71 @@
8080
"redirect_url": "/azure/iot-develop/quickstart-send-telemetry-iot-hub?pivots=programming-language-python",
8181
"redirect_document_id": false
8282
},
83+
{
84+
"source_path_from_root": "/articles/iot-hub/iot-hub-csharp-csharp-c2d.md",
85+
"redirect_url": "/azure/iot-hub/c2d-messaging-dotnet",
86+
"redirect_document_id": true
87+
},
88+
{
89+
"source_path_from_root": "/articles/iot-hub/iot-hub-python-python-c2d.md",
90+
"redirect_url": "/azure/iot-hub/c2d-messaging-python",
91+
"redirect_document_id": true
92+
},
93+
{
94+
"source_path_from_root": "/articles/iot-hub/iot-hub-node-node-c2d.md",
95+
"redirect_url": "/azure/iot-hub/c2d-messaging-node",
96+
"redirect_document_id": true
97+
},
98+
{
99+
"source_path_from_root": "/articles/iot-hub/iot-hub-java-java-c2d.md",
100+
"redirect_url": "/azure/iot-hub/c2d-messaging-java",
101+
"redirect_document_id": true
102+
},
103+
{
104+
"source_path_from_root": "/articles/iot-hub/iot-hub-ios-swift-c2d.md",
105+
"redirect_url": "/azure/iot-hub/c2d-messaging-ios",
106+
"redirect_document_id": true
107+
},
108+
{
109+
"source_path_from_root": "/articles/iot-hub/iot-hub-java-java-file-upload.md",
110+
"redirect_url": "/azure/iot-hub/file-upload-java",
111+
"redirect_document_id": true
112+
},
113+
{
114+
"source_path_from_root": "/articles/iot-hub/iot-hub-python-python-file-upload.md",
115+
"redirect_url": "/azure/iot-hub/file-upload-python",
116+
"redirect_document_id": true
117+
},
118+
{
119+
"source_path_from_root": "/articles/iot-hub/iot-hub-node-node-file-upload.md",
120+
"redirect_url": "/azure/iot-hub/file-upload-node",
121+
"redirect_document_id": true
122+
},
123+
{
124+
"source_path_from_root": "/articles/iot-hub/iot-hub-csharp-csharp-file-upload.md",
125+
"redirect_url": "/azure/iot-hub/file-upload-dotnet",
126+
"redirect_document_id": true
127+
},
128+
{
129+
"source_path_from_root": "/articles/iot-hub/iot-hub-java-java-schedule-jobs.md",
130+
"redirect_url": "/azure/iot-hub/schedule-jobs-java",
131+
"redirect_document_id": true
132+
},
133+
{
134+
"source_path_from_root": "/articles/iot-hub/iot-hub-python-python-schedule-jobs.md",
135+
"redirect_url": "/azure/iot-hub/schedule-jobs-python",
136+
"redirect_document_id": true
137+
},
138+
{
139+
"source_path_from_root": "/articles/iot-hub/iot-hub-node-node-schedule-jobs.md",
140+
"redirect_url": "/azure/iot-hub/schedule-jobs-node",
141+
"redirect_document_id": true
142+
},
143+
{
144+
"source_path_from_root": "/articles/iot-hub/iot-hub-csharp-csharp-schedule-jobs.md",
145+
"redirect_url": "/azure/iot-hub/schedule-jobs-dotnet",
146+
"redirect_document_id": true
147+
},
83148
{
84149
"source_path_from_root": "/articles/iot-hub/iot-hub-devguide-glossary.md",
85150
"redirect_url": "/azure/iot-fundamentals/iot-glossary/",

articles/iot-hub/TOC.yml

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -310,34 +310,34 @@
310310
- name: Send cloud-to-device messages
311311
items:
312312
- name: .NET
313-
displayName: cloud-to-device messages, C2D
314-
href: iot-hub-csharp-csharp-c2d.md
313+
displayName: cloud-to-device messages, C2D, csharp, C#
314+
href: c2d-messaging-dotnet.md
315315
- name: Python
316316
displayName: cloud-to-device messages, C2D
317-
href: iot-hub-python-python-c2d.md
317+
href: c2d-messaging-python.md
318318
- name: Node.js
319319
displayName: cloud-to-device messages, C2D
320-
href: iot-hub-node-node-c2d.md
320+
href: c2d-messaging-node.md
321321
- name: Java
322322
displayName: cloud-to-device messages, C2D
323-
href: iot-hub-java-java-c2d.md
323+
href: c2d-messaging-java.md
324324
- name: iOS
325325
displayName: cloud-to-device messages, C2D
326-
href: iot-hub-ios-swift-c2d.md
326+
href: c2d-messaging-ios.md
327327
- name: Upload files from devices
328328
items:
329329
- name: .NET
330-
displayName: Azure Storage, file upload
331-
href: iot-hub-csharp-csharp-file-upload.md
330+
displayName: file upload, upload files, csharp, C#
331+
href: file-upload-dotnet.md
332332
- name: Python
333-
displayName: Azure Storage, file upload
334-
href: iot-hub-python-python-file-upload.md
333+
displayName: file upload, upload files
334+
href: file-upload-python.md
335335
- name: Node.js
336-
displayName: Azure Storage, file upload
337-
href: iot-hub-node-node-file-upload.md
336+
displayName: file upload, upload files
337+
href: file-upload-node.md
338338
- name: Java
339-
displayName: Azure Storage, file upload
340-
href: iot-hub-java-java-file-upload.md
339+
displayName: file upload, upload files
340+
href: file-upload-java.md
341341
- name: Get started with device twins
342342
items:
343343
- name: CLI
@@ -398,17 +398,17 @@
398398
displayName: jobs
399399
href: schedule-jobs-cli.md
400400
- name: .NET
401-
displayName: jobs
402-
href: iot-hub-csharp-csharp-schedule-jobs.md
401+
displayName: jobs, csharp, C#
402+
href: schedule-jobs-dotnet.md
403403
- name: Python
404404
displayName: jobs
405-
href: iot-hub-python-python-schedule-jobs.md
405+
href: schedule-jobs-python.md
406406
- name: Node.js
407407
displayName: jobs
408-
href: iot-hub-node-node-schedule-jobs.md
408+
href: schedule-jobs-node.md
409409
- name: Java
410410
displayName: jobs
411-
href: iot-hub-java-java-schedule-jobs.md
411+
href: schedule-jobs-java.md
412412
- name: Query Avro data from a hub route
413413
displayName: Azure Data Lake, U-SQL
414414
href: iot-hub-query-avro-data.md

articles/iot-hub/iot-hub-csharp-csharp-c2d.md renamed to articles/iot-hub/c2d-messaging-dotnet.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
11
---
2-
title: Cloud-to-device messages with Azure IoT Hub (.NET) | Microsoft Docs
3-
description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for .NET. You modify a device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
2+
title: Send cloud-to-device messages (.NET)
3+
titleSuffix: Azure IoT Hub
4+
description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for .NET.
45
author: kgremban
56

7+
ms.author: kgremban
68
ms.service: iot-hub
7-
services: iot-hub
89
ms.devlang: csharp
9-
ms.topic: conceptual
10+
ms.topic: how-to
1011
ms.date: 10/20/2021
11-
ms.author: kgremban
1212
ms.custom: [amqp, mqtt, 'Role: Cloud Development', 'Role: IoT Device', devx-track-csharp]
1313
---
1414

1515
# Send messages from the cloud to your device with IoT Hub (.NET)
1616

1717
[!INCLUDE [iot-hub-selector-c2d](../../includes/iot-hub-selector-c2d.md)]
1818

19-
Azure IoT Hub is a fully managed service that helps enable reliable and secure bi-directional communications between millions of devices and a solution back end.
19+
Azure IoT Hub is a fully managed service that helps enable reliable and secure bi-directional communications between millions of devices and a solution back end.
2020

2121
This article shows you how to:
2222

@@ -78,14 +78,14 @@ In this section, modify your device app to receive cloud-to-device messages from
7878
ReceiveC2dAsync();
7979
```
8080

81-
The `ReceiveAsync` method asynchronously returns the received message at the time that it is received by the device. It returns *null* after a specifiable timeout period. In this example, the default of one minute is used. When the app receives a *null*, it should continue to wait for new messages. This requirement is the reason for the `if (receivedMessage == null) continue` line.
81+
The `ReceiveAsync` method asynchronously returns the received message at the time that it's received by the device. It returns *null* after a specifiable timeout period. In this example, the default of one minute is used. When the app receives a *null*, it should continue to wait for new messages. This requirement is the reason for the `if (receivedMessage == null) continue` line.
8282

8383
The call to `CompleteAsync()` notifies IoT Hub that the message has been successfully processed and that the message can be safely removed from the device queue. The device should call this method when its processing successfully completes regardless of the protocol it's using.
8484

8585
With AMQP and HTTPS, but not MQTT, the device can also:
8686

8787
* Abandon a message, which results in IoT Hub retaining the message in the device queue for future consumption.
88-
* Reject a message, which which permanently removes the message from the device queue.
88+
* Reject a message, which permanently removes the message from the device queue.
8989

9090
If something happens that prevents the device from completing, abandoning, or rejecting the message, IoT Hub will, after a fixed timeout period, queue the message for delivery again. For this reason, the message processing logic in the device app must be *idempotent*, so that receiving the same message multiple times produces the same result.
9191

articles/iot-hub/iot-hub-ios-swift-c2d.md renamed to articles/iot-hub/c2d-messaging-ios.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
---
2-
title: Cloud-to-device messages with Azure IoT Hub (iOS) | Microsoft Docs
3-
description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for iOS.
2+
title: Send cloud-to-device messages (iOS)
3+
titleSuffix: Azure IoT Hub
4+
description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for iOS.
45
author: kgremban
6+
7+
ms.author: kgremban
58
ms.service: iot-hub
6-
services: iot-hub
7-
ms.topic: conceptual
9+
ms.devland: swift
10+
ms.topic: how-to
811
ms.date: 04/19/2018
9-
ms.author: kgremban
1012
ms.custom: mqtt
1113
---
1214

@@ -65,7 +67,7 @@ Along with installing the pods required for your project, the installation comma
6567

6668
### Run the sample device application
6769

68-
1. Retrieve the connection string for your device. You can copy this string from the [Azure portal](https://portal.azure.com) in the device details blade, or retrieve it with the following CLI command:
70+
1. Retrieve the connection string for your device. You can copy this string from the [Azure portal](https://portal.azure.com) in the device details page, or retrieve it with the following CLI command:
6971

7072
```azurecli-interactive
7173
az iot hub device-identity connection-string show --hub-name {YourIoTHubName} --device-id {YourDeviceID} --output table
@@ -91,9 +93,9 @@ Along with installing the pods required for your project, the installation comma
9193

9294
## Send a cloud-to-device message
9395

94-
You are now ready to receive cloud-to-device messages. Use the Azure portal to send a test cloud-to-device message to your simulated IoT device.
96+
You're now ready to receive cloud-to-device messages. Use the Azure portal to send a test cloud-to-device message to your simulated IoT device.
9597

96-
1. In the **iOS App Sample** app running on the simulated IoT device, click **Start**. The application starts sending device-to-cloud messages, but also starts listening for cloud-to-device messages.
98+
1. In the **iOS App Sample** app running on the simulated IoT device, select **Start**. The application starts sending device-to-cloud messages, but also starts listening for cloud-to-device messages.
9799

98100
![View sample IoT device app](media/iot-hub-ios-swift-c2d/view-d2c.png)
99101

articles/iot-hub/iot-hub-java-java-c2d.md renamed to articles/iot-hub/c2d-messaging-java.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: Cloud-to-device messages with Azure IoT Hub (Java) | Microsoft Docs
3-
description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for Java. You modify a simulated device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
2+
title: Send cloud-to-device messages (Java)
3+
titleSuffix: Azure IoT Hub
4+
description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for Java.
45
author: kgremban
56

67
ms.author: kgremban
78
ms.service: iot-hub
8-
services: iot-hub
99
ms.devlang: java
10-
ms.topic: conceptual
10+
ms.topic: how-to
1111
ms.date: 06/28/2017
1212
ms.custom: [amqp, mqtt, devx-track-java]
1313
---
@@ -84,12 +84,12 @@ In this section, modify your device app to receive cloud-to-device messages from
8484
mvn clean package -DskipTests
8585
```
8686

87-
The `execute` method in the `AppMessageCallback` class returns `IotHubMessageResult.COMPLETE`. This notifies IoT Hub that the message has been successfully processed and that the message can be safely removed from the device queue. The device should return this value when its processing successfully completes regardless of the protocol it's using.
87+
The `execute` method in the `AppMessageCallback` class returns `IotHubMessageResult.COMPLETE`. This status notifies IoT Hub that the message has been successfully processed and that the message can be safely removed from the device queue. The device should return this value when its processing successfully completes regardless of the protocol it's using.
8888

8989
With AMQP and HTTPS, but not MQTT, the device can also:
9090

9191
* Abandon a message, which results in IoT Hub retaining the message in the device queue for future consumption.
92-
* Reject a message, which which permanently removes the message from the device queue.
92+
* Reject a message, which permanently removes the message from the device queue.
9393

9494
If something happens that prevents the device from completing, abandoning, or rejecting the message, IoT Hub will, after a fixed timeout period, queue the message for delivery again. For this reason, the message processing logic in the device app must be *idempotent*, so that receiving the same message multiple times produces the same result.
9595

@@ -193,7 +193,7 @@ In this section, you create a Java console app that sends cloud-to-device messag
193193

194194
## Run the applications
195195

196-
You are now ready to run the applications.
196+
You're now ready to run the applications.
197197
198198
1. At a command prompt in the simulated-device folder, run the following command to begin sending telemetry to your IoT hub and to listen for cloud-to-device messages sent from your hub:
199199

articles/iot-hub/iot-hub-node-node-c2d.md renamed to articles/iot-hub/c2d-messaging-node.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: Cloud-to-device messages with Azure IoT Hub (Node) | Microsoft Docs
3-
description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for Node.js. You modify a simulated device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
2+
title: Send cloud-to-device messages (Node.js)
3+
titleSuffix: Azure IoT Hub
4+
description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for Node.js.
45
author: kgremban
56

67
ms.author: kgremban
78
ms.service: iot-hub
8-
services: iot-hub
9-
ms.devlang: javascript
10-
ms.topic: conceptual
9+
ms.devlang: nodejs
10+
ms.topic: how-to
1111
ms.date: 06/16/2017
1212
ms.custom: [amqp, mqtt, devx-track-js]
1313
---
@@ -70,12 +70,12 @@ In this section, modify your device app to receive cloud-to-device messages from
7070
});
7171
```
7272

73-
In this example, the device invokes the **complete** function to notify IoT Hub that it has processed the message and that it can safely be removed from the device queue. The call to **complete** is not required if you are using MQTT transport and can be omitted. It is required for AMQP and HTTPS.
73+
In this example, the device invokes the **complete** function to notify IoT Hub that it has processed the message and that it can safely be removed from the device queue. The call to **complete** isn't required if you're using MQTT transport and can be omitted. It's required for AMQP and HTTPS.
7474

7575
With AMQP and HTTPS, but not MQTT, the device can also:
7676

7777
* Abandon a message, which results in IoT Hub retaining the message in the device queue for future consumption.
78-
* Reject a message, which which permanently removes the message from the device queue.
78+
* Reject a message, which permanently removes the message from the device queue.
7979

8080
If something happens that prevents the device from completing, abandoning, or rejecting the message, IoT Hub will, after a fixed timeout period, queue the message for delivery again. For this reason, the message processing logic in the device app must be *idempotent*, so that receiving the same message multiple times produces the same result.
8181

@@ -117,7 +117,7 @@ In this section, you create a Node.js console app that sends cloud-to-device mes
117117
var Message = require('azure-iot-common').Message;
118118
```
119119

120-
5. Add the following code to **SendCloudToDeviceMessage.js** file. Replace the "{iot hub connection string}" and "{device id}" placeholder values with the IoT hub connection string and device ID you noted previously:
120+
5. Add the following code to **SendCloudToDeviceMessage.js** file. Replace the "{iot hub connection string}" and "{device ID}" placeholder values with the IoT hub connection string and device ID you noted previously:
121121
122122
```javascript
123123
var connectionString = '{iot hub connection string}';
@@ -170,7 +170,7 @@ In this section, you create a Node.js console app that sends cloud-to-device mes
170170
171171
## Run the applications
172172
173-
You are now ready to run the applications.
173+
You're now ready to run the applications.
174174
175175
1. At the command prompt in the **simulated-device** folder, run the following command to send telemetry to IoT Hub and to listen for cloud-to-device messages:
176176

articles/iot-hub/iot-hub-python-python-c2d.md renamed to articles/iot-hub/c2d-messaging-python.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,14 @@
11
---
2-
title: Cloud-to-device messages with Azure IoT Hub (Python) | Microsoft Docs
3-
description: How to send cloud-to-device messages to a device from an Azure IoT hub using the Azure IoT SDKs for Python. You modify a simulated device app to receive cloud-to-device messages and modify a back-end app to send the cloud-to-device messages.
2+
title: Send cloud-to-device messages (Python)
3+
titleSuffix: Azure IoT Hub
4+
description: How to send cloud-to-device messages from a back-end app and receive them on a device app using the Azure IoT SDKs for Python.
45
author: kgremban
6+
7+
ms.author: kgremban
58
ms.service: iot-hub
6-
services: iot-hub
79
ms.devlang: python
8-
ms.topic: conceptual
10+
ms.topic: how-to
911
ms.date: 01/02/2023
10-
ms.author: kgremban
1112
ms.custom: mqtt, devx-track-python, py-fresh-zinc
1213
---
1314

@@ -75,7 +76,7 @@ In this section, you create a Python console app to simulate a device and receiv
7576
CONNECTION_STRING = "{deviceConnectionString}"
7677
```
7778
78-
1. Define the following function that will be used to print received messages to the console:
79+
1. Define the following function that is used to print received messages to the console:
7980
8081
```python
8182
def message_handler(message):

0 commit comments

Comments
 (0)