.png?width=180&height=32&name=NW%20Logo%20(2).png){kind=small}
Core Service-to-Service Configuration Parameters
Core Service-to-Service Configuration ParametersCore Service-to-Service Configuration Parameters
This topic lists and describes the configuration parameters that control how a Core service connects to another Core service. For example, when a Concentrator connects to a Network Decoder, the connection parameters are controlled by these settings.
Whenever a Core service establishes a connection to another Core service, the service that acts as the client creates a new sub-folder in the /services folder of the configuration tree. The name of the sub-folder corresponds to the name of the service and has the form host:port. For example, the service connection folder for a Concentrator connection to a Network Decoder could be /services/reston-va-decoder:50004. Inside each service connection folder, there is a config sub-folder that holds configurable parameters.
The following list describes the Service Configuration parameters:
- Services: allow.nonssl.to.ssl
- /services/host:port/config: Allows a non-SSL connection to connect to a SSL service, when set to true. Otherwise, if false, non-secure to secure connections will be denied. Change takes effect immediately.
- Services: compression
- /services/host:port/config: Displays a config node that determines if data is compressed before sending. A positive value determines the number of bytes that need to be sent before it will be compressed. Zero means no compression.
- Services: crc.checksum
- /services/host:port/config: Displays a config node that determines if data streams are validated with a CRC checksum. A positive value determines the number of bytes that need to be sent before it will be CRC validated. Zero means no CRC validation.
- Services: ssl
- /services/host:port/config: Displays a config node that enables or disables SSL encryption on the connection.