EDIMatrix - Products

Converters

At the heart of the DMX range are the converters; programmes which transform information to and from the specialised EDI syntax. DMXCONST will convert from application created intermediary files to files containing EDI interchanges. DMXTRANS will convert from files containing EDI interchanges to files for import to an application. Both programmes use what is called a table to define the format and structure of the input and output files, and a control file to steer the (often complex) operational aspects of the conversion. The format and structure declarations are normally strictly defined and static, so the table used is a binary file compiled from a user source description. The control file can be modified from session to session and so a user-editable plaintext file containing different record types for the different aspects of a session is used. Facilities exist for modifying a control file from the command line when the converters are invoked, and dynamically during a session in response to incoming data.

The primary function of the converters is syntax conversion, but they also perform sophisticated error checking, reporting, and error recovery. The way in which errors are handled can be varied by the user; with possibilities ranging from carrying on regardless in all cases other than the grossest operational faults to immediate termination of the session if the slightest fault or inconsistency is found. If nothing else is specified the converters will assume 'sensible' defaults for error handling which cover the requirements of most users.

The DMX converters are unusual in that they can operate in a much more varied environment than is customary. In the course of a single session you can process multiple files containing a mix of interchanges for different partners, EDI standards, and message types. DMXTRANS can also distinguish between EDI and non-EDI files, and ignore extraneous information inserted by networks. The data-splitting, file movement and session management normally handled by extra software in an EDI Gateway are present in the converters themselves.

Session Logging

The converters generate a cumulative log which contains information about everything that has happened during a session. This includes logging of partners and messages processed, files used and moved, profiles invoked, physical positions of messages and interchanges in files, data values for information that the user has nominated for logging, and detailed information about any errors detected. The log is in a format which makes this information readily available to other software. The program DMXERRAN is used to transform as much of this information as you require to a readable form, which can be output to file if you do not have other software for accumulating information about your EDI processing.

Table Maintenance

The creation and maintenance of tables, the format definition files which govern how the converters manipulate information, is normally a specialised business better left to EDI consultants. Since changes to the EDI message definitions affect your trading partners (both present and potential) they should not be made without careful consultation. You may however wish to alter your inhouse file format (the file(s) generated and read by applications). The DMX converters are supplied with table maintenance utilities to enable you to do this. DMXTLIST will display the structure and contents of a table in a form ideal for overview and understanding of the table; DMXTDUMP will produce a comprehensive (and large!) plain text file which completely defines the table. This text file can then be edited by the user and recompiled to form a new table using the DMXTCOMP utility, which will check and validate the table specification to ensure that there are no inconsistencies.

EDIMatrix has specialised programs such as DMXTEDIT available for table maintenance which considerably ease the creation or substantial modification of tables. These are not however supplied automatically as part of a DMX purchase, since the majority of users do not develop their own tables.

Control Files

These are the text files which define the operational environment for the converters during a session. At their most basic they merely specify which input and output files are to be used, and which table should be read to govern the session. Most control files use little more than this plus a few specifications for file formats. You can specify where you want processed files moved to based on the results of the conversion, semaphore files for multitasking environments, code and character conversion definition files, a profile for data-driven context changes, constant data to be used during the session, and a number of other more exotic options.

Profiles

A profile is a potentially a complete specification for your EDI processing requirements for either construction or translation. You can relate any combination of trading partner and/or message type to the control file to be used for processing that combination. Since the control file specifies the session completely this gives you great flexibility. The control file information can be included directly into the profile if required. When running under a profile the converters match every partner and message type encountered in their input data against those specified in the profile. If a match is found then the existing control file information will be modified by the control file information specified for that match in the profile. This can include changing output files, tables and processing options.

This is easier in practice than it sounds, since the majority of your EDI processing will not require special context changes. Profiles always contain a default specification which is obeyed unless some more specific match can be found, and your profile normally only has to specify exceptions to the default processing.

A DMX converter is always supplied with the DMXPCOMP utility, which can convert plain text profile descriptions into the binary form required by the converters and will provide validation of the profile and identification of any potential problems involved in its use.

Scripts

The majority of users do not have special requirements for an EDI converter above the functionality described so far. Occasionally the need does occur for special processing and in the past this normally required bespoke programs to massage the incoming or outgoing converter information. The DMX converters contain a script interpreter which can be invoked at most significant points in the conversion process to perform special processing (including links to external programs). The script language is specially designed for EDI processing, and plain text scripts in this language can be compiled into a table by use of the DMXSCOMP utility.

