]>
&moregen;
If you have ever tried using DCOM as a method of communication, you are probably aware of its shortfalls. Its inability to work well across NT domains and through firewalls have proved problematic for many businesses. ICONICS GenBroker™ solves these problems by opening up more communication options for your ICONICS system.

GenBroker Architecture

The GenClient / GenBroker™ architecture consists of two main parts:

GenClient.dll
GenBroker.exe

The GenClient.dll resides on the client side. It can communicate directly with OPC servers (using the traditional DCOM method), or it can establish a connection with GenBroker™, which then communicates with the OPC servers on behalf of the client. Unlike DCOM, GenBroker™ can communicate over the Internet.

DCOM is the method of communication for GENESIS32™. There are, however, certain disadvantages to using DCOM. To overcome DCOM timeout problems, for example, it was necessary to eliminate Windows callbacks and reduce the number of different function calls over Windows DCOM communications. DCOM's major disadvantages are:

Its complex settings often make its configuration ineffective when the client is remote.

It does not work well across NT domains.

Its connection over slow and unreliable networks (e.g., the Internet) is practically impossible.

It is not easy to configure to pass through firewalls.

In response to these difficulties, ICONICS has enhanced GENESIS32™ with GenBroker™, a proven, high-speed communications utility. Employing a network of applications, GenBroker™ uses TCP/IP and SOAP/XML channels to achieve real-time and secure communications between Web browser clients and WebHMI™ servers. Everything except the method of communication remains the same as before.

Communication Methods
OPC Direct Direct Channel Over DCOM Direct Channel Over TCP/IP Direct Channel Over SOAP/XML
Request/Response Protocols

The basic philosophy of GenBroker™ communications lies in its use of reliable Request / Response protocols: The client sends requests, and the servers reply to them. GenBroker applies to all GENESIS32™ applications. For example, a thin client sends out a request over the Internet to the WebHMI server. The thin client uses GenBroker to transmit the request. The WebHMI™ server's response to the request is also returned via GenBroker™. But if the thin client's request requires a response from a remote server in a local area network (LAN), WebHMI™ could be configured to use DCOM. The machine will use DCOM to return the response to the WebHMI server, which will use GenBroker™ to relay the response to the thin client.
GenBroker™ over The Internet

GenBroker™ technology has been incorporated to make the setup of Internet and intranet communications easier. In addition, GenBroker™ provides easier Internet connectivity and operation with firewalls and routers. GenBroker™ enables you to designate which method is to be used for networked communications, as well as to define a central License and/or Security server for a networked set of workstations.
Advantages

GenClient/GenBroker™ TCP communication has the following advantages:

It works well within, across, and in the absence of NT domains.

It works well on slow and/or unreliable networks (e.g., the Internet).

The client side works well behind a firewall.
GenBroker™ Configurator Remote Server Settings