AMTrix
| Original author(s) | Frontec |
|---|---|
| Developer(s) | Axway |
| Initial release | 1995 |
| Stable release | 4.4.3 |
| Written in | Message Builder, C |
| Operating system | Win, UNIX, OS/400 |
| Platform | x86, POSIX, AS400 |
| Size | 500 MB+ |
| Available in | English |
| Type | Middleware |
The AMTrix System is an Enterprise application integration software system that acts as a middleware and enables applications to exchange data in standardized message formats, regardless of physical distance and hardware platforms.
In order to enable this application messaging, AMTrix performs several vital functions:
- Message conversion: This is usually done between an in-house format (for example, flat file or database) and an external, more standardized format (for example, EDIFACT or X12), although AMTrix can convert between any two message formats. Message conversion is done by programs or 'maps' which are written in the Message Builder Language (MBL). Maps are programs that map data fields in the input message (source) to data fields in the output message (destination) with or without manipulation of the data that is being mapped. Maps in AMTrix can be created using AMTrix's Datamapper which provides a user-friendly GUI that 'links' the source and destination data fields.
- Application server connectors: These are a complete solution packages for the efficient implementation and integration of specific applications into an enterprise infrastructure. The first application connector for SAP R/3 and fully certified as compliant was launched in October 1997. It acts as the interface with SAP R/3systems, using either IDoc or ALE. This makes AMTrix a powerful support during SAP implementations, as it provides a unified method for integrating all non-SAP environments.
- Intelligent processing of messages: In addition to conversion between different message formats, AMTrix can validate data and make decisions based on the contents of a message.
- Message logging: AMTrix monitors the system and creates message logs so that users can see what is going on at present and what has happened in the past—enabling the retransmission of messages and retrieval of message information for report generation. AMTrix also has two other type of logs:
- Document Log – It maintains a log of all the documents that were processed through the AMTrix system in the past 10 days (including the actual documents)
- Transfer Log – Maintains a log of all transfers that happened via the AMTrix system. Including details of the "Trading Partners" involved in the transfer, the time of transfer and the associated documents corresponding to each transfer.
- Message transportation: In order to be able to reach applications located on other hardware platforms and/or retrieve data to construct messages, AMTrix features a number of different communication protocols and interfaces, for example, X.400, FTP, EMAIL, OFTP, WWW, and asynchronous.
The AMTrix System is constructed in a modular fashion, with message processing and communication modules connecting to a central message distribution engine (the AMTrix Router). The entire system is monitored and configured from a network client (the AMTrix Monitor).
AMTrix Monitor is the GUI client for the AMTrix System, to operate, configure, and maintain the AMTrix System on the server (or servers), manage trading partner information, and define and modify various system parameters, for example, those affecting Event Logging.
Message Builder
Message Builder is a general purpose programming language. Among other things, it contains special constructs to access SQL databases and to handle EDI messages. Large parts of the Integrator are written using Message Builder.
Add on packages add extra capabilities to the Message Builder language. Examples are graphical user interface programming and socket communication.
Message Builder runs on different versions of UNIX, on Windows, and AS/400. With one exception (the AS/400), compiled Message Builder programs can be moved between different computers and executed without recompilation.
The language can be extended with Message Builder written functions and statements that can be used in the same way as built-in functions and statements. It is also possible to extend the language with C-written functions and statements (refer to the MBC Extender Guide).
A Message Builder program consists of one or more text files containing the program text. These files are compiled using a compiler that produces an executable Message Builder program. This executable program consists of instructions for an imaginary machine. An interpreter implements this imaginary machine and is used to execute the program.