In BTT version 4.3, the component package is under its own kColl:
<kColl id="packages">
<kColl id="operations">
<field id="packageEJS1" value="com.ibm.dse.appl.ej.server"/>
</kColl>
<kColl id="processors">
<field id="package1" value="com.ibm.dse.automaton"/>
<field id="package2" value="com.ibm.dse.automaton.ext"/>
</kColl>
<kColl id="typedData">
<field id="package1" value="com.ibm.dse.base.types.ext"/>
<field id="package2" value="com.ibm.dse.base.types"/>
</kColl>
</kColl>
After you migrate to BTT version 6.1.2, all the packages for type,
operation and processor are under the
<kColl id="packages">.
Following is the code sample:
<kColl id="type">
<kColl id="packages">
<field id="package1" value="com.ibm.dse.base.types.ext"/>
<field id="package2" value="com.ibm.dse.base.types"/>
</kColl>
....
</kColl>