Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Retired
Posts: 86
Registered: ‎07-11-2008
My Device: Not Specified

File and Email monitoring questions

1. Can we get BlackBerry SmartPhone file upload and file download activity and any related meta-data? If so, how?


The file APIs could be used to index all the files on the device however there is no way to get an audit of all user (or third party app) activity relating to how this file has been moved around, copied, shared, etc. 

2. Can we get BlackBerry SmartPhone location data, and if so, how? Hopefully, we can set specific filters on this, to avoid getting too much data.

GPS / location APIs are supported and criteria like intervals, accuracy, etc can all be configured.

3. Can we get information about email attachments- so that we can perform keyword searches. And, can we get any metadata associated with the email attachments (size, date created, hash file, etc.)

This is expected to be supported for BlackBerry 10, through the Native SDK, however a review needs to be conducted to confirm.  It is available today for BlackBerry 7 with the Java SDK and the BlackBerry Web Works SDK through a custom Java extension.

4. What are our options configuring the Extension plug-in APIs (if this is possible)

More information/clarification is required to answer this.

5. Do you have any rule of thumb sizing guides that might help us estimate amount of data, for the information we are pulling into the solution

The amount of data collected from the device and transmitted over the network could be minimized with compression so it’s a matter of how you store the data.  If sending compressed text, even if days worth of montioring data, the actual transfer amount should not be significant.  And if sending over WiFI, size considerations don't much factor in at all.  The only gotchas are users with very small data plans and/or MDS 413 errors for file size of an individual transmission if delivering the data to a server which resides behind the firewall - check the knowledge base for solutions here.

Brian Zubert
Technical Partnership Manager
Research In Motion