Deploying JVC compliance checking on IBM Sterling B2B Integrator

You can deploy JVC compliance checking on IBM Sterling B2B Integrator.

If the SWIFT component of the Transformation Extender Pack for Financial Payments is installed on the IBM Sterling B2B Integrator server, skip step 1.

If the Transformation Extender Pack for Financial Payments is not installed on the IBM Sterling B2B Integrator server, then you must deploy the components to the IBM Sterling B2B Integrator server using the procedures provided here.

In the following procedures, si_install_dir is the location where the IBM Sterling B2B Integrator server is installed. install_dir is the directory where the IBM 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 IBM Sterling B2B Integrator server. See the pack release notes for deployment instructions.
  2. After installing the Transformation Extender Pack for Financial Payments on Windows, copy jvalccyy.jar from the following location:
    install_dir
    to the following directory on the IBM Sterling B2B Integrator server:
    si_install_dir/jar/SterlingTX/n_n_n
    where n_n_n indicates the IBM Transformation Extender base product version.
    Note: The JVC must be set to verbose mode.
  3. Install the jvalccyy.jar file by using the IBM Sterling B2B Integrator third party installer utility called install3rdParty under si_install_dir/bin
    For example:
    si_install_dir/bin/install3rdParty.cmd SterlingTX n_n_n -j install_dir/extjar/jvalccyy.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.srgccyy.Validator
    translator.DTX_SWIFT_CONFIG_DIR=pack_dir/swift/mt/jvc/maps
  5. Restart IBM 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.