...
- The proxy server host name
- The proxy server port number
The TCP Gate
The TCP gate uses the TCP/IP communication protocol for all communication between EDMthinClients and the EDMsixServer. In the TCP/IP communication mode, the messages are transferred directly between the EDMsixServer and the EDMthinClient. You may therefore need to open the service ports through the fire walls.When the EDMsixServer is started, you must specify the service port number to use for TCP communication. Say you assign port 4500 to the EDMsixServer. Then you will need to keep this port open in the firewall. But you will also need to open as many successive port numbers as you have EDMapplicationServers running. With three EDMapplicationServers, you will need to open the ports 4500, 4501, 4502 and 4503.
The diagram below shows the communication through the TCP gate. The sample code block shows how to define a TCP Server Context with the EDMInterface API
Section | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The HTTP Gate
If your company's security is such that you cannot open service ports for TCP communication, you may have to use the HTTP gate.Then the HTTP packages are sent through the HTTP port in the firewall and redirected to the HTTP tunnel where the HTTP envelopes are stripped off before the message block is passed on to one of the EDMapplicationServers. This represents a performance overhead, so you should use the TCP gate whenever possible.
The diagram below shows the communication through the HTTP gate.
Section | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|