Using the SMAT API
The SMAT API can be used to save a message in other TPS contexts. As in the traditional SMAT database, you can write messages to a SMAT database at other locations in the engine; not only on the inbound and outbound protocol threads.
In the Tcl SMAT API, the user-defined SMAT database has these features (compared with the traditional IB/OB SMAT database):
- Full operations
- Multiple writers
- Resend mapping
- Trace storage
These behaviors are shared between the two types of SMAT database:
- Table schema is the same.
- SMAT history and cycle logic share the same configuration with the traditional IB/OB SMAT database.
- Encryption key is the same as the SMAT database, that is, the site name.
Additional points include:
- Tcl and Java TPS are supported for the SMAT API.
- External Tcl scripts, for example, Tcl in an hcitcl shell, are also supported.
- The Java TPS is through Tcl, not natively.
xltp
andjxltp
are not supported.