If you are unable to create a new account, please email support@bspsoftware.com

 

Powerplay audit tables (PPES_REQUEST, PPES_SESSION etc.) do NOT preserve history

Started by spjyoti, 18 Sep 2009 11:16:47 AM

Previous topic - Next topic

spjyoti

We observed that the Powerplay audit tables only capture the last       
activity performed by a user in the upfront, rather than maintaining   
the history.                                                           
We are enabling Powerplay cube level auditing functionality supported   
by Cognos Series 7 Version 4 suite.                                     
All steps have been followed properly to configure auditing as         
specified in "COGNOS Business Intelligence Series 7 - Cognos PowerPlay 
- Enterprise Server Guide" (pes.pdf)                                   
The backend tables including PPES_MEASURE_USAGE,  PPES_DIM_USAGE,       
PPES_REQUEST, PPES_USER_SOURCE, PPES_SESSION  have been configured and  being populated with logging data through the PPESAuditFileProcessor   
Utility.                                                               
The entries posted in "UserInfo.imr", "MeasureUsage.imr" and           
"DimensionUsage.imr" appear to be incomplete. These reports are         
delivered powerplay audit reports and can be found in the following     
location of installation: \cer5\samples\ppwb\audit\                     
Steps to recreate issue:                                               
1. Capture PPES_DIM_USAGE.DIM_COUNT, PPES_REQUEST.START_TIME,           
PPES_REQUEST.END_TIME,   PPES_MEASURE_USAGE.MEASURE_COUNT for a         
particular user having access to the published Powerplay               
cubes.                                                                 
2. Using the above User Id, login to Cognos Upfront and navigate through more than one cube.                                                                   
3. Access any one dimension/measure in each one of the cubes and logoff.                                                                 
4. Run PPESAuditFileProcessor utility to transfer information from Audit log to backend table.                                             
5. Query tables mentioned in step 1 for the particular cube and user Id
to see the difference.                                                 
6. We expect that an entry for all cubes navigated within the active   
session should be present in the reports.                               
7. Instead, only the entry corresponding to the last cube navigated  gets stored in the PPES_REQUEST table. Hence, the reports fail to fetch the history. The history of activities performed within an active session is not maintained. The cube last navigated before the transfer utility is run, seems to overwrite all previous entries recorded by the log.