TM1 ver 9.1.x (and below) Audit log

[gabi]

Hello all,

I'm wondering if there is any workaround/solution to audit user activities (especially user logon/logoff) on TM1 ver. 9.1.x. (requested by Information Security)
I have few directions and I'll appreciate your advice:
1. Use TM1 performance monitor and export relevant user information to flat file (I'm not sure if user logon/logoff is logged - I just found logging of number of connected users.
2. Dig users status changes from the transaction log.
3. Use TM1 performance counters (Windows performance monitor) to log user activities.
{I had a problem to find 'Applix TM1' (TM1 9.1.4) or 'IBM cognos TM1' (TM1 9.4.1) object counters in the Windows perfmon - even after manually registered the TM1perfmondll.dll and restart TM1)

Thnk you,
Gabi

[George Regateiro]

Though it will not get you 100% acurate information (we use it for tracking usage trends and not specific logins), we use the .net API and have a scheduled executable that pulls a listing of the users. It is a failry quick login, return the users to an array list and logout so there is not a huge impact on the system. Since it is scheduled we do not capture all the data, but trends are good with us.

[gabi]

Thank you for your reply, George

Guys,
Any other idea to track users login to TM1 on ver 9.1.x?

Thank you,
Gabi

[Steve Rowe]

I've not tested this but could you turn logging on for the client properties cube and then query the TM1 logs for changes to this cube. This should show log in activity
Cheers

[Steve Vincent]

I've not tested this but could you turn logging on for the client properties cube and then query the TM1 logs for changes to this cube. This should show log in activity
Cheers

Afraid not, Cognos broke that in 9.1 with the changes to the licensing and a brief test in 9.4 didn't show it to be fixed either. I use that method in 9.0 to track usage in a cube and it works a charm, but it seriously needs fixing by Cognos if we are ever to accurately track usage.

[lotsaram]

Actually, it is truly broken only in 9.1.3. In 9.1.4 they introduced ClientPropertiesSyncInterval to the tm1s.cfg file. Including this parameter in the config file starts a housekeeper thread that wakes at an interval of seconds specified by the parameter. i.e. ClientPropertiesSyncInterval=120 will mean the thread wakes every 2 minutes and writes "ACTIVE" or "" to the }ClientProperties cube.

This is in the 9.1 SP4 release notes. Although absent from 9.4 documentation this parameter setting also works in 9.4. Also little known is that this is an "active parameter," if the parameter value is changed while the server is running this will alter the frequency with which client status is logged.

[Andy Key]

ClientPropertiesSyncInterval is mentioned in the 9.4 MR1 FP1 release notes. Give them another couple of releases and it will find its way into the main docs...

[aanensonex]

I need help with db auditing models. How do I approach the problem below? Your company received a request from its most important partner to comply with industry standards, which requires an audit trail of all financial data. Your manager summoned you to her office, explaining this new requirement and assigning you to design the architecture and a high-level auditing model. Compliance requires that all data changes be recorded in the history tables and that the auditing model employ a mechanism to audit any user on demand.
__________________
market samurai ~ marketsamurai ~ marketsamurai.com