Technical developers can customize the default mode of the WebSphere Multichannel Bank Transformation Toolkit Processor editor according to their project requirements.
The WebSphere Multichannel Bank Transformation Toolkit Transaction editor stores the flow in a file with the .transaction extension, which contains a generic channel independent flow. To run this flow in a runtime environment, you must generate a WebSphere Multichannel Bank Transformation Toolkit .xml file of the transaction (right-click the transaction file in the Enterprise Explorer view, and then click ). This is a channel dependent file that is generated according to the current active generator.
Each WebSphere Multichannel Bank Transformation Toolkit channel has its own generator, which is defined through the com.ibm.btt.tools.transaction.editor generator extension point. WebSphere Multichannel Bank Transformation Toolkit version 8.0 includes a generator corresponding to the HTML channel. If several generators are defined, developers can select the generator to activate (in IBM Rational® Application Developer, click ).
A generator can have one or more mapping files. A mapping file contains tag mappings (for example, from PageState to htmlState), property mappings (for example, from page to typeIdInfo) and logic to be injected during the mapping. If a generator has more than one mapping files, each mapping file must define a different set of tags, otherwise there is no guarantee about which definition will be taken into account.