X.400 Gateway API

The Isode X.400 Gateway API is available in Java or as a simple ‘C’ programmatic interface to connect external messaging or telematic services to X.400. This API suits aviation, military, or EDI applications. This product was originally developed for the aviation industry and includes features designed for AMHS vendors building solutions for the aviation industry, developing ground-to-ground applications that operate over AMHS, and integrating AMHS applications with the AFTN network.

The API includes support for:

1. Control of M-Switch addition of message digital signatures and report on message signatures.
2. File Transfer Body Part (FTBP) support

The Isode X.400 Gateway API provides a simple, easy-to-use abstraction of X.400. Although the API abstracts X.400 complexity, it is designed so all X.400 services can be selected and modified if required. The API shares some common functionality with the Isode X.400 Client API product family.

Architecture

The X.400 Gateway API and AMHS Gateway APIs are co-resident with M-Switch X.400. This is primarily intended for building gateways that require access to X.400 (message transfer) service elements not available over P3 or P7. This architecture could support client X.400 applications, although Isode does not recommend it.

This API is synchronous and designed for use in a multi-threaded process, and a process may have multiple associations. Each association should be accessed by only one thread. You can run multiple processes in parallel using this interface.

API Definition

• The Isode manual, which describes all Isode messaging APIs, is here.
• The ‘C’ language Isode Gateway API definitions are available here, and example programs are available here.
• The Java language Isode Gateway API definitions are available here, and example programs are available here.
• Examples of the Tcl language Isode Gateway API are in the product release notes and are described here.