Map deployment procedure
To deploy to z/OS batch, see the deploying_to_mvs example. For all other operating systems, follow the steps here.
- Go to the compliance check mapsandschemas directory
and edit the compileAllX12.bat file, for X12,
or the compileAllEDF.bat file, for EDIFACT. You
must add the –P option to each of the mcompile commands
to compile the map for your target system. For example:
mcompile ccx12.mms –A –O *.mmc –P AIX
Valid values for the –P option are AIX, HPUX, SOLARIS, ZOS, LINUX, ZLINUX, and HPITANIUM. - Run the compileAllX12.bat file, for X12, or the compileAllEDF.bat file, for EDIFACT, to compile all compliance check maps.
- 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) 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 WebSphere 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 (both X12 and EDIFACT).
- Files with table data used by the compliance check maps: x12codes.txt and x12struct.txt (X12), 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.
- If you are deploying the compliance check maps for use under Sterling B2B Integrator, this step
(step 6) is not required, as Sterling B2B Integrator dynamically
creates the configuration input.
Create an XML configuration file on the target system. You can use one of the sample XML configuration files from the data directory, or you can create your own. This is typically an ASCII file for all operating systems, including z/OS. If you are uploading the file to z/OS (USS or batch), upload the file as binary. For other UNIX systems, the configuration file can be uploaded in either ascii or binary mode, since the file can be parsed either with or without the extra carriage-return characters.
- 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 and X12 fa/inbound EDIFACT and X12 fa/outbound EDIFACT and X12 ta1 X12 only ta1/inbound X12 only ta1/outbound X12 only x12 X12 only x12/reject X12 only