...
Section | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The TCP/IP communication mode uses the TCP/IP communication protocol for all communication between an EDMthinClient and an EDMsixServer.
In the TCP/IP communication mode, the messages are transferred directly between the EDMsixServer and the EDMthinClient. The EDMserverContext used by the EDMthinClient simply needs to specify the host name and the service port number of the machine hosting the EDMsixServer™ process.
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.
...
Section | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The HTTP communication mode is used when the EDMserver can only be reached with HTTP communication due to the server side firewall configuration.
In the HTTP communication mode, the EDMthinClient will wrap all message blocks in a HTTP envelopes. This makes it possible to communicate through port 80 (or any other gate used for HTTP communication on the EDMsixServer side). The EDMsixServer can not unwrap these messages by it self. Therefore, this communication mode requires a web-application on the server side that strips off the HTTP envelopes before passing the messages on to the EDMsixServer. This web-application is called an HTTP Tunnel and must run on the EDMsixServer host.
The HTTP Tunnel must be specified in the EDMserverContext that goes with all messages that are transferred between the EDMthinClient and the EDMsixServer. An HTTP Tunnel is specified by three parameters in the EDMserverContext;
- HTTP Tunnel Hostname
- HTTP Tunnel Port Number
- HTTP Tunnel Name
...
Suppose the HTTP Tunnel web-application can be reached from a web-browser with the URL
...
http://139.168.32.13:80/demo1/servlet/EDMHttpTunnelServlet, then these parameters get the values;
- HTTP Tunnel Hostname = "139.168.32.13",
- HTTP Tunnel Port Number = "80" and
- HTTP Tunnel Name = "demo1/servlet/EDMHttpTunnelServlet".
If there is an Internet Proxy Server on the EDMthinClient side, the EDMserverContext must specify two additional parameters;
- HTTP Proxy Server Name
HTTP Proxy Server Port Number