Gcom_pcd

Description - A Gcom-proprietary, stand-alone, application-level program

Purpose - Convert Gcom® Data Tunneling protocol to/from Gcom SyncSockets® protocol using an encapsulation or the Data Tunneling API, and the SyncSockets API.

Other Names - Protocol Converter Daemon, PCD

Program Start - Use the Gcom Protocol Appliance browser-based interface. Recommended order for starting Gcom_monitor, Gcom_config, Gcom_ssd, and Gcom_pcd: Assign SSD, Assign Stack, Assign Application (for Gcom_pcd), Start all Ports.

Message Exchange and Connections

On the IP side, Gcom_pcd can exchange messages using the Data Tunneling protocol with:

  • An IP host/device with a Gcom-supported encapsulation
  • And/or a custom application (in an IP host/device) created using the standard Sockets library or the Gcom Data Tunneling API

On the legacy side, Gcom_pcd exchanges messages with Gcom_ssd (which ultimately communicates with the legacy host/device) using the SyncSockets protocol.

A single Gcom_pcd can handle a virtually unlimited number of connections to handle message exchanges.

Gcom_pcd, the IP host/device, a customer or custom application in the IP host/device,, Gcom_ssd, and the legacy host/device can all initiate a connection. (Arrows in the following diagram show the connection initiation direction.)

Gcom_pcd, IP host/device, custom application, Gcom_ssd, and legacy host/device can initiate connection.

More on Relationships

Gcom_pcd configuration file - When started, Gcom_pcd reads a configuration file containing parameters that tell the default encapsulation method, TCP to Gcom_ssd route(s), and system log file specifications..

Gcom_pcd log file - Gcom_pcd logs global events to help you diagnose installation, setup, and configuration problems.

  

Click here for larger Solution Architecture diagram.

For more information...