Differences when running HCL Transformation Extender maps on Sterling B2B Integrator

On Sterling B2B Integrator, IBM Transformation Extender maps run through different services that are called by business processes.

There is a set of Sterling B2B Integrator services that run IBM Transformation Extender maps with some restrictions. There is also a WTX Map service that can run any IBM Transformation Extender map with no restrictions. Through the Design Studio, you can test running maps on a Sterling B2B Integrator server inside this WTX Map service.

Although map functions and all adapters are supported by Sterling B2B Integrator, running IBM Transformation Extender maps on Sterling B2B Integrator is different in the following ways:
  • For maps to run inside Sterling B2B Integrator services other than the WTX Map service, these services require that maps meet certain requirements to be considered "well behaved" maps.

  • If the map is checked into the Sterling B2B Integrator map repository, the IBM Transformation Extender map working directory is SI_install_dir\logs.
    • If a map uses the RUN function in a rule, the map that is referenced must be located either in the Sterling B2B Integrator map repository, or relative to the parent map location on the server.

    • If the Schema > Type > Metadata card setting specifies an XML schema, the schema should be checked into the Sterling B2B Integrator schema repository. However, if the schema is not in the repository, it should be placed relative to the SI_install_dir\logs directory.

      All IBM Transformation Extender maps, including validation and translation maps, and maps run through the WTX Map service, first attempt to load the schema from the repository. If the schema is not in the repository, the maps then attempt to load the schema from the map location on the server.

    If the map is not checked into the Sterling B2B Integrator map repository, the map runs in the same way as any other IBM Transformation Extender map runs.

  • The map can include the Sterling adapter in PUT and GET rules in the following locations:
    • on the map
    • on component rules in type trees
    • through the command line on an input or output card


    The Sterling adapter calls the data harness to provide access to Sterling B2B Integrator tables. These maps can only run within the Sterling B2B Integrator environment.

    To see how to use the Sterling adapter in a map rule to access Sterling B2B Integrator tables, see the translation example in the install_dir\examples\integrations\SterlingB2B\Engine directory, where install_dir refers to the path where IBM Transformation Extender is installed.

    See Supported HCL Transformation Extender map functionality on Sterling B2B Integrator.

  • You must configure the Design Studio settings, such as connection properties, the Check In Map service options, and the troubleshooting options, for Sterling B2B Integrator services.

    To test that IBM Transformation Extender for Sterling B2B Integrator is installed correctly, and that Design Studio and Sterling B2B Integrator are configured and are running properly, run the Installation Verification Test (IVT) example under install_dir\examples\integrations\SterlingB2B.

  • The map must be built on a platform that the Sterling B2B Integrator server supports.

  • When you run maps from the Design Studio on the Sterling B2B Integrator server, the map server location is the install_dir\logs directory.

  • For troubleshooting problems, you must configure the Save service request and response messages option in the Design Studio.

You can test the map in the Design Studio to verify that you configured the map to run correctly on Sterling B2B Integrator. After you completed test running the map, you can then deploy the map from Design Studio to a Sterling B2B Integrator server map repository.