Deploying BHDO on OpEdge

prerequisites 1 opedge device is installed and configured 2 opedge device is activated on belden horizon 3\ you have the required licenses for bhdo section 1 deploying the bhdo application option 1 deployment through belden horizon 1 login to belden horizon & select the “applications” tab locate the bhdo application and click on “deploy” 2\ select your opedge gateway & click on “next” 3\ check the application summary screen & click on “deploy application” review the summary (memory, cores, ports, volumes etc ) important make a note of the container path and volume when you re deploy the app (after corruption or deletion), this will preserve the licenses and configuration refer section 3 for more details 4\ now the application deployment is "in progress" when the status changes to “deployed”, click on “finish” bhdo application is installed and running on the opedge gateway option 2 local deployment open opedge device’s local ui in web browser via link as https //\<device ip address 8080> login the device & then click on “applications” & then “containers” 2 click on “+add”, pop up page will be displayed as below click on “upload application” 3\ choose the file from local file system and click on “import” 4\ once the upload is complete, below screen will be displayed, add the application “name” & click on “next” 5\ toggle the “enable network” and select “bridge” from the drop down click on “+add port” and map container port to host post as below 443 to 4443 (web ui) 4840 to 4840 (opc ua server) 1883 to 1883 (bhdo's native mqtt broker) 8086 to 8086 (bhdo's built in influxdb database) then click on “next” 6\ allot the ram (4096 mb) and cpu cores (2) click on “next” 7\ container path and volume mapping is not required for the 1st time deployment click on “next” 8\ the following environment variables are required in order for certain features within bhdo to work properly variables for ping utility name sysctl net ipv4 ping group range value 0 2147483647 variables for bhdm activation name cap add1 value net admin 9\ advanced mode is not required, click on “next” 10 review the summary and click on “create” 11 now you can see the container is created and running in the applications tab 12 you can see the details of running container click on three dots symbol under “other” tab then from drop down click on “edit container details” you can see the details of running container application scroll down to “advanced settings” section here you can see the container path to volume mapping same can be seen by clicking on “storage” tab under applications section important make a note of the container path and volume when you re deploy the app (after corruption or deletion), this will preserve the licenses and configuration refer section 3 for more details section 2 bhdo application web ui 1\ now you can access the bhdo app via local interface by inserting \[https //\[ip address of opeedge 8d] 4443 in your web browser for the first time login default username is “admin” and password is “password” 2\ accept the end user license agreement then you will be prompted to change the password change the password and click “reset password” 3\ now when you login you will be directed to the license key page, select “advanced options” and look for the “node locked license” section click on “add license” insert the license activation key provided to you and click on “submit” 4\ once the license key/keys are registered then you can start using the app section 3 application redeployment if your application container is corrupted or deleted you can re deploy the application and it will pick up from where you left (preserving the licenses and any configuration) note before proceeding further please delete the corrupted container from the opedge device either through local ui or through belden horizon option 1 deployment through belden horizon follow the same steps from section 1 > option 1 now follow same steps in section 2 bhdo application web ui you can access the bhdo app via local interface by inserting \[https //\[ip address of opeedge 8d] 443 in your web browser you can directly login with same username and password your licenses and configuration will be preserved you can start from where you left option 2 local deployment follow the same steps from section 1 > option 2 1\ open opedge device’s local ui in web browser via link as https //\<device ip address 8080> login the device & then click on “applications” & then “container” 2\ click on “+add” now instead of uploading the application from local file system you can make use of the available image stored on the opedge device click on “use existing image” 3\ select the bhdo application image and click on “next” 4\ once the upload is complete, below screen will be displayed, add the application “name” & click on “next” 5\ toggle the “enable network” and select “bridge” from the drop down click on “+add port” and map container port to host port as below 443 to 4443 & 4840 to 4840 then click on “next” 6 allocate the ram (4096 mb) and cpu cores (2) click on “next” 7 now add the container path “ /var ” and select the available volume from the drop down this is the path and volume mapped when you initially deployed the application on opedge device this step will make sure you pick up from where you left (preserving the licenses and configuration) 8\ environment variables are not required click on “next” 9\ advanced mode is not required, click on “next” 10 review the summary notice the container path and volume mapping click on “create” 11 now you can see the container is created and running in the application tab now follow same steps in section 2 bhdo application web ui you can access the bhdo app via local interface by inserting \[https //\[ip address of opeedge 8d] 443 in your web browser you can directly login with same username and password your licenses and configuration will be preserved you can start from where you left section 4 adding devices, tags, opc ua server, and client setup this section describes the the process of adding simulated devices and tags you can add them manually or use a json template if you have one adding the json template open the bhdo dashboard click on the “systems” icon on the left side panel then select the last option “templates“ now click on “upload template“ now browse the json file you want to upload and open it bhdo will start the upload process once the upload is complete you will get the “upload successful“ message navigate to bhdo dashboard and here you can see the number of devices and tags have updated along with that you can see “message broker and routing” number is also increasing 2\ adding devices and tags manually you can add devices and tags manually through “device hub” open the bhdo dashboard click on “device hub“ on the left side panel then click on the “+“ sign to add a device connect device screen will open now select the “device type“, “drive name“ in below case we are using simulator device with generator drive name the device add description click on “add device“ similarly, you can add multiple devices the new device will be in “connected“ state there will be 4 option on each device refresh, edit, stop, and delete now on the same screen select “tags“ option tags screen will open select the device for which you want to add tag/tags now select the “+“ sign on top right hand side and select “add a tag“ option add tag screen will appear fill in the details and click on “add tag” now you can see the tag will reflect on selected device’s tag list similarly, you can add multiple tags on a device 3\ opc ua server select the opc option from left hand side panel in the “hierarchy” section click on import from device hub option this will import the devices and tags from device hub now select the “management“ option from left hand side panel make sure the policy management and authentication management all selected as “none“ click on “configure” on the top right corner fill in the details as shown in below screenshot uncheck the “allow nodes under root” box then click “save“ now start the opc ua server by clicking on “start“ option on the top right hand corner confirm to “yes“ the opc ua server is running 4\ opc ua client here we are using the free uaexpert client software download and install on your machine open the uaexpert software, click on the “+“ to add the server in add server box under the “custom discovery” option double click to add server enter url box will open enter the address as “opc tcp\ //ip address of your edge device on which bhdo is running 4840” click on “ok” the client server connection is complete you can see edge devices under address space you can drag them to data access vie pane to monitor tags