When creating a newproject in 7.0(2), CVPDataFeedLog and CVPSNMPLog are automatically added as loggers already with config files. If for some reason you don't have the datafeed logger, here are some steps on how to re-add it.

How to enable DatafeedLogger using Call Studio:
1. Go to the Studio app's Project/Properties/Call Studio/General Settings window
2. If CVPDatafeedLog is not listed under "Loggers", then Click Add
3. You will be asked to enter a Name and Class.
    Name: CVPDatafeedLog
    Class: com.cisco.cvp.vxml.datafeed.DatafeedLogger
4. Select "Enforce Call Event Order" and "Include Configuration File". When "Enforce Call Event Order" is checked VXML Server will ensure that the logger receives the logger events for a call in the order in which they occurred in the call.
5. Click edit to make changes to the configuration file. Here are the default settings:
Configuration File Name: CVPDatafeedLoggerConfig.properties
File Content:
debug=false
#Logger Events
LoggerEvent.1=start
LoggerEvent.2=end
LoggerEvent.3=elementEnter
LoggerEvent.4=elementExit
LoggerEvent.5=elementData
LoggerEvent.6=elementFlag
LoggerEvent.7=defaultInteraction
LoggerEvent.8=hotlink
LoggerEvent.9=hotevent
LoggerEvent.10=warning
LoggerEvent.11=custom
LoggerEvent.12=systemError
LoggerEvent.13=javaApiError
LoggerEvent.14=vxmlError
LoggerEvent.15=xmlApiError
#Element type definitions
 
Note: By Clicking "Restore Defaults" in the General Setting window, among other things, the CVPDatafeedLog will be re-added with the default settings.
6. Once you are done configuring the logger, save your changes and deploy your app to the VXML Server. Be sure to update the app in VXML Server if it is an existing app, or deply the app if it is a new application.
 
How to enable DatafeedLogger through VXML Server (if you do not have access to the Call Studio app):
 
1. Go to the application folder for the app in question in VXML Server
2. Open <APP_NAME>/data/application/settings.xml. Here you will see all the loggers listed for your application between the tag <loggers> ...... </loggers>
3. Add the following
<logger_instance class="com.cisco.cvp.vxml.datafeed.DatafeedLogger" configuration="CVPDatafeedLoggerConfig.properties" enforce_call_event_order="true" name="CVPDatafeedLog"/>
 
Note that the logger name must be unique.
 
4. As you can see the "configuration" attribute has the name of the configuration file that was mentioned in step 5 above. Simply create a file with this name in the current directory, and enter the File Contents from step 5 above.
 
The preferred way to add a logger to an app is by using Call Studio and then re-deploying the app to VXML Server.


Note that reporting must be enabled for this VXML Server through OAMP. You can refer to the Config and Admin Guide for more information on enabling reporting and creating filters.

Standalone VXML Server
 
If you have a standalone VXML Server a quick way to check is by looking at the reporting statistics in OAMP. When you place a call to your application, you should see the "Database Writes" increasing.
 
Non-standalone VXML Server
 
The best way to check if you are not using a standalone VXML Server is by quering the reporting server database. Another thing you can do is look at the <CVP_HOME>\logs\VXML logs and first see if there are any error about datafeed logger. If you don't have any errors, place a call and check for datafeed information in thees logs. You can also look at the reporting server logs (on your reporting server box) and you should see events being logged here.
 
 

Enable debugs to look at the logs in detail and post further