Overview
It is possible to execute the Device Module Execute the Module Device in a Remote Computer. This single configuration allows , allowing an out-of-the-box setup for gateway and tunneling applications.
On this page:
Table of Contents maxLevel 3 style none
System Requirements
To try to use this feature,
the following requirements must bebe sure that these requirements are met:
- All computers must be on the same network.
- The product must be installed on both computers.
Security Measures for Remote Execution in a Secure Environment
Remote execution in a secure environment is a major concern for many organizations that want to protect their data and systems against external threats. In FactoryStudio, authentication and encryption are two fundamental security measures that can be implemented to ensure the security of data during remote execution. Authentication is a process that helps ensure that only authorized users can access the system. This can be done through passwords, access keys, or other authentication methods available in FactoryStudio. By implementing authentication, users can ensure that only authorized users can access the system and perform remote operations. Encryption is another important measure to protect data transmitted during remote execution. FactoryStudio supports strong encryption algorithms and digital certificates, allowing users to protect transmitted data against interception and reading by unauthorized third parties. By implementing security measures such as authentication and encryption in FactoryStudio, organizations can ensure that their systems and data are protected during remote execution in a secure environment. This helps minimize the risk of security breaches and ensures that confidential information remains protected at all times.
Using Remote Channels
To use the remote the Device Module, your project should use a communication protocol ir order to use this feature. Follow the steps below to enable the remote channel feature.
- Access Devices → Channels.
- Create a new channel clicking the plus icon.
- Once created, in the Initial State column, select the Remote option from the Combo Box.
- Now, in the Remote Settingscolumn, insert the IP Address where the device will run remotely.
| Note |
|---|
If the Remote settings |
How to Use
To enable this feature, your Project should use a Communication Protocol. In your Engineering environment, go to the Devices → Channel Tab, and create a new Channel for one of the protocols on the list.
Once a Channel is created, you will find a column called RemoteSettings in the configuration grid.
| Note |
|---|
If the column is not visible on the grid, you need to enable it by right-clicking the grid header , and selecting it from the list. |
In the Initial State column, select the Remote option from the ComboBox.
This feature is available for all available protocols.
. |
| Note | ||
|---|---|---|
| ||
Some protocol drivers must be executed by Windows Users that contain certain specific access permissions (e.g.: , PI) must be executed by Windows Users. This means that the TWebServer or IIS the TWebServices or IIS must be executed by the same same Windows User User (even when the Project runs as a service). |
Channel Configuration
To start the remote setup, go to the Devices → Channelstab. Under the RemoteSettings column, insert the IP Address where the device will run remotely.
This feature is available for all available protocols. If the Channel is either PI, Tundra or Prediktor, the tag's Historical Data that was configured in the Devices → Points tab is returned by the Remote Computer. Any other tab related to those Channel settings (Nodes and Points) are configured as they would be in a local configuration.
Project inRemote Channel Execution
Before running the Projectsolution, there are some important details that must be taken into account:
- The Remote Device will be executed remotely using the settings from the Device/Channels/RemoteSettings option.
The
ProjectSolution (TStartup) will connect to the remote computer that is running the TWebServer or IIS through the
ProjectServer. Format:SolutionServer. It will be formatted in an IP:
port (e.g.Port format (For example: 192.168.1.1:3100
- default port is 80).
Note TWebServices or IIS only needs to be executed on the Remote Computer.
- Windows Firewallor any other firewall in every router must enable some Inbound and Outbound ports on both computers.
- WebServices ports: 10108, 80, 3100, or other.
- TServer port
- : 3101 or other
- .
Once you launch the Project is launchedsolution, you will notice the following things.
- You will see a non-default message in
- the TStartup dialog window
- stating that the Module Device was started remotely.
- A process
- called TRemoteDevice can be found running in the Task Manager on the Server computer. This application is responsible for launching the Device Module on the Remote PC.
- On the Remote computer,
- you can
- see the same TRemoteDevice process running in the task manager. The command line for this process will show more information related to the Channel we are running on the remote machine, such as the Channel Name, Server’s IP, and Port Number.
In this section
...:
| Page Tree | ||||
|---|---|---|---|---|
|