Skip to main content

Socket LAM Reference

This is a reference for the Socket LAM and UI integration. The Socket LAM configuration file is located at $MOOGSOFT_HOME/config/socket_lam.conf.

The following properties are unique to the Socket LAM and UI integration.

See the LAM and Integration Reference for a full description of all common properties used to configure LAMs and UI integrations.

mode

Specifies the connection mode.

In CLIENT mode, the Socket LAM will attempt to connect to the defined address and port. If the Socket LAM cannot make a successful TCP connection to the socket, it will continue to retry within a built-in time period. This means you can start the Socket LAM without the source being ready, and it will continue to try and connect until it gets a connection.

In SERVER mode, the Socket LAM opens the address and port number as a listening socket that can accept inbound connections. It will sit and wait until the source of the data establishes a TCP connection to the address and port, spawning a standard TCP socket on which to accept input.

Type

String

Required

Yes

Default

SERVER

Valid Values

CLIENT, SERVER

protocol_type

Connection protocol to use. You only need to define this if mode is set to SERVER. If mode is set to CLIENT the LAM connects using TCP protocol.

Type

String

Required

Yes, if mode is set to SERVER

Default

UDP

stream_mode

Determines how to treat suffix data.

Type

String

Required

No

Default

N/A

Valid Values

  • single: If data coming into this LAM is from one source, use this mode to ensure the LAM does not lose suffixes.

  • multiple: The LAM manages streams via the remote IP/hostname of the source, and cleans any streams up that are inactive for more than 1 hour.

  • unique: If data coming into the LAM is from multiple sources, each source (including the remote ports) has its own stream and thus its own dangler.

In this section: