TM1 Admin Host in Web

[winoth]

Hi,

What will be the functionality of the TM1 Admin host if we install it on a web server?
There is a separate application server in addition to the web server and all the TM1 instances are installed in the application server.

Thanks,
Vinoth

[lotsaram]

Hi,

What will be the functionality of the TM1 Admin host if we install it on a web server?
There is a separate application server in addition to the web server and all the TM1 instances are installed in the application server.

Thanks,
Vinoth

if you think about it I'm sure you can answer your own question.

[tomok]

To be fair to the OP, I think he misused the term functionality and really meant performance. Obviously, the functionality of the Admin Host program is the same regardless of where you run it. The performance could change if you run it on a box other then the actual TM1 server but probably not. It's not a very resource intensive app.

[lotsaram]

To be fair to the OP, I think he misused the term functionality and really meant performance. Obviously, the functionality of the Admin Host program is the same regardless of where you run it. The performance could change if you run it on a box other then the actual TM1 server but probably not. It's not a very resource intensive app.

I disagree. I think functionality was the intended meaning, as in "what does the TM1 admin host do if installed on the web server?" And it is also pretty clear that this is on a web server in addition to an application server where the admin host and TM1 database services are already installed. In which case I think we know what the answer is, and if the OP isn't sure then he can mull it over.

[winoth]

Hi lotsaram,

You are correct. That was exactly the question I was asking. I tried installing the admin host in one of our sandbox environment and the perfomance over the web has increased rapidly. That is, with the admin host installed in the web, if a user enters the admin server name in the web login page it refreshes the available TM1 servers instantly (within a second). On the other hand if there is no admin host installed in the web then it takes atleast 5 to 10 secs to load the available TM1 servers.

So I was wondering how the admin host increases the perfomance rapidly. The main function of the admin host is to keep track of all the available TM1 servers present in the network. So I thought that the admin host installed in the web would keep track of all the available TM1 instances in the network. So I tried connecting to the admin host installed in the web via perspectives but I was not able to find any available TM1 servers under it.

1) How did the admin host increases the perfomance via web rapidly?
2) Does admin host have any other additional functionality if installed in the web?

[lotsaram]

Without any TM1 databases connecting to it a TM1 admin host service does precisely ..... NOTHING. There is therefore not really any point of installing and running an admin host unless TM1 servers are going to connect to it!

1) How did the admin host increases the perfomance via web rapidly?
2) Does admin host have any other additional functionality if installed in the web?

OK so you have now clarified that you installed the admin host on the web server and the TM1 web default login page seems to come up faster than it did before and you are wondering why? (might have been good to include this information up front as it seems quite relevant and important, but hey maybe that's only me.) It seems from your description that the admin host setting in the web.config file is blank. For all TM1 clients if no admin host setting is given then the default value is localhost. If a localhost can't be found then the client continues to search for a while before it gives up leading to a hang time. Sounds like this is what you are experiencing. With an admin host running on the web server the localhost is found straight away but returns no servers so the login sheet renders straight away and you can then enter the admin host of choice.

Rather then installing the admin host on the web server you could get the same faster initial rendering of the login screen and save the work of entering the admin host value by having this setting pre-configured in the web.config. That would be the usual thing to do.

[winoth]

It seems from your description that the admin host setting in the web.config file is blank. For all TM1 clients if no admin host setting is given then the default value is localhost. If a localhost can't be found then the client continues to search for a while before it gives up leading to a hang time. Sounds like this is what you are experiencing. With an admin host running on the web server the localhost is found straight away but returns no servers so the login sheet renders straight away and you can then enter the admin host of choice.

Yes, I agree with your point. But what we are facing is slightly different. Even after installing the admin server in the web we are experiencing an initial hang time. But TM1 perfomance is rapidly increased only after we get the login page. When we enter a admin host name and when we click the refresh button all the available TM1 servers are loaded within a second. Without the admin server installed it would take atleast 5 to 10 secs. I tested it by giving different admin host names we have in our environment. I guess such a rapid increase in the perfomance can only be achieved only if the admin host has the details of all the available TM1 servers in the network. Please correct me if I am wrong.

[tomok]

Please correct me if I am wrong.

You are wrong. Did you even read lotsaram's post? The reason for the delay in startup is because the web client is searching for available admin hosts. If you would just specify the admin host in the web.config file (the setting is called AdminHostName) then it wouldn't have to search and the list of servers would appear immediately.