Remote Services: Advanced Gateway Connections¶
This section outlines how to access Devices located in secondary Device Networks, which comprises their onboarding and the setup of involved gateways.
Note
- The setup and configuration of this documentation's reference tenant, its users, Sites and Devices can be found in chapter Sample setup used in documentation.
- The product structure and the protocol routing capabilities of the individual optional capability packages are described in chapter Product structure and procurement.
Example: Administrator Creates Protocol Application for RDP into Secondary Device Network¶
A Protocol Application is a template for assigning a particular access protocol to a particular devices. We start with creating an RDP Protocol Application, which will be used for Devices in secondary Device Networks. Please click "Create New Protocol Application".
Now you see the RS Protocol Hub, which displays the protocols you may use. Please note, that the protocols are tagged with the MRS Option package they belong to. Click "Remote Desktop Protocol".
Now we name the Protocol Application as RDP login Asia and specify aspects such as the default user name (here: userasia), that will be used for the RDP login itself. Click "Save".
The newly created Protocol Appliation RDP login Asia is now available and awaits assignment to Devices.
Example: Administrator Configures Device Endpoint as Gateway into Secondary Device Network¶
In order to connect to Devices in secondary Device Networks we now configure a Device Endpoint on a Device in a primary Device Network as a gateway.
Note
Please ensure, that the secondary network can be reached by configuring your network setup accordingly.
Select the blue hexagon in the top left corner to open the organizational device tree. Then navigate to Device PC i01. Then edit this device via and configure its Device Type as Gateway. Complete this action by pressing "Save".
The device page of PC i01 does not show any Assigned Devices in its bottom right dashboard. Press "Create New Device" to launch the menu for creating Devices in secondary Device Networks.
In the following menu we create a Device named HMI i01 and set its Device Type to Secondary Target. Please provide additional information such as the device's IP address. When done, press "Save".
The device page of PC i01 now displays HMI i01 as an assigned device residing in a secondary Device Network.
We now assign a Protocol Application to HMI i01 so that one may connect to it. Press "Assign Protocol Application".
In this example we selected RDp, so that it shows up on the right hand side of the menu. Press "Save" to complete the action.
The chosen protocol RDP was successfully assigned to Device HMI i01 and is ready for use.
Example: User Establishes RDP to HMI in Secondary Device Network¶
We assume that User Europe is a remote technician, who now wants to connect HMI i01 via an RDP session to perform some maintenance tasks. In the beginning, there is no connection established. Press the blue "chain" button to launch the connection.
The RDP launcher pops up - press "Connect".
Then provide the credentials associated with the RDP user name configured in an earlier step.
Accept the connection request.
The RDP windows opens now providing the trigged access.
Example: Site Owner Disconnects All Devices at a Site¶
Users with the role of Site Owner have a special responsibility for all the Devices within their site. Thus, they may disconnect an entire site including all its devices from RS by using a special Lock Connectivity button function. This is available in RS UI V1 under tile "System Management" and then selecting the site to be disconnected from the device tree on the left.
