Running the probe in either Server mode or Client mode
The probe can be configured to operate in either Server mode or Client mode by setting the SocketMode property. By default, the probe operates in Server mode.
In Server mode, the probe operates as a multi-headed server that can accept connections from multiple devices using TCP/IP and receive events sent to it. To run the probe in Server mode, set the SocketMode property to Server. In Client mode, the probe connects to the target system and listens on the socket to which the target system writes its event data; the probe receives ASCII data in the form of an element value followed by a carriage return or new line characters. To run the probe in Client mode, set the SocketMode property to Client.
Most properties are common to both Server and Client probe modes of operation. However, the way certain properties are set is determined by the mode in which you are running the probe.
The following properties are only configurable when the probe is running in Client mode:
- ChatinString
- ChatoutString
- EndpointSocketHost
- EndpointSocketPort
- ProtocolHeartbeatString
The following properties are only configurable when the probe is running in Server mode:
- EventReadString
- IdleConnectionTimeout
- LoginScript
- LocalSocketHost
- LocalSocketPort
For details of all these properties, see Properties and command line options.