Tcl SMAT API
Because of the audit role of SMAT, for inbound, users can see exactly what was received in the NetConfig configured SMAT archives. For outbound, users cannot. The message that is saved is the one before encoding was applied because it is resent to an OB pre/post SMS queue. Encoding back to UTF-8 to insert into that queue can introduce anomalies.
When encoding is involved, you can use the SMAT API to save the post-encoded messages and view exactly what is being sent.
A Tcl interface has been implemented to store those messages into the SMAT database.
The SMAT API accesses the traditional IB/OB SMAT database, which is defined on the GUI to script actions that are based on the content.
You can save inbound/outbound messages into the SMAT database using the traditional IB/OB SMAT database. The SMAT API can save messages with other TPS contexts into an additional user-defined SMAT database that is separate from the traditional IB/OB SMAT database.
The user-defined SMAT database has these features (compared with the traditional IB/OB SMAT database):
- Full operations
You cannot use the SMAT API to save messages into the IB/OB SMAT database defined on the GUI. The SMAT API can open a traditional IB/OB SMAT database, but is restricted to read-only operations. Full use is granted to the user-defined SMAT database.
- Multiple writers
One protocol thread can only have one traditional IB/OB SMAT database. It can only be written based on its configured thread with a unique save context, that is, inbound or outbound. Multiple user-defined SMAT databases can be created in a thread or in a TPS. Similarly, one user-defined SMAT database can be shared/operated at the site level, that is, it can have multiple writers with multiple contexts by multiple processes.
- Resend mapping
For the resend of a user-defined SMAT database, there is a mapping between the TPS context (saveContext), and the traditional IB/OB save contexts.
- Trace storage
Trace information, such as the SMAT database name/location, is stored into the tracing database.
These behaviors are shared between the two types of SMAT database:
- Table schema is the same.
- The SMAT history and cycle logic share the same configuration with the traditional IB/OB SMAT database.
- The encryption key is the same as the SMAT database, that is, the site name.
Additional points:
- 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 still through Tcl, not natively.
-
xltp
andjxltp
are not supported.