Setup Operations

This section describes setup operations on the licensing clients.

  1. Copy the authentication file to all the licensing clients in the following default location:

    • C:\ProgramData\DassaultSystemes\Licenses (Windows)
    • /var/DassaultSystemes/Licenses (Linux).

  2. Optionally, set the DSLS_AUTH_PATHNAME environment variable.

    You can also set the environment variable DSLS_AUTH_PATHNAME using a full pathname (UNC supported), if you decide to store the file in a different directory from the default one. For example:

    DSLS_AUTH_PATHNAME=G:\Shared\MyAuth.LIC

    If you do not set the DSLS_AUTH_PATHNAME variable, and there are several authentication files in the default location, only the most recent file (which supersedes the others) is taken into account.

  3. Retrieve the service connection hostnames from the e-mail you received and declare them in the DSLicSrv.txt file located in the above directory.

    The port number is 443.

    When a licensing client contacts the managed licensing service, it looks for an authentication file and sends it to the license server. The license server grants the license(s) and the session continues as normal.

  4. Check your network configuration (firewalls and proxies) to allow https access to the three hostnames on port 443.

    You can run the DSCheckLS command to check that your installation is correctly configured.

    You can then run the desired apps.

    Note: Working on a laptop with offline license keys is possible, assuming the laptop is not a virtual machine. The status of the license server appears in the DSLicMgt tool with a black bullet if a valid authentication file is not found.
    Note:

    A Windows service running as a generic account, such as Local System, cannot access the Internet and in particular cannot access the managed licensing service. So, by default, your Dassault Systèmes code running in a Windows service and which needs a license key provided by the Managed Licensing Service cannot work. A typical case is the 3DEXPERIENCE 3DSpace service hosted in a TomEE+ application server started as a Windows service.

    To solve this constraint:

    • either disable the Windows service and start the process manually, in a .bat file for example
    • or replace the Local System account used to start the service with a user account.