Usage Tracking for BI Publisher

Question

We need to track Oracle BI EE Suite user's activity. There is Usage Tracking option in exSiebel products making possible to track what and when user did. It's needed to do similar audit for BI Publisher.
It's works "by itself" for Publisher reports built on top of BI Server infrastructure. Usage Tracking does all the job. But what should we do to audit reports using direct sql requests to the database?
PS
We have sucurity model integrated with Oracle BI EE Server

Answer 1

Here is an interview with Kurt Wolff, which is one of the original OBIEE developers from the nQuire days:
http://obibb.wordpress.com/2010/08/23/obibb-%E2%80%93-interviews-kurt-wolff/
This is particularly relevant of how I feel about OBIEE 11g so far...
"I don’t really know if there are any new features that are important to me in my current work or not. There may be features that help Oracle sell more product, but that’s different.
Over two years ago I submitted a list of 20 “little” enhancements that, as someone who on a daily basis worked developing analytic apps with OBIEE, I thought would be really beneficial. They were “little” in the sense that I thought the dev team could knock them all out in less than three weeks’ time. Seriously big impact with seriously little work.
Instead, we’re getting what appears to be a major re-write of the product, which raises questions in my mind about compatibility, unlearning, and new bugs. What I know about new features – well, they’re not so compelling. Sure, if you have a need to integrate Essbase with your other data, that’s good. But in my present situation, it’s irrelevant, and I’m planning on taking a lot of time to evaluate the new release before moving ahead with it."