- #Kepserverex v6 download update
- #Kepserverex v6 download free
Remember, the 'hostname' in config.yaml has to match whatever name you use from clients to connect to it exactly, whether it's a FQDN or the IP address.
#Kepserverex v6 download update
If you do, however, make sure that you update the 'hostname' property in config.yaml to be the IP address of the gateway and not its name.
if you do not, or just want to test before you do, you can add a hosts file entry on your KEPServerEX for your IoT Edge gateway in the c:\windows\system32\drivers\etc\hosts fileĮither way, ensure your KEPServerEX can 'ping' your IoT Edge gateway device by this FQDN.Īlternately, you can reference the IoT Edge gateway by its IP address instead. if you have DNS infrastructure services available in the environment in which your KEPServerEX runs, add a DNS entry for your IoT Edge gateway. This FQDN must match the hostname parameter used in your IoT Edge device's config.yaml file. The KEPServerEX must also be able to resolve the fully-qualified domain name (FQDN) of the IoT Edge gateway to its IP address. Make sure you do this for the 'local computer', and not 'personal'. on the KEPServerEX, using the Certificate Manager MMC console, import the IoT Edge Root CA certificate into its "Trust Root Certification Authorities" store. If you used the instructions above, this certificate will be located at $CERTDIR/certs/.cert.pem (where $CERTDIR is the directory in which you created your dev/test certificates). You need to get this certificate to a location from which your KEPServerEX can read (either copy local to the KEPServerEX or a file share it can reach) if you used the dev/test-only convenience scripts provided by the Azure IoT engineering team, you need to copy the Root CA certificate from your IoT Edge box. if you used a production certificate from a company like Baltimore, DigiCert, etc to set up your IoT Edge device, or a corporate certificate based on a Certificate Authority(CA) that your KEPServerEX will already trust, you can skip this step. The Edge Hub module will provide it with a server certificate for the TLS connection and the KEPServerEX must trust that certificate. When KEPServerEX connects to IoT Edge, it will do so with MQTT over TLS. Administrative permissions on the KEPServerEX (both KEPServerEX and the underlying host machine)īefore configuring KEPServerEX, we need to take a few environmental setup steps. This is required by the KEPServerEX IoT Gateway. the Java Runtime Engine (JRE) installed on the KEPServerEX server. a KEPServerEX set up and licensed with the IoT Gateway plug-in. an Azure IoT Edge device set up as a 'transparent gateway' per the Azure IoT Edge documentation ( linux or windows). If you do not already have one, create one via the instructions here #Kepserverex v6 download free
If you do not already have one, you can create an Azure account and subscription with free credits here Examples include the ability to use custom modules or Azure Functions to transform the data, Azure Streaming Analytics to do filtering and aggregation of the data before it goes to the cloud, and Azure Machine Learning for making predictions on the edge, potentially without having to send all of the detailed data to the cloud.īelow are the step-by-step instructions for connecting KEPServerEX to IoT Hub through IoT Edge Prerequisites That allows both for Edge to act as a gatewey through which traffic must flow, thus isolating the KEPServerEX further from the Internet, as well as the ability to take advantage of the many IoT Edge capabilities for pre-processing that data on the edge. Many customers have expressed a desire to be able to send the data from KEPServerEX through Azure IoT Edge. Kepware provides an IoT Gateway module today that, per their own instructions, can be used to connect to and send data to Azure IoT Hub over the MQTT protocol.
It has connectivity libraries for a vast array of equipment and is a popular choice for unlocking the data from both new and legacy industrial devices. PTC/Kepware's KEPServerEX is an industry leader in industrial and manufacturing device connectivity. Note: inline images in this sample are not currently showing on the Azure Samples site - to see images and screenshots in this article, visit the github repository by clicking the "Browse on Github" button above Overview These instructions provide the necessary steps to connect PTC/Kepware's KEPServerEX to Azure IoT Hub through Azure IoT Edge.
0 kommentar(er)
