How to force a given server as connection server

When a user connects to an endpoint, the connection can be on several servers depending on the configuration:

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

By default, a user who connects to an endpoint associated with the solution uses one of the available server. 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 to assign a given server for the execution of some process in a multiserver environment, you can define a tag associating this server with a group, and connect as a user who belongs only to this group.

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

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