The various configuration tables present in Web NMS and the details about what they store are explained in this document.
ConfigTasks - Whenever a task gets defined, it gets stored in this table. This contains information like name of the task, protocol to be used when executing the task, etc. It also stores information like whether or not rollback is needed, the rollback document, etc.
ConfigTaskDetails - This also contains the task related details like the total number of attributes contained in a task, type of the attribute namely, group, table, columnar, etc.
ConfigAttributes - The attributes defined in a particular task are stored in this table.
PendingTasks - When the ConfigServer is shut down, the list of pending tasks available for execution at the time of shut down are stored in this table. Whenever the server gets restarted, it reads this table and starts the configuration again.
PendingDevices - Similar to storing the pending tasks, the pending devices over which configuration has to be performed is stored in this table.
DeviceList - Many devices can be grouped together so that the task can be executed over the group of devices at a later point of time. This grouping of devices are stored in this table.
DeviceListDetails - This contains the common properties of the device, like port to be used for configuration, value for timeout, retries, etc.
DeviceUserProps - This table contains the user properties specified for the device, like COMMUNITY in case of SNMP.
TasktoDeviceListMap - When a task is defined and devices are associated, the mapping between the tasks and device lists are stored in this table.
TaskAudit - This table is used to store the task level audit details. This contains information like task name, submitted time, device list, etc.
AttributeAudit - This table contains the audit at the attribute level and contains information, like the number of retries, ending time of execution, etc.
DeviceAudit - This table is used to store the device level audit details. This contains information, like device name, task name, starting time of execution, ending time of execution, etc. This also contains the status of configuration i.e., Success or Failure
ConfigProvider This contains the entries which are created by reading the configprovider.xml file and also contains the list of provider for the protocols used for configuring the device.
These tables are populated with the necessary data when the Web NMS gets started. The default tasks bundled with Web NMS are present under <Web NMS Home>/configtasks directory. When the Web NMS is started, these files are read and the corresponding database tables are populated.