Create a Gateway

The DINGO-Manager connects to DINGO devices with the help of information stored in a so called Gateway entity. A new gateway can be created in the System Tree.

Note: The Details module has to be loaded, so that creating a gateway is possible. Go to the top menu and select View then Details.

In its simplest setup, the user will assign a name and the IP address of the DINGO device, to the gateway.

Gateway Type: Is always set to DinGo gateway when working with DINGO devices.

Gateway name: Is the name of the gateway.

OPC2Net Server, OPC2Net Topology, GW unique ID, GW key, Logging interval and Channels are not used when working with DINGO devices.

Connects via: The type of connectivity to use when connecting to the DINGO device. TCP/IP is most commonly used.

Router/Gateway: What connectivity the DINGO device supports if it is set up as a router .

IP address/domain: The IP address of the DINGO device that we want to connect to. A domain name or hostname can also be used if that works.

Port: The port to connect to. 80 is set as default. Port 80 is used for HTTP traffic and port 443 is used for HTTPS traffic.

User ID:If the connection is set to use HTTPS and an internal or external authorization server is enabled, then the user name used in the OAuth2 flow: Resource Owner Password Credentials Grant goes here.

Password: If the connection is set to use HTTPS and an internal or external authorization server is enabled, then the password used in the OAuth2 flow: Resource Owner Password Credentials Grant goes here.

Device at server side: If the DINGO device is not accessible on the local network, but instead on the remote location where the Go-IoT Cloud system is hosted, then this option should be chosen .

Use web proxy server: If the DINGO is only accessible via a web proxy server that the Go-IoT Cloud system can access, then this option should be chosen .

Proxy server: Choose a predefined proxy server from the combo-box or click the ... button to edit or create new proxy server definitions.

Note: The SilverLight plugin has the limitations, that it can not do proxy request client-side. So the web proxy servers have to be accessible by the Go-IoT Cloud system which is server-side.