História stránky

...

1. Loading of XML files.
2. The first parsing of XML data.
3. Matching of the objects and references with the target configuration:
   • matching of the imported objects with the target configuration
   • ID is assigned to new objects (insert) , if the ID reservation failed or ID was zero
   • matching of the object references with the target configuration
   • parent consistency check checking the consistency of the parents of the changed objects (update), but while the change is permitted only allowed:
     
     • for the object of  I/O
     tags
     • tag, Event, Database
     or Table
     • , Table, Eval Tag,  Alarm, Remote Tag, Historical Value types
     • for other types of objects (e.g. Line, Station) provided that the parent process (e.g. KOM) is stopped. If the parent of the object is directly a process (e.g. for objects of type Line), both the old and the new parent process must be stopped
       Note: check of parent process running in redundant systems is performed only on the HOT D2000 Server. If the parent process is running on the SBS D2000 Kernel, it will be stopped after the XML import is finished (and if Autostart is configured, it will be started again).
   • matching of the column references with the target configuration
4. Reading of the binary files.
5. The second parsing of XML data.
6. XML data import.

Kotva
parsing parsing

XML data parsing

...

Each XML file together with the proper binary files represents the object configuration that is to be imported.

...

• XML file structure must be correct
• each object reference <HOBJ_REF> in <REFERENCES> section must have:
  • filled name <name>
  • unique name <name> and <uid> (if it is filled) within this section
• each column reference <COL_REF> in <REFERENCES> section must have:  
  • filled name <col_name>
  • unique name <col_name> and <col_idx> (if it is filled) within this section
  • <col_idx> must not acquire the a value higher than MAX_VALID_COL_IDX = 7777
• the structure <tObjItemData> must be listed as the first in <CFGRECORDS> section
  • name <Name> of the structure must be filled
  • if the object in references refers to itself, its name must match with uid

If an object or column reference is found while parsing <CFGRECORDS> section (it was not found according to name in prepared references from <REFERENCES> section), it will be added automatically into <REFERENCES> section. It means , that the references from <REFERENCES> section are just a sort of some rule that is primary taken into consideration but the import may be done also without <REFERENCES> section.
This action is followed by a check whether all the objects (as individual elements) were changed from XML to the structures in memory. It only involves the check of objects (whether they are correct or not) regardless of their membership in the particular configuration.

...

An important element at matching is uuid in TObjItemData structure.
The second important element is Name in TObjItemData structure.

Warnings that may occur at matching:

...

The important element at matching is uid in HOBJ_REF structure.
The second important element is name in HOBJ_REF structure.
If the parameter IGNR_REFS is checked, the matching may be executed only through the second element.

...

The important element at matching is col_idx in COL_REF structure.
The second important element is col_name in COL_REF structure.
If the parameter IGNR_REFS is checked, the matching may be executed only through the second element.

...