Secure communication gateways for multi-site deployments.
Parent Page: Installation & Licensing (Reference)
TSecureGateway Overview
Secure Multi-Port Gateway manages communications between multiple projects, nodes, and systems.
Architecture Benefits
- 1-to-1 Communications: Direct single site connections
- 1-to-Many Communications: Multiple sites to master project
- Traffic Control: Only authorized traffic between designated points
- Site Isolation: Sites remain separate from each other
- Security: All communications encrypted and authenticated
Example: Business-level project sending requests to any site in a group, with traffic handled via Secure Gateway.
Installation
Basic Setup
- Run
InstallTWebGatewayService.exe
- Configure
TWebGatewayService.exe.config
- Service created in Windows Services
- Logs appear in Windows Event Viewer
Multi-Port Setup
When using additional ports:
- Stop service:
cmd
InstallWebGateway /uninstall
- Modify
TWebGatewayService.exe.config
- Reinstall with port configuration:
cmd
InstallWebGateway
The installer reads config and updates Windows routing table.
Configuration Parameters
Core Parameters
Parameter | Description | Default/Notes |
---|---|---|
LocalPort | Gateway listening port | Set 0 for Windows Auth only |
LocalPortWA | Windows Auth listening port | Set 0 if not using |
RemoteIP | TServer.exe computer IP | Runtime server location |
RemotePort | TServer.exe port | Without Windows Auth |
RemotePortWA | TServer.exe port with WA | Alternative to RemotePort |
WA | Authentication mode | True = Windows Auth only |
Optional Parameters
Parameter | Description | Usage |
---|---|---|
RuntimeUsersProject | Project with RuntimeUsers table | Validates SmartClient/RichClient users |
CheckRunTimeUsersWA | Validate with Windows Auth | Cannot use with RuntimeUsersProject |
TargetCF | Compact Framework support | For Windows CE deployment |
Multi-Port Configuration
Configure additional routing with ExtraCount
:
xml
<add key="ExtraCount" value="3"/>
<add key="LocalPort2" value="3100"/>
<add key="RemoteIP2" value="192.168.1.100"/>
<add key="RemotePort2" value="3101"/>
<add key="LocalPort3" value="3200"/>
<add key="RemoteIP3" value="192.168.1.200"/>
<add key="RemotePort3" value="3201"/>
Pattern continues for LocalPort(n), RemoteIP(n), RemotePort(n).
Service Management
Starting the Service
Start from Windows Services or command line:
cmd
net start TWebGatewayService
Verification
Check Windows Event Viewer for startup log:
First redirect :: LocalPort: 3101, RemoteIP: localhost, RemotePort: 3101
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
Monitoring
- Windows Event Viewer for logs
- Performance Monitor for traffic
- Network traces for debugging
Configuration Examples
Single Site Gateway
Basic 1-to-1 connection:
xml
<add key="LocalPort" value="3101"/>
<add key="RemoteIP" value="192.168.1.100"/>
<add key="RemotePort" value="3101"/>
Multi-Site with Windows Auth
Master connecting to multiple sites:
xml
<add key="LocalPortWA" value="3102"/>
<add key="WA" value="true"/>
<add key="ExtraCount" value="2"/>
<add key="LocalPort2" value="3200"/>
<add key="RemoteIP2" value="site1.local"/>
<add key="RemotePort2" value="3101"/>
<add key="LocalPort3" value="3300"/>
<add key="RemoteIP3" value="site2.local"/>
<add key="RemotePort3" value="3101"/>
Limitations and Notes
- Windows Authentication disables multi-port functionality
- XML comments use
<!-- -->
syntax (remove when editing) - All config modifications require service restart
- Default values in
TWebGatewayService.exe.config
- Each additional port requires unique LocalPort number
- RemotePort can be same across different RemoteIPs
Troubleshooting
Issue | Solution |
---|---|
Service won't start | Check Event Viewer for errors |
Port conflicts | Use netstat to find conflicts |
Connection refused | Verify firewall rules |
Authentication fails | Check WA parameter matches client |
Routes not working | Reinstall after config changes |