Problem with Operations console installation

[Catherine]

Hello,

I have installed TM1 V10.2 on a windows 2008 R2 server.
I tried to follow the steps described in IBM guide to be able to use operations console. Regarding certificates, I had the message "Certificate was added to keystore", except that in my configuration I had only a 7.0 folder (not 6.0 as written in IBM guide).
The problème is that I can not find the file Obsconfig.xml. I don't have any tm1operationsconsole folder in the webapps folder.

I did not find any guide regarding V10.2 Operations console installation and I followed the V10.1 guide.

Are there any changes in V10.2 ? Any ideas regarding my problem ?

Thank you

[declanr]

They moved the opsconfig.xml in version 10.2 (a move which I believe is undocumented... I don't even know if the opsconfig file is mentioned anymore as the guide recommends you update it through pmhub/admin) a standard install will see the opsconfig.xml in the following folder:
C:\Program Files\ibm\cognos\tm1_64\bin64\opsconsoledata

Below is the 10.2 install guide:
http://pic.dhe.ibm.com/infocenter/cbi/v ... ncole.html

[Catherine]

Thanks for your answer.
I had searched for the file only in Webapps folder... As a matter of fact, that's always a mistery to know why some changes are undocumented...
I was able to modify the ObsConfig.xml file, and to start the Operations Console.
Now I have to get familiar with this new interface and understand how it works but that's another question !

[Sebastian.Klein]

I was able to modify the ObsConfig.xml file, and to start the Operations Console.

That is not the correct way IBM wants you to make changes to the config file. As of TM1 10.2 there exists a new config site which you can access through following URL: http://Servername:Portnummer/pmhub/pm/admin

Then you must go to com.ibm.ba.pm.opsconsole.monitor.tm1.TM1OpsConsoleMonitor and com.ibm.ba.pm.opsconsole.monitor.tm1.TM1OpsConsoleMonitor.dictionary. Here you can configure the Operations Console like in the OpsConfig.xml.

I mention this because I have read here in the forum, that if you manually edit the OpsConfig.xml it can be overwritten by a service restart or what else. So if you want to be safe, configure it like I described above.

[declanr]

I mention this because I have read here in the forum, that if you manually edit the OpsConfig.xml it can be overwritten by a service restart or what else. So if you want to be safe, configure it like I described above.

True ... but likewise I have found a couple of times that after changing the pmhub/admin options (even with full service restarts) it still doesn't pick up the changes; as such I've made it habit to change it in both there and the opsconfig.xml file... overkill 90% of the time but it is guaranteed to get the job done (or at least it has always worked thus far). I think this is just due to the customers in question having pretty hardcore lockdowns on some changes.

Thanks for your answer.
As a matter of fact, that's always a mistery to know why some changes are undocumented...

In this instance I am sure it is due to them wanting you to just use the pmhub but I'm more concerned about the stuff they leave undocumented for multiple versions... or in fact the stuff that gets documented completely incorrectly