Configuring the CSC Gateway¶
The CSC Gateway enables communication across the boundaries of two TCP/IP networks. Via a CSC Gateway, for example, a client in network A can make a request to a server located in network B.
Requirements¶
- The CSC Gateway must be installed on a PC that has both access to network A and access to network B.
- Routing is only carried out on the five relevant server applications.
- Each time a client attempts to connect, a check is made to see whether it is authorized to do so. All authorized clients are entered in the configuration file on the gateway computer.
Info
The incoming and outgoing port for SecureConnect (VDogSecureConnect_Port and VDogSecureConnect_PortRemote) must be identical, otherwise it will not be possible for the clients to login to the CSC gateway.
Configuration of the gateway¶
The settings for the Gateway are configured using the INI file VDogGateway.ini. The file can be found under: {Drive}:\vdoggateway\VD$A\Configuration\
- Open the
VDogGateway.inifile using a text editor, for example Notepad++. - Implement the desired settings. Possible settings can be found in the following table.
- Save the data and close the text editor.
The CSC Gateway is configured via the [vdog_cs{n}] section.
The server for the configuration is specified under_n_. The following values apply for the entry:
- 1: when using a conventional server
If a value is entered for n that is outside the permitted numerical range, the [vdog_cs {n}] section and all key values belonging to it are not taken into account when the INI file is read.
| Key | Description | Value | Default |
|---|---|---|---|
| Enabled | Key for activating the CSC Gateway functionality. | Y/N | N |
| VDogAdminServer_Port | Key for configuring the port where the gateway for the AdminServer routing is situated. | {1024 to 65535} | 64001 |
| VDogAdminServer_PortRemote | Key for configuring the port via which the AdminServer of the octoplant server can be reached. Value is read out at runtime. | {1024 to 65535} | 64001 |
| VDogAdminServer_SvrRemote | Key for configuring the computer name of the octoplant server. Value is read out at runtime. Mandatory field | {computer name} | |
| VDogCheckInCheckOutServer_Port | Key for configuring the port on which the gateway waits for CheckInCheckOutServer routing | {1024 to 65535} | 64002 |
| VDogCheckInCheckOutServer_PortRemote | Key for configuring the port via which the CheckInCheckOutServer of the octoplant server can be reached. Value is read out at runtime. | {1024 to 65535} | 64002 |
| VDogCheckInCheckOutServer_SvrRemote | Key for configuring the computer name of the octoplant server. Value is read out at runtime. Mandatory field | {computer name} | |
| VDogScheduler_Port | Key for configuring the port on which the gateway waits for Scheduler routing | {1024 to 65535} | 64003 |
| VDogScheduler_PortRemote | Key for configuring the port via which the octoplant server's Scheduler can be reached. Value is read out at runtime. | {1024 to 65535} | 64003 |
| VDogScheduler_SvrRemote | Key for configuring the computer name of the octoplant server. Value is read out at runtime. Mandatory field | {computer name} | |
| VDogOsServer_Port | Key for configuring the port on which the gateway waits for OsServer routing | {1024 to 65535} | 64004 |
| VDogOsServer_PortRemote | Key for configuring the port via which the octoplant server's OsServer can be reached. Value is read out at runtime. | {1024 to 65535} | 64004 |
| VDogOsServer_SvrRemote | Key for configuring the computer name of the octoplant server. Value is read out at runtime. Mandatory field | {computer name} | |
| VDogApi_Port | Port on which the gateway waits for API routing. The value specified here must be identical to the value of VDogApi_PortRemote. | {1024 to 65535} | 64023 |
| VDogApi_PortRemote | Port on which the API of the octoplant server can be reached. Value is read out at runtime. The value specified here must be identical to the value of VDogApi_Port. | {1024 to 65535} | 64023 |
| VDogApi_SvrRemote | Computer name of the octoplant server. Value is read out at runtime. Mandatory field | {computer name} | |
| IpAddressesClient | Key for configuring the computer names/IP addresses of participants (= clients) that are allowed to communicate via the gateway. Value is read out at runtime. Multiple entries are separated by commas. Wildcards (?/*) are accepted. Mandatory field | {computer names/IP addresses} |
Make the following settings in the [Logging] Section:
| Key | Value |
|---|---|
| DebugLog | Absolute path to the log file. Logging is activated by setting the key. |
Example configuration¶
[Logging]
DebugLog=C:\vdoggateway\debug.log
[SimaticNet]
Enabled=N
[vdog_cs1]
Enabled=Y
VDogAdminServer_SvrRemote=vDogServer1
VDogOsServer_SvrRemote=vDogServer1
VDogCheckInCheckOutServer_SvrRemote=vDogServer1
VDogScheduler_SvrRemote=vDogServer1
IpAddressesClient=10.0.100.1,10.0.100.2,10.0.*.3
[SimaticNet]
Enabled=N
[vdog_cs2]
Enabled=Y
VDogAdminServer_Port=64201
VDogAdminServer_SvrRemote=vDogServer2
VDogCheckInCheckOutServer_Port=64202
VDogCheckInCheckOutServer_SvrRemote=vDogServer2
VDogScheduler_Port=64203
VDogScheduler_SvrRemote=vDogServer2
VDogOsServer_Port=64204
VDogOsServer_SvrRemote=vDogServer2
IpAddressesClient=10.0.100.1,10.0.100.2,10.0.*.3