Having done a number of TM1 10 installs recently I thought it was worth noting some of my experiences with how TM1 now has a Cognos Configuration tool.
After installing TM1 10.1 or 10.1.1 you will be presented with an option to start Cognos Configuration. You will not at this stage if you check your Services that only TM1Webservice has been created. In Cognos Configuration if you then start the Admin Server it will then create the corresponding service.
Note at this stage how Excelservices is set for manual start and needs changing and you should set all the TM1 services to be run under an admin account.
Having Cognos Configuration for TM1 makes it very easy to create a TM1 server instance and then pointing it at your cfg file. That’s the good part.
The bad part is that although easy to create the TM1 server instance you will find it impossible to then delete it. You will also find you cannot delete the corresponding Service using the traditional tm1sd.exe –remove “servername”
I have found the best thing to do is to go back to the traditional hacking of the registry. There is a good write up on developerworks here:
I have had to do this to delete an entry or to edit the config path of an existing entry. Anyone can see that hacking the registry is ugly but although cognos configuration is a step forward to looking like the rest of the cognos product suite it still needs work.