2.4 Audit Management Process for Change Events

Figure 2-1 provides an overview of how the Audit Management feature works for change events.

Figure 2-1 Change Events

The overall workflow to capture change events is as follows:

Step - Administrator enables the change events: The administrator logs in to ZENworks Control Center and enables the change events that need to be audited. For information about how to enable and configure change events, see Section 4.2, Enabling a Change Event.

Step - ZENworks Primary Server saves the configuration information in the ZENworks database: After the administrator enables the change events, the ZENworks Primary Server stores this information in the ZENworks database.

Step - ZENworks Primary Server queries the ZENworks database: When a change occurs in the Management Zone, the ZENworks Primary Server queries the ZENworks database to identify whether the change needs to be audited.

Step - Change event information is sent as an XML file to the Collection folder: If the change needs to be audited, the Primary Server stores the change event details in the Collection folder.

Step - ZENLoader collects the XML file from the Collection folder: After the XML file is stored in the Collection folder, the ZENLoader collects the file from the folder. The ZENLoader also checks for additional information related to the generated change events in the ZENworks database.

Step - ZENLoader stores the change event information in the audit database: The ZENLoader stores the change event information in the audit database.

Step - ZENworks Primary Server retrieves the generated change event details from the audit database and displays it in the Dashboard: The ZENworks Primary Server retrieves the details of the generated change events from the audit database and displays the details in the ZENworks Control Center Dashboard. For information about how to access the Dashboard, see Section 4.3, Viewing a Generated Change Event.