You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+60-60Lines changed: 60 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,11 +28,12 @@ The software is an open source toolbox which has to be integrated into an end to
28
28
Live Objects platform supports load balancing between multiple MQTT subscribers.
29
29
30
30
## Technologies
31
-
* Java 8
32
-
* Spring Boot 2.4.4
33
-
* Microsoft Azure SDK IoT 1.22.0
34
-
* Microsoft Application Insights Java SDK Spring Boot Starter 2.5.1
35
-
* Azure Metrics Spring Boot Starter 2.2.1
31
+
* Java 21
32
+
* Spring Boot 3.2.3
33
+
* Microsoft Iot Hub Java Service SDK 2.1.7
34
+
* Microsoft IoT Hub Java Device Client 2.4.1
35
+
* Microsoft Application Insights Java SDK Spring Boot Starter 2.6.4
36
+
* Azure Metrics Spring Boot Starter 2.3.5
36
37
37
38
## Requirements
38
39
In order to run the connector you need to have:
@@ -42,8 +43,8 @@ In order to run the connector you need to have:
42
43
***Application Insights resource created (per each Iot Hub)** (creation process is described in official [documentation](https://docs.microsoft.com/pl-pl/azure/azure-monitor/app/create-new-resource))
43
44
***App Service plan created (per each Iot Hub)** (creation process is described in official [documentation](https://docs.microsoft.com/en-us/azure/app-service/app-service-plan-manage))
44
45
***Development tools (only when building the package)**
45
-
***Java SE Development Kit 8**
46
-
***Apache Maven**
46
+
***Java SE Development Kit 21**
47
+
***Apache Maven**
47
48
48
49
## Getting the installation package
49
50
@@ -87,52 +88,51 @@ All configuration can be found in **application.yaml** file located in src/main/
37 device-registration-period: 200 # in milliseconds - 200ms
118
+
38 device-reestablish-session-delay: 10000 # in milliseconds - 10s
119
+
39 device-client-connection-timeout: 5000
120
+
40 message-expiry-time: 60000 # in milliseconds - 60s
121
+
41 message-send-max-attempts: 10
122
+
42 message-resend-delay: 10000 # in milliseconds - 10s
123
+
43 tagPlatformKey: platform
124
+
44 tagPlatformValue: LiveObjectsGroupIoT1
125
+
45
126
+
46 lo-messages-topic: MESSAGES_TOPIC
127
+
47 lo-devices-topic: DEVICES_TOPIC
128
+
48 lo-devices-group: DEVICES_GROUP
129
+
49
130
+
50 azure:
131
+
51 application-insights:
132
+
52 enabled: true
133
+
53 instrumentation-key: YOUR_INSTMENTATION_KEY
134
+
54
135
+
...
136
136
```
137
137
138
138
#### hostname
@@ -166,7 +166,7 @@ This value, measured in seconds, defines the maximum time interval between messa
166
166
#### page-size
167
167
Maximum number of devices in single response. Max 1000
168
168
169
-
#### synchronization-device-interval
169
+
#### device-synchronization-interval
170
170
Controls the interval (in seconds) at which device synchronization process starts.
171
171
172
172
#### iot-connection-string
@@ -179,8 +179,8 @@ The `iot-host-name` can be found in the details of IoT Hub:
179
179
180
180

181
181
182
-
#### synchronization-thread-pool-size
183
-
How many threads will be used in devices synchronization process
182
+
#### device-registration-thread-pool-size
183
+
How many threads will be used in devices registration process
184
184
185
185
#### device-client-connection-timeout
186
186
The length of time, in milliseconds, that any given operation will expire in. These operations include reconnecting upon a connection drop and sending a message.
@@ -293,22 +293,22 @@ You can deploy this connector wherever you want (local server, cloud provider et
293
293
```
294
294
- Copy the file to the virtual machine ([documentation](https://docs.microsoft.com/pl-pl/azure/virtual-machines/linux/copy-files-to-linux-vm-using-scp)):
0 commit comments