Monitor / Detect Package Changes

[mhope]

I would like to monitor/detect when a package has changed.  Do you use third party tools or perhaps SQL against the CM or Audit tables?  If the latter, a code sample will be truly appreciated.  Thank you.

[cognos810]

Hello mhope,
The quickest way without going the SDK route would be query the CMOBJECTS table in your content store. Not sure, which cognos version you are using, but the below SQL will list the details for all the packages in your environment, including the My Folders content of your user.
/* THIS IS SQL SERVER BASED SQL, TIME FUNCTION WILL NEED TO BE CHANGED IF USING NAY OTHER DB*/
select * from CMOBJNAMES objnm
inner join CMOBJECTS cmobj on
objnm.CMID=cmobj.CMID
and cmobj.CLASSID=18
and cmobj.MODIFIED BETWEEN DATEADD(MINUTE, -30, CURRENT_TIMESTAMP) and CURRENT_TIMESTAMP

Get a FM package going to see the results of the above query and base an event studio event on it to be scheduled and run every 30 minutes. If any results are returned send yourself an email as a second step of the event in event studio.

PS: An SDK application would be the most ideal way to do this.


Hope it helps!!!
-Cognos810

[mhope]

Cognos810 - Sorry for the very late reply, other priorities... I am still lobbying to have the SDK, but I do have query access to the CM.  With that said, your code is helpful.  Thank you.  Mike

[bdbits]

Just FYI: It sounds like maybe you already have an admin license. If the resistance to give you the SDK is licensing cost related, I was recently told from an IBM rep that the licensing changes last year mean you now get an SDK license with an administrator license. Which for me at least is awesome, as I have wanted to take a shot at writing some utilities with the SDK for some time but did not have the licensing (and I do have admin).

[Andrew Weiss]

mhope,

What is it that you're looking to do when a package changes?  We have 2 solutions that might be a fit.  First is our version control solution which would obviously capture changes to the object and log that to an easy to database which can easily be reported on (e.g. with a event studio report or database trigger).  The second is the MetaManager script api which can query the packages on a regular basis and find ones with a recent modification time.

If you're interested in using 3rd party tools to address the issue please let me know.  Here's a link to some more information on both solutions:

http://www.bspsoftware.com/ics
http://www.bspsoftware.com/api

Thanks,
Andrew Weiss