Riƙe saitunan wakili na Azure IoT Edge a cikin manifest ɗin turawa

Haɗin farko na iya ɓacewa idan wani manifest daga baya ya maye gurbin muhallin edgeAgent/edgeHub ba tare da ƙimar wakilin ba.

Lokacin da turawa ta maye gurbin ma'anar lokacin aiki, riƙe wakilin a cikin duka modules ɗin. Don edgeAgent haɗa:

"env": {
  "https_proxy": {
    "value": "http://proxy.example:8080"
  },
  "UpstreamProtocol": {
    "value": "AmqpWs"
  }
}

Riƙe wannan ƙarƙashin edgeAgent desired properties/systemModules tare da ainihin ma'anar. Kiyaye hotuna, saituna da sauran shigarwar muhalli. edgeHub ma yana buƙatar https_proxy ɗinsa; UpstreamProtocol da aka nuna yana kiyaye zaɓin AmqpWs na fara aiki na wakilin.

Ana buƙatar AMQP ta WebSockets lokacin da mai shiga tsakani ya toshe ainihin AMQP. HTTP URL yana bayyana mai sauraro duk da cewa sabis ɗin yana amfani da TLS.

Ka ɗauki ƙimar zuwa manifest ɗin gaba. Cire hanyar edgeAgent na iya hana shi karɓar turawar da aka yi don gyara shi.

Daukar hotuna na injin kwantena, sabis ɗin ainihi da Edge daemon sun kasance masu amfani daban. A cikin EFLOW suna aiki a cikin Linux VM, don haka saitin Windows host kaɗai ba ya daidaita su. Modules ɗin mai amfani ma suna buƙatar abubuwan da abokan cinikinsu suka goyi bayan.

Labarai masu alaƙa