A WebGateway is a type of security solution that prevents unsecured traffic from entering an organization's internal network. Businesses use a WebGateway to protect their employees/users from accessing and/or being infected by malicious web traffic, websites, or virus/malware.
The TWebGatewayService is an executable file that works in association with IIS (Internet Information Services). Below, you will find more detailed information regarding the installation process and regarding setting parameters.
To install the “WebGateway”, run the “InstallTWebGatewayService.exe” application. All the information for the WebGateway is in the TWebGatewayService.exe.config. This will create a windows service and all output will be sent to the windows event viewer. After any modification to the .config file, the windows service must be stopped and restarted.
When using additional ports (ExtraCount parameter), you need to configure the TWebGatewayService.exe.config file, and then execute the WebGateway installation. The executable “InstallTWebGatewayService.exe” will verify the TWebGatewayService.exe.config and install the additional ports on the Windows routing table. After you make modifications to the related additional ports, you must follow the steps below:
The available WebGateway parameters can be found below:
LocalPort : WebGateway listening port. If you are ONLY using Windows Authentication, set the parameters to zero (0) and the port will not be opened
LocalPortWA: WebGateway listening port using Windows Authentication. If you are not using Windows Authentication, set the parameters to zero (0) and the port will not be opened
RemoteIP : Computer IP that runs the runtime server (TServer.exe)
RemotePort : “TServer.exe” listening port without Windows Authentication
RemotePortWA: “TServer.exe” listening port using Windows Authentication
WA: Must use either RemotePort or RemotePortWA. It does not matter which port the data arrives in (LocalPort or LocalPortWA)
True = Use only Remote Port WA
False = Use only Remote Port
RuntimeUsersProject: [optional] Set which project (tproj) has the RuntimeUsers data table that will validate the users from SmartClient/RichClient
CheckRunTimeUsersWA: [optional] Set to validate the users from SmartClient/RichClient using Windows Authentication
True = Enabled (Runtime Using Project parameter cannot be used when True)
False = Disabled
TargetCF : [optional] This enables a project to be deployed in a Compact Framework environment (WindowsCE).
True = Enabled
False = Disabled.
ExtraCount: [optional] Number of additional ports. These ports will only route the incoming data in the LocalPort<#> to the RemoteIP<#> and RemotePort<#>.
LocalPort2: WebGateway listening port. It must start with #2.
RemoteIP2: Computer IP that is running the runtime service
RemotePort2: “TServer.exe” listening port
LocalPort3: WebGateway listening port
RemoteIP3: Computer IP that is running the runtime service
RemotePort3: “TServer.exe” listening port
RemoteIP<n>: Computer IP that is running the runtime service
RemotePort<n>: “TServer.exe” listening port
Since the line ”<! − −” and ”−− >” makes a comment block, it needs to be removed.
You can find any default values in the “TWebGatewayService.exe.config”.
The additional ports will not work with the parameters: LocalPortWA, RemotePortWA ,WA, Encrypt, RuntimeUsersProject, CheckRunTimeUsersWA and TargetCF.
When the WebGateway service is started, log messages are in the Windows EventViewer.
Below is a message similar to one of the log messages.
First redirect :: LocalPort: 3101, RemoteIP: localhost, RemotePort: 3101,RemotePortWA: 3102 Extra Redirection Table: Listen on ipv4: Connect to ipv4: Address Port Address Port --------------- ---------- --------------- ---------- 0.0.0.0 3100 192.168.80.129 3100 0.0.0.0 3102 192.168.80.129 3101