Building Transformation Extender maps

The build process generates a compiled map with a file name extension that is specific to the target platform of the server, which you specified in the Sterling B2B Integrator preferences window.

You can test run a map from the Design Studio or deploy a map from the Design Studio to the Sterling B2B Integrator server in either the Outline view or Composition view. When you select the map in either of these views, the test run map and deploy map functions automatically build the IBM Transformation Extender map for the target platform of the server, which you specified in the Sterling B2B Integrator preferences window.

You can also deploy a map from the Design Studio to the Sterling B2B Integrator server in either the Navigator view or the Extender Navigator view. When you select an executable map in either of these views, you must first manually build the IBM Transformation Extender map for the target platform of the server by selecting one of the build map options.

After a successful build, you can test the map on the Sterling B2B Integrator server. When you run a IBM Transformation Extender map, the compiled map, and input files are sent to the Sterling B2B Integrator for processing. The results are returned to the Design Studio.

This is a pre-production phase. When your maps are ready for production, after you deployed the maps to a Sterling B2B Integrator server map repository, there are additional tasks to complete using the Sterling B2B Integrator Graphical Process Modeler (GPM) user interface. For information about running maps in a production environment, see the IBM Sterling B2B Integrator documentation.