Rename TM1 admin host

[mvanrooyen]

I've read other posts on guys trying to rename the TM1 admin host at the root node in Server Explorer but no-one has come up with a way to do this. Is this at all possible? We have four different admin hosts with multiple instances on each and it's frustrating having to always go back to File\Options... to see which host we're connected to. I'd prefer to be able to rename the host in some way. Short of that, I may have to put in a dummy instance under TM1 on heach host to indicate which admin host we're connected to? Any ideas? Thanks.

[lotsaram]

Since changing admin hosts will disconnect any open sessions on the old admin host I don't think there is any way to toggle admin hosts without going into the options dialog. But I do like your idea of a dummy server that has no purpose other than to advertise the admin host name, I just might do this myself.

You do know that you can connect to multiple admin hosts by separating with a semi-colon? Or is it that you can't do this because the servers are identically named as opposed to containing an environment identifier?

[Paul Segal]

I use dummy instances to differentiate identically named servers, and it works without any problems. I do it primarily to enable all the user reports to run using the one server name no matter which server they are actually connected to.

[lotsaram]

I use dummy instances to differentiate identically named servers, and it works without any problems. I do it primarily to enable all the user reports to run using the one server name no matter which server they are actually connected to.

If that's the only reason for not having distinct server names there's a simple trick using the tmuser function to automatically detect the server name. It should be in the tips and useful code somewhere.

[mvanrooyen]

Hi guys,

Thanks for the replies. Lotsaram, I tried connecting to multiple admin hosts but we are actually using identically named instances on the various hosts (Dev, QA and Production servers with identical instances on each) so connecting to multiple hosts in this instance is not helping but I appreciate the hint.

So it appears that we are stuck with creating a dummy instance to identify the admin host? Would be great if we could just rename the root level TM1 node....

[wissew]

Here's a suggestion:
Use QA & Dev as a prefix to the TM1 server name. All will be available when you list multiple hosts as the admin host. You will just need to add a find and replace to your migration process for templates and reports. You can move TM1 objects (*.pro, *.cub, etc.....) between data directories with out having to change anything.

[mvanrooyen]

Thanks Wissew for that. I'll look into it. With the amount of changes on the templates (around 60 - 70 sheets per instance) the effort in changing the server name with find/replace might be more than the trouble of having a dummy instance. Appreciate the suggestion though!

[lotsaram]

Thanks Wissew for that. I'll look into it. With the amount of changes on the templates (around 60 - 70 sheets per instance) the effort in changing the server name with find/replace might be more than the trouble of having a dummy instance. Appreciate the suggestion though!

Reread the hint I gave you and do a quick search in the tips. If you set up your Excel sheets correctly then there is no need to find/replace to transfer between environments with differently named servers.

[ParisHilton]

Resurrecting this as it's not TOO old.

But... I'd like to use the semicolon separation of server names and have two different admin host names, so I can clearly see which 'servers' I'm connecting to. At the moment I'm using the workaround of prefixing UAT servers, but it's a bit ugly. Far better in archtiect to see....

TM1
server 1
server 2
server n
TM1UAT
server 1
server 2
server n


rather than
TM1
server 1
server 2
server n
UAT server 1
UAT server 2
UAT server 3

I guess there's no documented way of doing it though (tempted to try and hack the TM1 binary, but that would be mental).