Citect SCADA allows you to temporarily transfer the communications of a server to another computer to assist with hardware maintenance and system analysis.
By including an address forwarding section within a Citect.ini file, you can override a server's project-configured address, redirecting network traffic to a different address and port.
For example, if you would like to test a new server before adding it to a project configuration, you could make the necessary address forwarding adjustments within the citect.ini file of a single client to direct it to the new hardware. The server could be tested within the context of a system without having to recompile the project.
You need to make the necessary adjustments within the citect.ini file for every computer that is likely to be impacted by address forwarding.
For example, if you have a computer configured to run two I/O Servers, and you would like to temporarily redirect one of them, then both server machines and every connecting client need to have the necessary address forwarding adjustments made to their citect.ini files, so that the servers are aware of each other.
Address forwarding is implemented using the following syntax within a citect.ini file:
[AddressForwarding]
<ClusterName>.<ServerName>=<ipaddress>:<port>
You can also redirect the Peer Port connection for an I/O Server using the following syntax:
[AddressForwarding]
<ClusterName>.<ServerName>_PeerPort=<ipaddress>:<port>
For Alarm Servers which have an additional Database Port, you can redirect it using the following syntax:
[AddressForwarding] <ClusterName>.<ServerName>_AlarmDBPort=<ipaddress>:<port>
Address forwarding is only interpreted and used during startup of Citect Runtime. It is recommended (but not necessary) that the Setup Wizard is run before running up a project to confirm your changes.
|
UNINTENDED EQUIPMENT OPERATION
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
Note: The Citect SCADA Web Client uses address forwarding to manage communication across corporate firewalls. Any manual adjustments may also impact the ability to connect a Web Client to a deployment on a Web Server.
Published June 2018