7.16. Running multiple server connections on a client

In some configurations the necessity arises that a client connects to multiple servers. One reason might be that clients from branch offices connect over an unreliable connection to an IDERI note server in a central location. If the connection to the central location is interrupted, it would be desirable if the client components could instead connect to a local IDERI note server where administrators in the branch office can instead create messages that the clients can receive while the connection to the central server is interrupted (one such message of local origin could be an information that the connection to the central location is currently down and that therefore some other services will not be available).

The IDERI note client currently has no ability to dynamically switch between multiple servers but the same effect can be achieved by running multiple client instances in parallel on each desktop. Please refer to section 7.29 that discribes how secondary client instances can be started from within clientlaunch.exe.

Multiple instances of an IDERI note client do not share any data so they will not step on each others feet. However, you need to be aware that multiple client instances also display messages independently from each other, so it is possible that multiple messages will be displayed at the same time in such a configuration, each displaying one message from the server it is connected to.

Note that each IDERI note client instance will then also launch a separate IDERI note ticker instance. If you want to have the IDERI note ticker running for only one client instance, you should add the server names of the ticker instances that should not be started to the REG_SZ value “ExcludedServers” in the key HKEY_LOCAL_MACHINE\SOFTWARE\ideri\inotick. This key specifies a comma separated list of server names. You can also specify this list at installation time of the IDERI note ticker with the property named “EXCLUDED_SERVERS”.