Deploying MX compliance checking components

If the SWIFT components are installed on the Sterling B2B Integrator server, then you can skip step 1 in the following procedure, and you can continue with step 2.

If the SWIFT components are not installed on the Sterling B2B Integrator server, then you must deploy the components to the Sterling B2B Integrator server, using the following procedures:

In the following procedures, and throughout this documentation, <si_install_dir>, is the location where the Sterling B2B Integrator is installed, and <wtx_install_dir>, is the directory where the WebSphere Transformation Extender base product is installed.

Note: Make certain that the permissions are set properly on the pack directory structure and subsequent subdirectories, including all of the compiled maps.
  1. Deploy the SWIFT components to the Sterling B2B Integrator server.
  2. After installing the SWIFT components on Windows, define the customer_overrides.properties under the following directory:

    <si_install_dir>/properties

    Include the following entry:

    translator.framework_driver_map_location=<pack_install_dir>/swift_vnnn/mx/maps/swiftval.mmc

  3. Restart Sterling B2B Integrator. This is required after changes are made to the customer_overrides.properties file.
  4. Verify the configuration by executing the MX Generic Envelope and Deenvelope example maps. The result should be consistent with the expected results as defined in Expected results.