CygNet Service Endpoints
The remaining sections of the sample_appsettings.json file define information about the sources, including each name, role, what type of data each endpoint provides, the data format, protocol, and data retrieval information. There must be an endpoint section for each of the CygNet services you wish to query:
Each service is identified in the endpointConnections object in the gateway section of the appsettings.json file.
Note: The following table lists all common properties found in each endpoint section of the appsettings.json file. For service endpoints with unique data retrieval properties, this will be noted, and linked to the endpoint topics that follow. Properties are listed in the order they appear in the sample_appsettings.json file. Use the search or link to find a particular property.
| Property | Description | Required | Property: Value Example | |
|---|---|---|---|---|
|
The root object that contains the name of the endpoint, specified in endpointConnections. |
yes |
|
||
|
The function performed by the endpoint. Possible values include:
The publisher endpoint role must be set to "Target" and the CygNet service endpoints' role must be set to "Source". |
yes |
|
||
|
Defines the data format of the source or target data. Contains required and optional members. |
yes |
|
||
|
type |
Specifies the dataFormat type. Possible values include:
|
yes |
See dataFormat. |
|
|
Specifies the format of the transaction data published from a DDS endpoint only. Possible values include:
|
no |
|
||
|
Contains service protocol information including type, hostname, and port number. |
yes |
|
||
|
type |
Specifies the protocol type. For CygNet service endpoints the protocol type is "CygNet". Formerly "CygNetDevice" or "CygNetHistorian", is deprecated but supported for backwards compatibility. |
yes |
See protocol. |
|
|
hostname |
The host name of the endpoint. Possible values include:
The hostname is required for the target endpoint and the CVS endpoint but is optional for the VHS and DDS endpoints. Since this hostname is in the service endpoint, the value is the Site Service endpoint name.
|
yes & no |
See protocol. |
|
|
port |
The port number for the source or target host. Possible values include:
The port is required for the CVS endpoint but is optional for the DDS and VHS endpoints. Since this port is in the service endpoint, the value is the domain of the CygNet Site.Service.
|
yes & no |
See protocol. |
|
|
Defines the data to be published from the CVS, VHS and DDS. See each endpoint, which contains different objects:
|
yes |
|
||
|
data continued |
|
yes |
|
|
|
data continued |
|
yes |
|
|
|
The default global frequency (in ms) used to poll data specified in the publish object of each endpoint. Used when a publishobject does not specify its own pollingFreq value. The minimum value is 200 (ms). |
no |
See data. |
||
|
The default global value used to determine how data is sent to the server in the case of intermittent communication failure. The defaultQualityOfService is a way of specifying the quality of service (QoS) of the MQTT protocol and is used when a publish object does not specify its own qualityOfService value. Possible values include:
Note: If the endpoint type is "AWS", only Low or Medium values can be used. If a High value is configured, the value will be changed to Medium. |
no |
See data. |
||
|
Determines how the real-time point type and value is published for the CVS endpoint only. Possible values include:
Link applies the following logic when strictPointValues is configured in the appsettings.json file.
Note: strictPointValues is not supported for history rollup points in 9.4.2000. |
no |
See data (for the CVS endpoint only). |
||
|
Determines if point data is missing, disabled, or other security errors prevent data from getting published for the CVS endpoint only. Possible values include:
Link applies the following logic when strictPointValidation is configured in the appsettings.json file.
strictPointValidation relates to the environment mode setting (Edge vs SCADA):
Note: strictPointValidation also applies to history rollup, when rollup is defined in appsettings.json file, but a point is not configured to report to VHS. |
no |
See data (for the CVS endpoint only). |
||
|
Specifies the maximum number of points that Link can publish at any point in time. Note: The recommended maximum amount of data that Link can publish at any point in time is 200,000 points across all CVS service endpoints in each Link instance. If you plan to publish more than 200,000 points, ensure that the system has sufficient CPU and memory to process the total amount of data, as attempting to publish too many points can severely impact a system's performance. |
no If pointLimit is not defined, Link will look at the limit from the license file. |
See data (for the CVS endpoint only). |
||
|
Specifies the frequency (in ms) used to query the PNT service for any new DynaCard points that will be published from the VHS. Configured for a VHS endpoint only. |
no |
See data (for the VHS endpoint only). |
||
|
Specifies the data to be published to the target from the CVS, VHS, and DDS endpoints. The contents of this object depend on the type of endpoint: |
yes |
More:


