13.4. Handling XML databases

The XML database in the ZMS is functionally divided into two parts and stores two basic types of information.

  • predefined information

    For example: proxies, packet filtering parameters or add-ons. This information is provided by Balasys but other definitions can also be freely added.

  • configuration settings of your sites, hosts or components

    These are the settings created in ZMC. The configuration files are generated on the basis of this data.

ZMS loads the database information from the /var/lib/zms library and places it in the appropriate part of the XML database. During database save ZMS carries out the reverse process: takes the data from the XML database and saves it in the appropriate file and folder of the library.

The /var/lib/zms is library is composed of the following folders and XML files.

  • zms_userdatabase.xml

    including the configuration settings created in the ZMC except for PKI information

  • zms_keymngt.xml

    including all PKI information and related user settings

  • configdb folder

    storing templates, databases, definitions necessary for the ZMS such as built-in proxies or other settings provided by Balasys (configuration settings are excluded)

    Note

    Do not change the files in this folder because during upgrade the content of the folder is automatically overwritten. Necessary modifications should be stored in the configdb-user folder.

  • configdb-user folder

    containing the additional settings and templates for the ZMS in separate XML files

    (These files are modified versions of the configdb/zms_database.xml file). This data is not deleted during upgrade.

  • keymngt folder

    containing certificate entities (certificate, key and CRL files generated by PKI)

    Note

    Do not modify this folder.

  • backup folder

    storing by default the backup of the XML files and folders

    For further information, see chapter Section 13.1.2, Configuring backup.