Use of such scripts is normally more advanced than the general user requires and the facility is intended for use by DMX vendors to customise the converters if required. One of the script language commands can however be used to implement code conversion and the DMXSCOMP script compiler is therefore supplied as part of a DMX converter purchase, since this is (regrettably) something which users do ask for.

Character Conversion

One aspect of EDI which is ignored by most converters is the potential problem in international traffic which occurs when the character sets used by sender and recipient do not match. This is most marked with vowels which can occur in foreign languages which will often appear as obscure characters when printed out or displayed using the English or American character sets. The DMX converters can, at the interchange interface, perform character substitution based on the character set which the interchange header identifies for the messages in it. The DMXMKTRN utility can be used both for incorporating a single conversion matrix in a table, and creating an external character conversion file for more sophisticated, syntax type, conversions.This facility can also be used for EBCDIC / ASCII conversion if required.

Other DMX Products:

DMXPRINT

A general-purpose, easy-to-use, utility which can transform flat files to other flat files, printed reports, web pages, XML, or multiple key-linked files in CD or SDF format. If used as a post-processor for DMXTRANS the input file definitions can be imported from the DMX table: otherwise a straightforward plain text definition file is required to define the input file format.

The output file definition is via a user-created template which resembles the output file to be created. DMXPRINT interpolates data from the input file into this template to generate the desired output. Because of the 'What You See Is What You Get' nature of the template even inexperienced users can readily specify and modify the output file format. Advanced users can use programming commands such as IF / THEN / ELSE to create really sophisticated output.

DMXEFAX

This product uses the same output specification technique as DMXPRINT, but takes its input directly from files containing EDI interchanges instead of from an inhouse file generated by a converter. A plain text input description file is used to identify the data items from the incoming EDI message which are to be extracted, and their desired output field format. A partner/message filter can be specified for input files containing a mixture of EDI information. DMXEFAX can also be used to process delimited files and XML.

Whilst DMXEFAX lacks the power and versatility of DMXTRANS it does provide an extremely low cost facility for users wishing to receive only a few message types, and can easily be configured by a user with only a limited knowledge of EDI. It can generate traffic information which can be automatically imported into the DMX Gateway DMXGWAY.

DMXREFRM

Another module whose output capabilities are similar to DMXPRINT's, but with input taken from multiple Comma Delimited (CD) or Standard Data Format (SDF) files. Typically used as a report generator, or to generate input for an EDI construction program which requires a tagged flat file. Can be 'user programmed' for very sophisticated data handling. It can also generate EDI messages directly without the need for a converter in 'Lite EDI' systems, and thus is the equivalent of DMXEFAX for construction (outgoing data)

DMXCOMMS

A general-purpose communications module whose look, feel and functionality are determined by scripts written in a powerful language designed for the purpose. It can be used for asynchronous dialed links or TCP/IP. Multiple windows, simulated multi-tasking, data linkage to external procedures and an inbuilt help referencer combine to make this an ideal product to form the basis of your own comms module. Standard scripts configure it as a network module for BT EDI*NET, TRADANET. or AT&T EASYLINK, and for POP3 and SMTP applications. If required EDIMatrix can configure DMXCOMMS according to your requirements. Not available under Linux. DMXCOMMS is our most popular single product!

DMXGWAY

A traffic display and analysis module for Windows which provides a user interface to the results of EDI conversion sessions. Data from the session logs is processed into a database which is subsequently accessed via a SQL query generator to produce displays and reports. DMXGWAY lets you see what has happened in your EDI system, and links together the other DMX modules to give a complete end-user EDI product. The display is document based, and whenever possible a suitable value (such as order or invoice number) is extracted from the document and displayed to identify the documents for you. DMXGWAY can register and monitor transactions which have been processed by the converters and the re-formatters. You can also use a web browser to get EDI traffic and status information, selected by criteria which you specify, if you do not have physical access to the EDI PC.

The DMXGWAY database is accessed and modified by other DMX network and audit modules so that an up-to-date picture of your EDI traffic is always available. DMXGWAY can be scheduled as a background task for periodic data collection, analysis, reporting and archiving. It is the visible interface to your EDI system.

DMXSCHED

A sophisticated Windows scheduling system which allows you to run EDI-related (and other) processes automatically at specified periods. Functionally similar to the Unix CRON scheduler but with a very much more intuitive graphical interface. Includes WINTASKS, a Windows 'batch processing on steroids' facility, for creating your own sequences of related tasks, moving files around, checking on statuses and performing general housekeeping. Wintasks scripts are used in all our installations and allow us to create an EDI system which matches individual client requirements.

DMXTEDIT

