Useful details on testing configuration and debugging of the mobile SDKs.
QA and Validation Setup
This first setup can be used without having access to the app source code or setting any special debug settings in the SDK itself.
Download a traffic monitoring tool: Wireshark
Watch the Webtrends requests being made from your app as they happen.
Download Wireshark. Wireshark is a free open source network request and packet analyzer (Wikipedia). Install it onto a machine where you can run an emulator for the app or plug your device(s) into and make your internet requests through.
When you have Wireshark running and your emulator or device proxied through your internet connection.
Note that some devices require you to have the development environment at least partially installed to allow you to proxy through the computer. This doesn't mean you need the source code though.
Wireshark will listen to all your traffic through any of your network connections. Here are a couple screen shots to show you how to
1. Attach Wireshark to one of your network connections. It supports "virtual" connections too from VMs, etc.
2. Filter the Wireshark traffic to listen to HTTP traffic and not everything or you'll be flooded with too much information
3. Once you have traffic requests from your device flowing, watch for events to the domain name dc.webrends.com. All actions will show up here. Please note though that Webtrends defaults all traffic as HTTPS meaning it is secure transport. That means that while you can see the events, you can't see the individual parameters because they are sent in the POST body and listening tools can't examine the contents of HTTPS (or that would be pretty poor security
Click around and watch your app kick off Webtrends events as they happen.
If you want to debug the actual parameters being sent you need to change the Webtrends protocol to HTTP instead. This is, naturally, only recommended for QA and Development and you should ship your app using HTTP.
Fiddler is a simpler and easier to use tool, the only reason it doesn't get my preferred status is because you need to set up a proxy for it to be able to see your app emulator traffic which, while not difficult, is one extra step that can trip you up.
Development and Debugging Setup
If you have access to the app source code, you can make the following changes to assist in testing and debugging of the app.
Set to HTTP instead of HTTPS
This allows you to use the same setup as above (using Wireshark or Fiddler) and you can also look at the contents of the HTTP POST requests. This is incredibly useful because you can then see what kinds of events are being sent on which actions as well as to examine the parameter values.
The settings is wt_dc_url
Edit the webtrends.plist or webtrends.xml (as the platform demands).
Parameters and Events
Here is a document of all the Webtrends parameters that will be sent from the SDKs. There are pivot tables by event type, device platform, etc.
Set the SDK to debug mode. This has two effects: it writes event execution in the SDKs to the app dev tools terminal logging and it also echoes back the event that the Webtrends servers saw and interpreted from the event that was sent. This response is in place of the simple HTTP return code and you can see the parameters as they are being recorded by Webtrends servers.
The setting is wt_dc_debug
DC API Debugging
If you want the Webtrends servers themselves to simply respond with the full log file line that is being recorded, you can change the wt_dc_url to contain the debug setting. If you are debugging with the SDK itself, this step is unnecessary.