This article explains the sensor export format behavior in Enterprise Manager starting from Service Update 34 (SU34). It clarifies why XML is the only supported export format, why the exported file is not designed for human readability, and where alert configuration data is stored.
Why can I only export sensors in XML format?
Starting from Service Update 34 (SU34), Enterprise Manager supports only XML format for sensor exports.
The HTML, PDF, and RTF export options were intentionally removed as part of a product update. This change eliminates external library dependencies and simplifies export handling within the application.
From SU34 onward, XML is the only supported format for sensor documentation export.
Why is the exported XML file not easy to read?
The exported XML file uses an internal format designed for Enterprise Manager processing.
The system primarily uses this file for:
Backup
Migration
Re-import into Enterprise Manager
The export is not intended to serve as a human-readable audit report. Because the structure reflects the internal configuration model, the content may appear technical and complex.
Is there documentation that explains each XML field?
No.
There is currently no separate document that explains each XML tag or field in the exported file.
The XML structure directly reflects the internal configuration model used by Enterprise Manager. It is not designed as a user-facing schema document.
Can I extract alert configuration from the database instead?
No.
The Enterprise Manager database tables (for example, db_sensor_history and db_sensor_realtime) store runtime sensor data only, such as:
Severity
Sensor value
Timestamp
Server information
These tables do not store alert rules, thresholds, or notification configurations.
Alert configuration details are stored only in the Business View definition (XML format).