Programming Guide
The engine's own programming guide, generated from the 8.1 engine source beside the API reference it explains: the concepts every tier shares, then one page per client tier. Names in the guide link to their pages in the C/C++ reference.
| Page | |
|---|---|
| Concepts & Architecture | This page defines the components of a Tricryption deployment and describes the common data-protection scenarios and the decisions to make before you start developing. |
| C API Programming Guide | The C TEAgent package provides functionality such as encrypting, decrypting and hashing data. The full function reference is in teagent_c.h; this guide covers the overall workflow and points to runnable examples. |
| C++ API Programming Guide | The Tricryption Engine C++ API comprises two groups of components: TEAgent (cryptographic operations) and TEAdmin (administration). All classes live in the PISOFT namespace, so either bring it into scope with using namespace PISOFT; or prefix class names with PISOFT::. |
| Java API Programming Guide | The Java agent is the tech.pisoft.teagent package of the TEAdmin jar (TEAdmin-8.1.0.jar, built by the product's te_java_teadmin target into build/Java). It is compiled for Java 25 (class-file version 69), so it needs a Java 25 or later runtime. This page is a guide only: the Java classes are documented in the separate Java API reference, generated from each class's own documentation comments, which are the reference for its methods. |
| TypeScript API Programming Guide | The TypeScript agent is the npm package server-ts-agent (TricryptionSuite/TEAgent/server-ts-agent), for server-side Node.js consumers. It speaks the Key Server's binary protocol over TLS 1.3 in pure TypeScript. Consume it through a file: dependency and import it by package name only — the typed barrel (src/index.ts) is the supported surface, and a subpath into dist/ is not. This page is a guide only: the TypeScript declarations are not part of the generated reference; the barrel's and src/auth-types.ts's comments are the reference. The in-tree samples are under samples/ts. |