How can I get the "Search service name" in client application?

While I install the WildFire, I set the “Server Name”(included in “Server Settings” of “Server Manager” sidebar item located under the “Server” tab in the Wildfire Admin Console), for example, “WildFireServer”, then the “Search service name” is “search.WildFireServer”. Then in client application, I must use “search.WildFireServer” to search users. But if I change the “Server Name” to “NewServerName”, then the “Search service name” is “search.NewServerName”. So far in client application, I must use “search.WildFireServer” to search users now.

My question is how can I get the “Search service name” in my client application? Cause this name varies from installation to installation.

After changing the server name, did you restart Wildfire? While not precisely documented, its a good idea to do that since some things remember the server name and may not expect it to change.

I think it’‘s not the question of whether restartinig the server. Because when I set the “Server Name” by its IP Address(such as 192.168.18.1), the spart uses “search.192.168.18.1” to search users. Then I change the “Server Name” to its computer name(such as “WildFireServer”), and restart the server, then spart uses “search.WildFireServer” to search users. So my question is how the client application can get the server’'s “Server Name” infomation?

clients should get the server name when they connect. This is why a restart is a good idea- clients that connected before the name change wont know about the new name. Really, the server name needs to be considered a static. If you want to change it, you should restart the server, or at the very least make everyone sign off.

First, thanks a lot for your reply.

But as I described before, spark can correctly get server’'s “Search service name” information, whether it use domain name or IP address to login. So my question is how it work?

somebody help me!

Could you describe exactly what you would like answered. THere seems to be a miss understanding of what your question was.