Deploying the XML schemas to Sterling B2B Integrator

The WebSphere Transformation Extender Pack for SWIFT contains XML schemas. These include SWIFT MX schemas as well as other pack-specific XML schemas that are used for configuration, transformation, and validation.

For these XML schemas to be used within the Sterling B2B Integrator, they must be uploaded to the Sterling B2B Integrator schema repository. The steps provided here, describe how to check-in (upload) the XML schemas that come with the Pack, to the Sterling B2B Integrator schema repository.

The WebSphere Transformation Extender base product resolves the location of the XML schemas used within a WebSphere Transformation Extender map, executing within the Sterling B2B Integrator, in the following order:

The XML schema is resolved by searching the SI schema repository.
If the schema is not found in the SI repository, the WebSphere Transformation Extender locates the schema based on any file path references associated with it.

Perform this procedure to deploy XML schemas to the Sterling B2B Integrator server:

Stop Sterling B2B Integrator.
Navigate to <si_install_dir>/bin
Load the XML schemas to the Sterling B2B Integrator directory.
1. For Windows, at the command prompt, or in the Run dialog box, enter:
  InstallService.cmd<product short name>/common/data/swiftnnnnxsd4si.jar
  
  Note: To obtain the product short name, open a command prompt and cd to C:\IBM, then enter dir /x. The product short name is displayed. For example, the product short name for WebSphere Transformation Extender version 8.4.1 is WEBSPH~1.1.
2. For UNIX/LINUX, enter:
  installService.sh <pack_install_dir>/common/data/swiftnnnnxsd4si.jar
Restart Sterling B2B Integrator.

In the above directory locations, <product short name> indicates the short name of the WebSphere Transformation Extender installation directory; <pack_install_dir> indicates the installation location of the pack; and nnnn indicates the version number of the pack.