Gcom_ssd
|
Description - A Gcom-proprietary, stand-alone, application-level program Purpose - Convert legacy protocols to/from the SyncSockets® protocol using legacy APIs and the SyncSockets API. Other Names - SyncSockets Daemon, SSD Program Start - Use the Gcom Protocol Appliance browser-based interface. Recommended order for starting Gcom_monitor, Gcom_config, Gcom_ssd, and, if necessary, Gcom_pcd: Assign SSD, Assign Stack, Assign Application (for Gcom_pcd), Start all Ports. Message Exchange and Connections On the IP side, Gcom_ssd can exchange messages using the SyncSockets protocol with:
On the legacy side, Gcom_ssd exchanges messages with the legacy host/device using legacy protocols. A single Gcom_ssd can handle a virtually unlimited number of connections. Gcom_ssd, a custom application in the IP host/device (directly or via Gcom_pcd), and the legacy host/device can all initiate a connection. (Arrows in the following diagram show the connection initiation direction.)
More on Relationships Legacy protocol stack drivers - A single Gcom_ssd can communicate with multiple legacy protocol stack drivers because the decision as to whether a particular legacy protocol connection is, for example, SNA or X.25, is made on a per-connection basis. Gcom_ssd configuration file - When started, Gcom_ssd reads a configuration file containing parameters that tell it the listening port, how to behave as an application-level user of the legacy protocol stack drivers, system log file specifications, and connection definitions for legacy connections. Gcom_ssd log file - Gcom_ssd logs global events to help you diagnose installation, setup, and configuration problems. Gcom_config - Gcom_ssd manages connections to legacy protocol stack drivers built by Gcom_config. There are parameters in the Gcom_ssd configuration file, such as X.25 routing addresses and SNA LU numbers, that must match parameters in the Gcom_config configuration file. |
For more information... |
