The template of processing input initiative connections expands early one template initiative connections processing for the associated output transports by complete representing data of the remote OpenSCADA hosts on some aggregation server and with a possibility of control the remote hosts through the server, that is finishing the conception of data acquisition in the passive mode and the initiative connection.

The template does in whole:
- detecting a new connection from remote host, which has no ID;
- sending an acquaintance direct request to the established connection for getting KEY of the host, when it was already connected early, and for getting information about the host for creating ID of the host;
- setting ID for the connection;
- creating a record in the OpenSCADA hosts table for the connection and sending all followed requests already through the host;
- creating on the remote host a representative Logical Controller;
- creating on the remote host a representative DAQ.System Controller Object in the automatic mode, at missing any other there;
- processing the present DAQ.System Controller Objects to link the Logical Level parameters to them and creating some processing logical parameters;
- writing the generated key by a line "SrcKey: {KEY}" to description of the Logical Controller as a sign of finalising the initialisation;
- creating a Controller Object in DAQ.DAQGate with connection to the remote Logical Controller.

ID of the remote host is formed in the view "{HostDomain}{StatName}{RandKey}" and with limiting to 20 symbols, where:
- {HostDomain} — network host name-domain;
- {StatName} — station name of the OpenSCADA project;
- {RandKey} — random key in sixth digits.

Data model of the representative Logical Controller can contain both the generated links with processing parameters, and custom parameters, when the user is decided to publish some extra data. The generated items from DAQ.System are represents sources currently:
- "CPU", "MEM", "sensors", "Power", "uptime" => links in the "System (SYS)" container parameter;
- "fs", "hddstat", "hddsmart" => links in the "Disk (DISK)" container parameter with a processing one for "hddsmart" by the template base.DiskSMART;
- "netstat" => links in the "Network (NET)" container parameter;
- "ups" => links in the root with a processing one by the template base.UPS.

The aggregated data in DAQ.GAQGate can be lifted to up, or used in derivative DAQ objects, or whether directly on custom frames, or in future on a Dynamic Frame, which scheduled to implement; and without any additional action you will get notification about violations on the hosts.

Author: Roman Savochenko <roman@oscada.org>
Version: 1.1.0
License: GPLv2