Well-behaved map

There are several Sterling B2B Integrator services that can run IBM Transformation Extender maps. When a IBM Transformation Extender map runs from those services, with the exception of the WTX Map service, it must operate according to a certain set of requirements. A map that meets these requirements is considered to be well-behaved.

A well-behaved map has the following characteristics:

  • The map is an executable IBM Transformation Extender map. If at run time the map is provided with the required input, it can be run.

  • The map is designed to be called from within a specific Sterling B2B Integrator service. If the service is set up to process incoming X12 data, for example, the first input card of the map accepts X12 data. If the service is expecting the map to generate an XML message, then the last output card of the map creates an XML message.

  • You define the restart and burst settings in the map as the service requires, and as stipulated in the Sterling B2B Integrator exhaust input setting.

  • If the map requires table data information or settings from Sterling B2B Integrator, such as delimiter settings for outbound EDI, or extract information while parsing the data that is to be sent back to Sterling B2B Integrator, such as correlations, then the map has been designed to meet these requirements.

  • The map design follows published Sterling B2B Integrator and IBM Transformation Extender integration best practices including being a thread-safe map. In Sterling B2B Integrator, Sterling B2B Integrator maps are run in a multi-threaded environment.

  • The service passes the Primary Document to the first input card and reads it from the last output card. For more information about the Primary Document, see the IBM Transformation Extender for Sterling B2B Integrator documentation.