In IBM® WebSphere® Multichannel Bank Transformation Toolkit version 7.1, the configuration of each component is defined in the component's kColl. Each component has its own initializer. All unknown first level tags will be put into settings clause which is compatible with WebSphere Multichannel Bank Transformation Toolkit version 4.3 usages.
In the following example, you can see that after the migration, each data's definition kColl has extFile and initializer:
<kColl id="data"> <field id="field" value="com.ibm.btt.base.DataField"/> <field id="iColl" value="com.fortis.be.rbaa.commons.data.IndexedCollection" description="compound"/> <field id="kColl" value="com.ibm.btt.base.KeyedCollection" description="compound"/> <field id="operDef" value="com.ibm.btt.base.OperField"/> <field id="refData"/> <field id="sessionEntry" value="com.ibm.btt.base.SessionEntry"/> <field id="sessionTable" value="com.ibm.btt.base.SessionTable"/> <!-- Ban WSBCC Commons --> <field id="finalField" value="com.bank.be.commons.data.FinalDataField"/> </kColl>
<kColl id="data"> <field id="extFile" value="dsedata.xml" /> <field id="initializer" value="com.ibm.btt.base.DataInitializer" /><kColl id="classTable"> <field id="field" value="com.ibm.btt.base.DataField"/> <field id="iColl" value="com.fortis.be.rbaa.commons.data.IndexedCollection" description="compound"/> <field id="kColl" value="com.ibm.btt.base.KeyedCollection" description="compound"/> <field id="operDef" value="com.ibm.btt.base.OperField"/> <field id="refData"/> <field id="sessionEntry" value="com.ibm.btt.base.SessionEntry"/> <field id="sessionTable" value="com.ibm.btt.base.SessionTable"/> <!-- Bank WSBCC Commons --> <field id="finalField" value="com.bank.be.commons.data.FinalDataField"/> </kColl> </kColl>