Applies To:
  • CitectSCADA 7.0
Summary:
Pre v7.0 I used to customise my DNS section to redirect the WebClients (and normal Display Clients / SCADA Servers) to the externally accessable IP Address of my Router.

I used to have Port Forwarding setup in my Router, forwarding ports 2075-2078 to my Servers, and the following in my WebClient's INI:

Assuming:
[IOSERVER]
NAME=IOServerP
[SERVER]
NAME=CitectP

[DNS]
IOServerP=10.0.0.1:2078
CitectPAlarm=10.0.0.1:2076
CitectPReport=10.0.0.1:2075
CitectPTrend=10.0.0.1:2077

How can I achieve similar in v7.0?

 

Solution:

The DNS Section has been replaced in CitectSCADA v7.0 by having 'Network Addresses' defined within the project.

However, in situations like having a WebClient (or normal Display Client / SCADA Server) connect to Citect Servers on another LAN, via a Router, the [AddressForwarding] section has been added.

Also, please note that the Port Numbers required to be mapped have changed for v7.0. The following ports are now required.

Assumptions:
Cluster Name: Cluster1
Alarm Server Name: AlarmServer1
Trend Server Name: TrendServer1
Reports Server Name: ReportServer1
Trend Server Name: TrendServer1
IO Server Name: IOServer
Externally accessable IP Address of Router: 10.0.0.1

[AddressForwarding]
Cluster1.AlarmServer1=10.0.0.1:2076
Cluster1.AlarmServer1_AlarmProps=10.0.0.1:2080
Cluster1.ReportServer1=10.0.0.1:2075
Cluster1.TrendServer1=10.0.0.1:2077
Cluster1.IOServer=10.0.0.1:2082
Cluster1.IOServer_PeerPort=10.0.0.1:2078
 
Keywords:
 

Attachments