In BTT version 7.0, the configuration of each component is defined in the component's kColl. And each component has its own initializer.
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"/> <!-- Fortis WSBCC Commons --> <field id="finalField" value="com.fortis.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"/> <!-- Fortis WSBCC Commons --> <field id="finalField" value="com.fortis.be.commons.data.FinalDataField"/> </kColl> </kColl>