Ortems HowTo Technical 

This solution is dedicated to customers/partners:

• not having any physical server to host their DS license.
• not having any Hyper-V virtual machines or not respecting the constraints to use them as host for their DS license.
• who want to reduce costs and time to manage their own servers 
• who want to benefit of DS highly available license servers

In such a case, Hosted DSLS (= Managed DSLS = Managed Licensing Service) is the solution.

Prerequisites:

• As explained in our install_config_mp_ps_2023_us.pdf documentation (available in \\help\\documentation\\ folder), to use Dassault Systèmes’ license system (DSLS), the Microsoft Visual C++ 2015 Update 3 Redistributable package (32- or 64-bit version, as applicable) must be present on all the server and client computers that are going to run the DELMIA Ortems applications. If you need to install it, you can find the setup files in the Tools folder provided with the DELMIA Ortems installation package.
• This DS licensing mode is compatible for Ortems since release 2020.
• Hosted DSLS is a free service provided to our customers under software support.
• On user side, must be respected some eligibility criteria.

To check them, DS offers Managed DSLS Eligibility Checker tool (available for download here).

That tool is supposed to be launched only from computers running Ortems processes, whatever they are user computers or computers running Interface loop with Ortems (for example in context of Citrix usage, only the Citrix server runs the processes, therefore our Eligibility checker tool requires to be launched only from that computer).

Example of returned result window:

In case of issue

A red flag is displayed on one or several checking), you can refer to this post focusing Eligibility Checker tool

The following step-by-step process to retrieve and install a Hosted DSLS license key file for DELMIA Ortems is described below

Managed DSLS enablement process with SIR (Site Modification Request)

Managed DSLS requires having an OML product (Online Licensing Service) in the customer’s Installed Base. The customer’s DS Sales Operations Distributor is the actor to contact to initiate the process to add this OML product. She/He will request some information to the customer in order the launch the process.

LKO creation to request the keys

Once OML product has been added, contact the usual license provider (depending on the situation, it may be the customer’s partner, the partner’s PSM, or DS).

Please note that the DELMIA Ortems Support Team cannot generate any LKO nor provide license keys directly without an LKO.

In the LKO request, it is mandatory to specify:

• Lic. Model - Gen. Type = DSLS – DSLSV5EXT (instead of Specific)
• Type = Managed DSLS
• Note that there is no Target-ID to specify (the filed has disappeared by selecting Type="Managed DSLS")
• Online instance is supposed to be prefilled. If it remains empty, click on the magnifier icon to select the appropriate online instance.

Reminder about product trigrams:

Please note that a new product must be present for Managed DSLS: OML trigram product (Online Managed License). This free-of-charge commercial product is mandatory because it will create an authentication file (.LIC file) and send it to the requester: deployed automatically by DS at DS. It then must be deployed at the customer to be identified as a regular user of Managed DSLS, according to the next chapter. This product is special because never expires (not to request again).

More information about Managed DSLS: https://www.3ds.com/support/documentation/resource-library/single/dassault-systemes-license-server-and-license-keys/

Installation of the license key file

Concerning the installation, the very good news is that there is no software to install on customer’s side!

Every software required installation was performed at DS automatically. A message is sent to the requester to inform her/him that the license is created and installed on DS server. 1 file is attached to the message. The message also explains how to create DSLicSrv.txt file that will be used later in this process.

However, the customer has to perform one of the 2 following actions:

1st alternative:

For each licensing client, copy the .LIC file (=authentication file) in the following default location:

 %ProgramData%\\DassaultSystemes\\Licenses\\

2nd alternative:

On only one computer: copy the .LIC file (=authentication file) to a unique location to which all the licensing clients have access

+

For each licensing client, set the DSLS_AUTH_PATHNAME environment variable with the pathname to the .LIC file. It is possible to use a full pathname (UNC supported).

For example: DSLS_AUTH_PATHNAME=G:\\Shared\\MyAuth.LIC

Configuration of DELMIA Ortems to switch on DSLS license keys

• Open the DELMIA Ortems “Environment management” module
• Navigate to Administration > Advanced settings
• Set the “Licensing mode” choice to 3DS Licensing 

​​​​​​​At this step, the interesting file is DSLicSrv.txt (reminder: this is the file created by you as explained in the message). Edit it with Notepad.exe, copy its content and paste it to “Address” field.

Click on the test license server button to check the installation:

Check that it is possible to connect to DELMIA Ortems

Now the process is completed, it should be able to launch each DELMIA Ortems module such as Data Module, WIP Control, Planning, etc.

How to know the details of the customer's license keys hosted on DS servers?

In the message sent to the customer, a link is provided to perform some "Advanced Administration Tasks" . 

This Administrative URL is for connecting directly to the license service Administration web user interface.

Note: for security reasons, the URL provided for web administration needs a first connection to Dassault Systèmes' servers through a 3DPassport login.

​​​​​​​

Via Admin tool, Customer Administrator can:

• Add authorization rules (User, TCPIP range)
• Configure license expiration alerts
• Get currently in-use license information
• Change passwords
• Consult logs stored on the license server

But Customer Administrator cannot:

• Start / Stop the license server
• Change the license server configuration
• Enroll and delete license keys
• Stop usage tracing
• Enable Statistics
• Access monitoring data