Map deployment procedure
For all operating systems, follow the steps provided here.
Procedure
- Build the maps:
There are several ways to build the maps including individual map selections using the Design Studio or Design Server, the Command Server, Deployment and Packages, Deployment and Build, etc.
- Copy the following files to the target system as binary and place the files in the same
directory as the compiled maps:
- All compiled maps. If you are sure that certain versions of the standards are not going to be used again, you can skip the seg* and ttv* maps that correspond to those versions. As an example, If you are not going to use X12 version 002040 again, you do not need to upload the ttv2040 or seg2040 compiled maps. However, if these maps are not present and an X12 002040 transaction is encountered, the compliance check maps cannot process the transaction correctly.
- Configuration schema x12cfg.xsd (X12), railcfg.xsd (RAIL), or edfcfg.xsd (EDIFACT).
- The shared exit library, which is found under the platform_support directory. Be sure to choose the operating system and bit type (32-bit or 64-bit) that matches your Transformation Extender installation.
- Copy the following files to the target system as ascii, and then place the files in the same
directory as the compiled maps:Note: When you copy these files to UNIX systems, the CR characters (x0d) must be removed. If the process that you use to copy them (for example, FTP) does not remove them, then you must remove them manually.
- The file that contains error message text, errcodes.txt (X12, RAIL, and EDIFACT).
- Files with table data used by the compliance check maps: x12codes.txt and x12struct.txt (X12), railcodes.txt and railstruct.txt (RAIL), or edfcodes.txt and edfstruct.txt (EDIFACT).
- The system information file edicc.ini.
- Edit the edicc.ini file on the target system, and set the
exitlib value to point to the shared exit library that you uploaded in the
earlier step.
- For Unix systems, this would be path to edisvu.so or edisvu.sl file, and on Windows it will be the path to edisvu.dll. (DO NOT INCLUDE FILE NAME IN PATH)
- Setting ./ is relative to map execution folder.
- Setting N/A or NA (Not Applicable) identifies the ITX install folder.
- Set up your configuration file to point to the output location that you want to use. If you are
using file output, you must create the following subdirectories under the output directory that you
specify in your configuration:
edifact EDIFACT only edifact/reject EDIFACT only fa EDIFACT, X12, and RAIL fa/inbound EDIFACT, X12, and RAIL fa/outbound EDIFACT, X12, and RAIL ta1 X12, RAIL only ta1/inbound X12, RAIL only ta1/outbound X12, RAIL only x12 X12 only x12/reject X12 only rail RAIL only rail/reject RAIL only