SMAT
The Saved Messages Administration Tool (SMAT) utility is for users to manipulate messages recorded by the engine, with these restrictions:
- Messages in a SMAT file can be deleted.
- Messages in the SMAT database cannot be deleted.
- Messages in both the SMAT database and SMAT file cannot be modified.
SMAT deals with all inbound and outbound messages that are saved through the Network Configurator. These are placed in two files collectively called the "saved message file."
The saved message file consists of these files:
- Index file (.idx)
This contains information about the messages.
- Message file (.msg)
This contains the body of the messages.
There is only one recovery database in a system site, but there are separate inbound and outbound saved message files for each connection.
The saved message file is written to the file specified in the network configuration file and is relative to $HCISITEDIR/exec/processes/process_name. Use the Inbound and Outbound tabs on the Network Configurator to specify where the engine saves the messages.
SMAT saves messages in a viewable message file. For interaction purposes, each message in the file is given a sequential number starting with zero. These sequence numbers are not used by other tools.
The SMAT files can be cycled based on the file size. Cycled files are kept as history data. You can configure the cycling options and history settings from the GUI.
SMAT files can also be cycled based on date and time. This is also available for cycling process logs.
See SMAT history.
The current SMAT files are not compatible with earlier versions of the
GUI. hcismatconvert
is a tool that converts SMAT files
between formats: old to new, or new to old.
See hcismatconvert.
Symbolic-linked SMAT and SMAT database files outside of HCIROOT
You can move SMAT files to locations outside the Cloverleaf root directory. These files can be opened from any location.
Types of SMAT
You can select file-based SMAT or database-based SMAT.
File-based SMAT is configured through the SMAT GUI. This is maintained for backward compatibility.
Database-based SMAT is configured through the SMAT database GUI. The system engine stores SMAT messages in a SQLite database in an encrypted form. This tool implements cross-database search per the user’s needs.