Deploying JVC compliance checking on Sterling B2B Integrator

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

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 procedures provided here.

In the following procedures, <si_install_dir>, is the location where the Sterling B2B Integrator server is installed. The notation, <wtx_install_dir>, is the directory where the WebSphere Transformation Extender base product is installed.

In the following procedures, make certain that the permissions are set properly on the pack directory.

  1. Deploy the pack to the Sterling B2B Integrator server. See the Pack for Financial Payments release notes for deployment instructions.
  2. After installing the SWIFT components on Windows, copy jvalnnn.jar from the following location:
    <wtx_install_dir>
    to the following directory on the Sterling B2B Integrator server:
    <si_install_dir>/jar/WebSphereTX/<n_n>
    where <n_n> indicates the WebSphere Transformation Extender base product version.
    Note: The JVC must be set to verbose mode.
  3. Install the jvalnnn.jar file by using the Sterling B2B Integrator’s third party installer utility called install3rdParty under <si_install_dir>/bin
    For example:
    <si_install dir>/bin/install3rdParty.cmd WebSphereTX <n_n> -j
    <si_install_dir>/jar/WebSphere/<n_n>/jvalnnn.jar -nodeploy
    Note: The above command is contained in one line.
  4. Define customer_overrides.properties under the following directory:
    <si_install_dir>/properties
    Include the following entry:
    translator.SWIFTValidation=com.ibm.websphere.dtx.ip.swift.vnnn.Validator
    translator.DTX_SWIFT_CONFIG_DIR=<si_pack_dir>/swift_vnnn/mt/jvc/maps
  5. Restart Sterling B2B Integrator. This is required after changes are made to the customer_overrides.properties file.
  6. Verify the configuration by executing the MT Generic Envelope and Deenvelope example maps. The result should be consistent with the expected results as defined in Expected results.