A Windows Table Editor (sometimes called a Mapper) which allows you to subset DMX tables and map the EDI data to your inhouse file formats. This is faster and more easily used than the text-based table support provided as standard with the DMX converters. Delivered with a full set of EDIFACT UNSM tables for D93a onwards. Any EDI documentation tool (such as EDISIM, EDIFIX or EDIFECS) which exports definitions in .SEF format can also be used to define the EDI side of a table. The .SEF file can then be processed to one or more tables by the free DMXSEF processor, and DMXTEDIT used to perform the mapping of data to the inhouse file.

BUDGET*EDI

A complete system for receipt of EDI messages from BT EDI*NET (other networks interwork with this) to generate paper documents, or intermediary files for import to your application. Delivered as a shrink-wrap product which can be installed and used by the non-technical. Uses DMXCOMMS, DMXEFAX, and 'glue'.

We have also created BUDGET*EDI packages for other networks, such as EasyLink, Tradanet, and IBM Information Exchange, and for target groups such as Automotive and Book Trade.

ROBOT WORKSTATIONS

Simple workstations for those who do not wish to integrate EDI into their application systems. They give the ability to receive an incoming EDI message type into a local database, view and complement the data, and then turn it around to generate another EDI message type as a response. For example orders can be received and used to generate invoices. The 'robot' refers to the automatic process used to create them from the converter tables for the messages to be handled. We do not recommend use of such a workstation unless it is absolutely necessary, or as a basis for customisation.

NETWORK INTERFACES

There are a number of network interfaces supplied with the DMX Gateway. You can use any or all of them; the Gateway partner profile links a trading partner to one of the networks. These include Tradanet (EDI*Switch in other countries), IBM Information Exchange, BT EDI*NET, EasyLink, GXS Trading Grid, MAPI, Internet Email, FTP, and secure FTP (both TLS and SSH). These interfaces access the Gateway database and post status and acknowledgement information from the networks there (the level of reporting available varies from network to network). We also have a freestanding Tradanet Interface which can be used by other EDI systems, and a number of Budget interfaces to all the above networks, Geis EDI Express, Kermit, and TeleOrder Async Dialup, plus some real oddballs!.

DMXMLCUT

A pre-processor for incoming files which can extract and match XML documents against a sophisticated profile to determine how they are to be handled, perform the appropriate transformations, and generate a Gateway compatible traffic log. Outgoing XML can be generated directly by the re-formatters when in XMLMODE.

Much More .....

There are many more modules to support a system based on DMX. Most are free!

DMX products are millenium compatible

DMX Pricelist

EDIMatrix is keenly aware that the initial cost of an EDI capability, particularly for low-volume users, has been a significant hindrance to the adoption of EDI. Despite their rich functionality DMX modules are available at budget prices. Some examples of the one-off price for DMX modules (under DOS, Linux, Win 3.1, Win95/98/2000/XP or NT4) are given below.

DMXCONST	£225
DMXTRANS	£225
DMXERRAN	£75
DMXEFAX	£150
DMXCOMMS	£120
DMXPRINT	£150
DMXREFRM	£150
DMXSCHED	£60 (Windows only)
DMXGWAY	£210 (Windows only)
*BUDGETEDI**	£300 complete!
DMXTEDIT	£300 (Windows only)
DMXMLCUT	£75

These are reduced when more than a single module is bought. The DMXCONST / TRANS / ERRAN / COMMS combination (a fully functioning EDI gateway) is £525. DMXEFAX / COMMS together are £225. A complete Workstation (GWAY / CONST / TRANS / ERRAN / SCHED, multiple network interfaces, and 'glue') is still only £800.

There are generous discounts available for quantity purchases and for re-sellers. EDIMatrix is primarily an EDI consultancy and we can offer full support for installation, training and maintenance; or take full responsibility for your EDI project at all levels if required.

Tie Products

We are UK representatives for TIE (formerly EDI-TIE BV), the prominent international EDI firm, and can supply, install and support systems based on their very wide range of products for many different platforms, operating systems, and communication networks. TIE have a global coverage using subsidiaries and agencies, so this can be of particular interest for international projects.

Hybrid EDI

This is how we describe a mixture of true EDI which is imported to your application, and other messages which are used to generate printed reports. By complementing a DMX Gateway with one of our Budget*EDI products we can easily handle this scenario. We can also arrange for outgoing messages to be processed to EDI for some partners, emailed reports for others, and even faxes if necessary. Generation of HTML and XML documents which are then automatically FTP'd up to a web site is also possible.

Page last modified 2004-10-01

DIMatrix product descriptions: EDI Converters, Gateways, Mappers, Schedulers, Network Interfaces, Lite EDI, Reformatters.