[dist]

[dist] connectDp

Type: string
Default: _DistConnections

Defines the default name for the internal connections datapoint of the type _Connections, which contians a list with all managers to which the Dist manager has an established connection.

[dist] distDpName

Type: string
Default: _DistManager

Sets the name of the internal DP. The DP must be of the type _DistManager.

[dist] distPeer

Type: string

distPeer = "host1[:port1][$host2[:port2]]" System number [UTF8]

Specifies the hosts and the system number the distribution manager will connect to as a "client" (the other system is the "server"). If the other system is redundant both host names are separated by a dollar sign $.

Caution:

The order, in which the hosts are set in the config file, must always be the same. This means that if e.g. the hosts are set as follows in the data config entry:


data = "host1-1,host1-2$host2-1,host2-2"

the hosts in the distPeer config entry must be set in the same order:


distPeer = "host1[:port1][$host2[:port2]]" system number [UTF8]

Another order (distPeer = "host2[:port1][$host1[:port2]]" system number) causes connection failures.

As an optional third parameter the literal UTF8 can be supplied: its presence means that the remote party (server) uses UTF-8 character encoding. The absence of this parameter implies usage of ISO encoding at the other party. This parameter is only available starting with v3.16, and it is required when the server we want to connect to is a pre-3.16 using UTF-8 character encoding. As versions >=3.16 are less restrictive in terms of language configuration, this setting allows systems in a distributed configuration to use the same languages, but different character encoding. Versions prior to 3.16 are not prepared for this, therefore this information is sometimes (again, when client is >=3.16 but server is <3.16) necessary to be configured explicitly by the engineer using this optional parameter.

[dist] distPort

Type: int
Default: 4777
Range: > 0

Specifies the port numbers that the distribution manager uses to accept connections from other systems. The default value is port = 4777. Note that you do not have to define the port numbers if your projects run on different computers. If your projects, however, run on the same computer, you have to define the port numbers.

[dist] enforceAccessControl

Type: boolean
Default: 1
Range: 0|1

Enables communication between SSA projects and older projects without SSA (<=3.15).

For the server-side authentication, see chapter Server-side Authentication for UI Managers Configuration), use the entry "enforceAccessControl=0" where an SSA project communicates with an older SSA project.

Note: Projects >3.15 always need the same plugin loaded.

[dist] maxSystemsToInitialize

Type: int
Default: 0
Range: >= 0

Defines the maximum number of foreign systems which can be initialized (= exchange of the DP identification) simultaneously. If the number is exceeded, each initialization will be rejected and not accepted until the number of running initializations falls below "maxSystemsToInitialize" - this can be achieved by closing the initializations. Note: maxSystemsToInitialize = 0 means that an unlimited number of simultaneous initializations is allowed.

[dist] maxUpdateMsgCount

Type: unsigned
Default: 1000
Range: >=0

This entry specifies how many identification changing messages the dist manager will buffer. If there are more messages as specified in the queues the dist manager will remove some messages. When a remote system connects to the dist manager and request the identification the dist manager will try to send only updates from these queues. Only if the request cannot be satisfied this way the dist manager will send the entire identification.

[dist] requestIdDelay

Type: int
Default: 0
Range: >= 0

Time between receiving of an idnetification and the request of the next one. With this setting one can stack the distribution of the identification in the event manager, i.e. give the Event enough time to distribute one identification to all clients before the identification of the next system is requested.

[dist] updateStatusForHiddenSystems

Type: bool
Default: 0
Range: 0|1

If the one-way-dist is used, the dist manager is enabled to request the identification only from certain systems but still connect to all systems (see the config entry distSystemIds). Therefore, the systems or their managers still know if the partner system is connected or not. However, due to the lack of the identification, the system is not shown in the system overview panel and you cannot access the data points. The config entry "updateStatusForHiddenSystems" can be used for systems that are not included in the distSystemIds list. With the updateStatusForHiddenSystems you activate the status updates for the identifications of these systems (see also chapter One Way Dist).