Examples are located in sm-sw-examples-xx.xx.xx.xx.zip in the sm-sw release bundle, where xx.xx.xx.xx is the current sm-sw release number. A README.txt file is available in the .zip file.
The Heartbeat file is a message file that is sent to Teradata every hour, communicating that TVI is still running at the site. It contains the site ID, heartbeat frequency, CMIC and Axeda version, Teradata ServiceConnect connection type, the last contact, next contact, and registration times, proxy type, source of the Heartbeat message, and source agent.
Alerts from Server Management represent existing or potential problems within the Teradata system. Server Management analyzes and summarizes groups of alert conditions that occur during problem conditions and creates summary alerts that identify the cause. The resulting alert summaries are sent to Teradata so that a service incident can automatically be generated.
Asset Baseline and Snapshot Files
The Asset Baseline (ABL) process gathers information on the system’s chassis to query their asset information. Asset information for the hardware and software components of the system are recorded in simple data bundle formatted files and sent to Teradata.
The Asset Snapshot automates the updating of asset data to Customer Services Infrastructure (CSI). Rather than requiring manual ABL be run after simple change controls such as upgrades or parts replacement, asset changes are automatically detected at periodic intervals and are reported as an asset snapshot that uses the simple data bundle schema.
The Asset Snapshot logic does not run while an ABL is in process or if the system is in failover.
Data bundles are scheduled or periodically-collected files containing information for the Support Analyst. The support data and an associated .xml file, which contains information about the support data, are zipped together into one file and sent to Teradata for processing and storage. The support data may be binary or human-readable and can be excluded by the Policy Server, as needed.