Folder structure

The folder structure used in the SWIFT components is shown in this table:

Folder Description

common/data

 Sample BIC and currency code and country code lookup files, and a sample jar file to upload schemas to Sterling B2B Integrator.

common/maps

 Maps to create lookup files from the SWIFT bank and currency files.

common/schemas

 Schemas used to describe the BIC and currency lookup files.

common/type_trees

 Type trees for the BIC and currency lookup files

mt/examples

 Examples for statement splitting, batch validation and JVC validation using the Launcher. Also includes Sterling B2B Integrator Generic Deenvelope and Generic Envelope examples.

mt/jvc/maps

 Map to invoke the JVC. Placeholder for the JVC configuration file.

mt/jvc/metadata

 Files used by the JVC for syntax validation.

mt/lmf/from_lmf

 Maps for converting LMF format to MT format.

mt/lmf/to_lmf

 Maps for converting MT into LMF.

mt/type_trees

 Core SWIFT type trees, JVC and LMF type trees, and general purpose MT type trees.

mx/data

 Sample data.

mx/examples
  • Bundling and unbundling MX with the Business Application Header.
  • MT and MX Translation maps.
  • Sterling B2B Integrator Generic Deenvelope service and Generic Envelope service maps.

mx/maps

 MX validation framework maps.

mx/msd

 Deployment script for the MT and MX translation maps and MX framework validation.

mx/schemas

 Latest versions of the SWIFT MX schemas as of the time of this pack release.

mx/type_trees

 Full set of SWIFT MX type trees, and type trees used by the MT and MX translation maps.

In addition, two jar files for the JVC are placed in the WebSphere Transformation Extender installation directory:

  • jvalnnn.jar - This file is the core JVC jar file (where nnn indicates the release version of the pack, for example 432).
  • jvcwrap.jar - This file is the version independent wrapper class for simple invocation of the JVC.