Runtime tools : Service components : Smart channel services : Smart data collector : Server collector : Smart visit server collector
  
Smart visit server collector
The UDTT Smart data collector supports collecting visit data from server side.
Refer to the general steps in Server collector, and configure the visit collecting in the smartCollectorConfigFile fileļ¼š
<SmartChannelDataCollect.xml>
<props id="classTable">
<entry key="SmartCollectorConfig4Transaction"
value="com.ibm.btt.channel.SmartCollectorConfig4Transaction"></entry>
<entry key="SmartCollectorConfig"
value="com.ibm.btt.channel.SmartCollectorConfig"></entry>
<entry key="SmartDataCollectJMSImpl"
value="com.ibm.btt.channel.smart.dao.jms.SmartDataCollectJMSImpl"></entry>
<entry key="SmartDataCollectDefaultImpl"
value="com.ibm.btt.channel.smart.dao.jpa.SmartDataCollectDAOImpl"></entry>
</props>
<SmartDataCollectJMSImpl id="jmsDAOImpl"
jmsConnectionFactory="jms/SmartChannelCF" jmsSendQueue="jms/SmartQueue">
</SmartDataCollectJMSImpl>
<SmartDataCollectDefaultImpl id="smartDAOImpl"> </SmartDataCollectDefaultImpl>

<SmartCollectorConfig id="smartCollectorConfig"
sampleRateRuleServiceName="globalDataCollectorRuleService"
smartDAO="smartDAOImpl">
<ref Injection="transactionCollectorConfig"
refId="TransactionDataCollectorConfig"/>
</SmartCollectorConfig>
<java.util.ArrayList id="TransactionDataCollectorConfig">
<SmartCollectorConfig4Transaction transactionID="signOp"
actionType="visit">
<map Injection="dataMap">
<entry key="name" value="userId"></entry> </map>
</SmartCollectorConfig4Transaction>
</java.util.ArrayList>
</SmartChannelDataCollect.xml>
For the visit server collector, the actionType should be set as visit. The transactionID field should be set the sign operation name.
Note If the actionType is visit, one entry that valued as userId must be defined in the datamap. In the previous sample codes, the entry key is name, which should be mapped in the data in the request web page; the entry value is userId, which is used to map into the visitLog bean.