Expanding the configuration data storage in the config-file
|
|
The interstation copying of the OpenSCADA configuration.
The module BD.DBGate.
The OpenSCADA configuration data storage in the configuration file by the functions TBDS::dataSeek(), TBDS::dataGet() and TBDS::dataSet(), expanded for work with the configuration XML-context, some common improved and fixed.
The configuration XML-context of the configuration functions applied for interstation copying of the main OpenSCADA configurators and in a new module BD.DBGate.
The interstation copying is the fastest way of transmitting-syncing OpenSCADA configuration from one local or remote station to other remote or local station by using the standard copying operations of the main OpenSCADA configurators 
QTCfg and WebCfgD. This function you can also use in the user procedures of OpenSCADA by the User API function cntrReq(), since this is just an expanding of the common service function "save" and "load" of the OpenSCADA control interface.
The new module BD.DBGate is a module of the subsystem "Databases" of locating-reflection databases of the remote OpenSCADA stations to local ones. In its work, the module uses the OpenSCADA self protocol and service functions of the subsystem "Databases". This module can be useful:
- in multiple-network accessing to the remote station DB, built on the local ones' basis like to SQLite, such transforming their to the network ones;
- in proxy-access to the remote station DB, built on the network DBMS basis, through the OpenSCADA control interface, what can be also secured, using SSL;
- in spreading between network stations the complex user area functions with DAQ and UI parts linked on DB, like to Prescriptions.
Other improvements and fixes of the configuration data storage in the config-file means:
- preventing from getting the previous value at loading from the config-file, by setting the default value;
- appending for changing-saving the defined entries in the config-file instead complete saving all their in the default DB;
- detection and correction of data losses with concurrence access to the SQLite database, when a minor error of the not started transaction "cannot commit - no transaction is active (1)" is generated, which, however, interrupts the data recording.
