How to force a given server as connection server

When a user connects on an endpoint, he can connect on several servers, depending on the configuration:

• The main server is the server on which the folder file hierarchy is stored. This can be the unique server available.
• Additional execution servers ("run-time" servers) can have been added for scalability purposes. This is defined in the endpoint definition.

By default, a user that connects on an endpoint associated to the solution will use one of the available servers (the algorithm that assigns the server is a round-robin server).

Some exceptions exist: for some administration operations (such as folder validation), the server assigned for execution is automatically the main server.

If for any reason you want assign a given server for the execution of some process in a multi-server environment, you can assign a tag associated to this server to a group and connect as a user that belongs only to this group.

The assignment of a given server can be interesting if you want dedicate a server for performance purposes to some dedicated operations (such as web service execution or heavy operations).

The main principles of the server assignment are described in the solutions documentation.