Configuring Clients

On Windows, on each client computer, create the following directory:
C:\ProgramData\DassaultSystemes\Licenses
On Linux, create the following directory:
/var/DassaultSystemes/Licenses
Go to the directory and create an ANSI file (multi-bytes such as UNICODE are not supported) named:
DSLicSrv.txt
Edit the file to declare the license server to which the client can connect.
The syntax of the declaration is as follows:
```
servername:portnumber
```
The server name can be declared as:
- a simple hostname, for example: lw5ses1dsy:4085
- a full qualified domain name, for example: lw5ses1dsy.dsy.com:4085
- an IPV4 address, for example: 10.232.70.1:4085
- an IPV6 address, for example: [2a00:4b00:220:172::103]:4085
The port number is the license server listening port, not the administration port.
Note that if the license server is on the same computer as the client computer, you must use the special keyword localhost instead of the computer name, for example:
```
localhost:4085
```
Note:
The syntax for failover servers is different. The three failover servers must all be referenced on the same line as follows:
```
server1:4085,server2:4085,server3:4085
```
By default, load balancing of the three failover members is performed automatically by the licensing client code. At startup, the licensing client process selects randomly the failover member to contact from the three members declared. If the first selected member is down, the second member is randomly selected, and so forth. This ensures that the three members are statistically contacted by the same number of clients and results in automatic load balancing on the three members.
However, it is also possible to specify the order of priority in which failover members are contacted by the licensing client, replacing randomization by an explicit order defined by the administrator. This can be useful in the following cases, for example if:
- one member is more (or less) powerful than the others
- one member is located much closer to (or further from) the licensing clients than the others
- one member cannot be reached due to proxy constraints
- one member is temporarily down.
Note that you cannot mix both automatic and manual configurations: in other words, the three failover members are either randomly accessed or are accessed through the specified order. So you cannot, for example, declare the first member then set random access to the remaining two members.

To explicitly specify an order of priority order between the failover members, use the following separator:
```
>
```
instead of:
```
,
```
which is reserved for automatic load balancing.
The following declaration is valid, for example:
```
licmbr1:4085>licmbr2:4085>licmbr3:4085
```
If several logical (i.e. standalone or failover) license servers need to be accessed, add a new line for each logical license server.
In this context, when a client requests a license and this license is not already granted by one of the declared logical servers, then the order in which the logical license servers is declared is observed: if a license is available on the first declared logical server, this one is taken; if not, if a license is available on the second declared logical server, then this one is taken, and so forth.
To add a comment to this file, begin the line with a #.
Optionally, check that the file is correctly configured.
The license client-side DSCheckLS command parses the DSLicSrv.txt file to check license server availability, and reports errors if, for example, the file is incorrectly configured. For more information, see the documentation of your license client product.