XML Repository actions:

Comparison of XML files with the object configuration


Evaluation of comparison:

  1. If no XML files are selected, the comparison will end with error (step 14 follows).
  2. Displays the information on how many files will be processed.
  3. All XML files are read (if there are some wrong data in XML file, it is inserted among wrong files, otherwise CVS information will be required for XML file from D2000 Server).
  4. If no CVS information are required from D2000 Server, the comparison will end (step 14 follows).
  5. Displays the information on how many objects need CVS information from D2000 Server.
  6. Waiting for response from D2000 Server.
  7. Displays the information that the process starts processing of the CVS information.
  8. Evaluation of CVS information.
  9. If no object configuration is required from D2000 Server, the comparison will end (step 14 follows).
  10. Displays the information on how much object configurations are required from D2000 Server.
  11. Waiting for response from D2000 Server.
  12. Displays the information that the process starts to compare the obtained object configuration with XML files.
  13. A result of each comparison is ERROR, DIFFERENCES or OK.
  14. Displays the information that the action ended ok or with some error.

It holds:

  • number of requests to read data of XML files (all the XML files) is grater than:
    • number of requests to get the CVS information for the objects from D2000 Server (read XML files) and it is grater than:
      • number of requests to get the configuration for the objects from D2000 Server (XML files of which data need to be compared with the object configuration)

Note: When CVS information is required from D2000 Server the identification data for UID, ID = 0 and NAME are filled in. I.e. ID is ignored and the object of D2000 System is preferentially searched via UID.

Comparison of the object configuration with XML Repository


In this case, a placing of XML file is important. This placing is affected by setting for XML Repository. Mainly, it is the setting of the directory for XML Repository (if XML Repository is in a subdirectory the name of which is as the name of user) and the setting of the export parameter SUBDIR_EXP. XML file is, then, searched according to this path in XML Repository under the name <object_name>.xml. Changing of these settings much influence whether the XML file for the object in XML Repository is found or not.

Evaluation of comparison:

  1. If directory for XML Repository does not exist, the comparison will end with error (step 14 follows).
  2. If no objects are selected, the comparison will end with error (step 14 follows).
  3. Displays the information on how many objects will be processed.
  4. Displays the information on how many objects need CVS information from D2000 Server.
  5. Waiting for response from D2000 Server.
  6. Displays the information that the process starts processing of CVS information and searching XML files.
  7. Process tries to load XML files from XML Repository to the objects from configuration.
    • if XML file does not exist - object is not associated with XML file
    • if XML file exists - object is associated with XML file
    • if data of XML file contains some error - XML file is assigned to object as wrong
    • if data of XML file does not contain some error - XML fill is correctly assign to the object
  8. Evaluation of CVS information.
  9. If no object configuration is required from D2000 Serever, the comparison will end (step 14 follows).
  10. Displays the information on how much object configurations are required from D2000 Server.
  11. Waiting for response from D2000 Server.
  12. Displays the information that the process starts to compare the object configurations with XML files.
  13. A result of each comparison is ERROR, DIFFERENCES or OK.
  14. Displays the information that the action ended ok or with some error.

Displaying of the differences between XML file and the object configuration


This comparison can be initialized after the XML files was compared with the object configuration or the object configuration was compared with XML Repository.

Evaluation of comparison::

  1. If a program for comparison of two files does not exist, the comparison will end with error (step 12 follows).
  2. If the record does not represent a pair, the comparison will end with error (step 12 follows).
  3. If XML file was not read, the comparison will end with error (step 12 follows).
  4. Displays the information that the XML files will be compared with the object configuration.
  5. Displays the information that the process is requesting one object configuration from D2000 Server.
  6. Waiting for response from D2000 Server.
  7. Displays the information that the process starts to compare the object configuration with XML file.
  8. The result of comparison is ERROR, DIFFERENCES or OK.
  9. If the result is ERROR, the comparison will end with error (step 12 follows).
  10. If the result is OK and it was not possible to create the temporary files, the comparison will end with error (step 12 follows).
  11. If the result is OK and it was not possible to activate the program for data comparison, the comparison will end with error.
  12. Displays the information that the action ended ok or with some error.
Write a comment...