Upcoming Events
   
 


DSLS VS LUM?

As you might be aware, Dassault Systèmes recently introduced DSLS (Dassault Systèmes License Server). As a matter of fact, DSLS has been introduced in V5R21 as the default licensing middleware for V5 products and is required for V6 products. This is a change to the actual IBM product LUM V4 (License Use Runtime) license management software you might be actually using right now with your current CATIA or ENOVIA DMU or even ENOVIA Smarteam installation.

This article might be very useful to you in case you are in charge of managing licenses for your company because the use of LUM V4 license management software and keys will be discontinued in a future releases.  We therefore want to give you the right information so you can take the appropriate actions.

If this article still doesn’t answer your questions, please don’t hesitate to contact your Inceptra representative and we’ll be happy to help you.

First of all, DSLS is a prerequisite for all new customers starting V5R21. For customers already working with previous V5 versions, IBM LUM 4 license server will be able to serve V5-6R2012 processes but will be out of support on December 31, 2013.  Customer is then allowed to choose either to use LUM server and then switch to DSLS server, or to immediately switch to DSLS server while deploying V5-6R2012 (recommended). If for some reason you still need to use LUM on V5R21 or V5-6R2012, you need to add the following environnement variable in the environment file in order to activate old LUM licensing mode because DSLS will be used by default:

DSLICENSING=LEGACY

Important to note, DSLS license keys are not compatible with IBM LUM license keys: new licenses should be obtained in order to run with DSLS. When requesting new license keys or renewing previous licenses, customers will have to indicate if DSLS OR LUM license keys have to be generated. The total number of keys (DSLS+LUM) cannot be greater than the entitled key number.

This new prerequisite applies to all V5-6R2012 products from:

  • CATIA V5,
  • ENOVIA DMU V5,
  • ENOVIA VPM V5
  • ENOVIA 3d Com
  • ENOVIA SmarTeam
  • DELMIA V5
  • CAA Rade
  • Companion


DSLS features

DSLS supports nodelock licenses and licenses enrolled on a server.

DSLS can be configured as a standalone license server or a failover cluster composed of three license servers (similar to LUM HAL).

DSLS supports concurrent offline licensing. Extracting a license from a standalone or a failover server to a laptop is supported.

DSLS follows standard communication protocols (https). This allows an easy integration in Customer network architecture.

DSLS can be installed on Windows, Linux, AIX and Solaris Sparc.

DSLS administration tool provides both graphical and command-line interfaces.

All DSLS features are fully described in DSLS documentation. Please refer to it for obtaining all necessary details related to installation and administration of DSLS.


DSLS compatibility

DSLS is already used by Dassault Systemes V6 products.
The same DSLS process can host V5 and V6 license keys and can grant simultaneously such licenses to V5 and V6 processes.
Minimum DSLS version able to serve V5-6R2012 products is DSLS V6R2012x (6.212.0 - September 8, 2011).
This DSLS version is also able to serve V5R21 products.


Frequently asked questions:

  1. I am a new V5 customer. Can I get LUM keys?
    If you are a new V5 customer we strongly recommend getting DSLS keys from the beginning. This will avoid unnecessary migrations in the future.

  2. If I order LUM keys and later am ready to switch to DSLS, can I get DSLS replacement keys?
    Yes, when the DSLS keys are received, the LUM keys must be destroyed

  3. If I start to use DSLS and need to go back to LUM, can I?
    The intent is for the conversion to be a one-time process. Once you have received a DSLS key for V5, you may not replace it with a LUM key, except in emergency situations

  4. What is the reason for this change?
    License key management has been and will continue to be an area of rapid innovation and change. Switching from a third-party license manager—IBM LUM--to for V6 gave us the flexibility to exploit improved software technology, to adapt in the future to continual changes in the technical environment such as Cloud computing, and to add new license management features. With IBM’s historic role in sales and marketing of Dassault Systèmes products transitioning to Dassault Systèmes, starting in 2010, it made even more sense for Dassault Systèmes to become independent in this area.

    Making the change for V5 as well as V6 not only brings these improvements to the V5 world; it also allows customers to consolidate resources by using the same license management software for both product sets.

  5. Do I need to switch to keys?
    For V5R21 and V5-6R2012 you have the option to continue to use LUM V4 for all your products, switch all products to, or to use a mixture of both key types.

    Dassault Systèmes strongly encourages customers to at least begin the transition to DSLS as soon as possible. V5-6R2012 is one of the last releases planned to support LUM keys.

    Note: LUM V4 goes to end of support on Dec 31, 2013.

  6. Does DSLS work on Virtual Machines?
    Virtual machines, such as VMWare, are not supported. It is not possible to either run or install the Dassault Systemes License Server on a virtual machine.


    Questions about comparison of DSLS to LUM

  7. We use LUM dynamic shareable licenses, which allow the user to check out or check in a shareable license in the middle of a session. Will DSLS offer this capability?
    Yes.
  8. Can I run DSLS over a WAN?
    Yes, if contractual conditions are satisfied.

  9. Can I run DSLS server and LUM server on the same host?
    Yes, if Operating System prerequisites are satisfied.

  10. I understand that DSLS keys for V6 are release-dependent. What about for V5?
    DSLS keys for V5R21 or V5-R2012 are release-dependent. The key contains a field called “MaxReleaseNumber” that is set to 1 (the number that corresponds to the current release) plus any buffer that Dassault Systèmes may assign. Future releases will be assigned sequentially higher values of MaxReleaseNumber. The key will not work for any higher release than the one corresponding to value of the MaxReleaseNumber parameter. To move in the future to a higher release, you will need to order release upgrade keys.

    For V5R21, Release=1; for V5-6R2012, Release = 2

  11. For V6, some DSLS keys are generated with a release “buffer”—keys issued for release x will work up to x + y because inside the key, MaxReleaseNumber=x + y. What about DSLS keys for V5?
    In some cases, a buffer may be added, depending on the terms of the license.

  12. For V6, the keys for products with Named User licenses behave as Named User keys. For example, they are locked to a given named user. What about DSLS keys for V5R21 or V5-6R2012?
    Named User keys are not used for V5R21 or V5-6R2012, since V5 products are not offered with Named User terms and conditions.

  13. LUM V4 had Nodelock, Concurrent, Offline Concurrent, and High Availability keys. What key styles are supported by DSLS?
    DSLS supports these types: Nodelock, Floating (ie, concurrent), and Failover (similar to LUM High Availability). Offline Concurrent function is still supported.


    Where to find it?

  14. Where can I find detailed documentation on DSLS?
    Additional information can be found in the V5 Program Directory.

  15. Where can I get LUM 4.6.8 FP 13, 14 or 15?
    LUM code does not ship with V5 media. It can be downloaded from the Dassault Systèmes Support website at http://www.3ds.com/support/resource-library

    Or directly from our FTP: ftp://ftp.inceptra.com/PLMDownloads/LUM/

  16. Where can I get DSLS code?
    DSLS will ship with the media for V5R21 or later releases or it can also be found on our ftp site:
    ftp://ftp.inceptra.com/PLMDownloads/DSLS/


    Policy questions

  17. How are the quantities of keys managed if I have a mixture of both LUM and DSLS keys?
    The total of LUM plus DSLS keys for a given product cannot exceed the total entitlement. For example, one product could have 34 licenses. If you keep 10 of these at V5R20 and 14 go to V5R21, then you will have 10 LUM keys for R20, and for V5R21, you could have 4 LUM keys and 10 DSLS keys.

  18. I am a new V5 customer. Can I get LUM keys?
    If you are a new V5 customer we strongly recommend getting DSLS keys from the beginning. This will avoid unnecessary migrations in the future.

  19. If I have unexpired LUM keys for my pre-V5R21 products, can I replace them with DSLS keys when I upgrade to V5R21 or V5-6R2012?
    Yes


    System configuration questions

  20. How do I configure the end user machine to select LUM or DSLS?
    If you are using V5R21 or V5-6R2012 and want to use LUM instead of DSLS, there is a CATIA environmental variable “DSLICENSING”. If it is assigned the value “LEGACY” then the session will use only LUM keys. If it is not set, then the session will use DSLS keys.

    By default it is not set. That is, DSLS is the default.

  21. Can I use LUM keys and DSLS keys for interactive, batch, or a mixture of the two, on the same end user machine at the same time?
    An interactive V5 session has a V5 environment, and so it can only have one value for the CATIA environmental variable controlling the key software selection (LUM or DSLS). So every configuration, Add-on, or shareable running in this session, and any batch job started from this session, must use the same kind of key—all LUM, or all DSLS.

    If two separate V5 environments are running at the same time, they can each have their own value of the CATIA environmental variable. So, one could be using LUM and one using DSLS.
    For example,
       • Two separate CATIA interactive sessions, each running in its own environment on the same machine
       • An Interactive CATIA session and a batch job, each running in a different environment on the same machine
       • Two batch jobs, each running in a different environment on the same machine

  22. I currently have LUM configured on my users’ machines to search a sequence of LUM servers, for performance and reliability reasons. Can I do this with DSLS?
    Yes.

  23. I have a DSLS server for V6 products which I would like to use to serve DSLS keys for V5 products. Can I enroll both sets of keys on a DSLS server?
    DSLS can enroll and serve license keys for both V5 and V6 products.


    Planning questions

  24. What are officially supported releases of IBM LUM Runtime (LUM server and utilities) supported for V5?
    V5R21 and V5-6R2012 both require LUM 4.6.8 FP 13 or 15.

  25. What is the officially supported releases of DSLS for V5R21 and V5-6R2012?
    V5R21 requires DSLS V6R2012 or higher. V5-6R2012 requires DSLS V6R2012x or higher.

  26. What release of DSLS ships with V5?
    V5R21 ships with DSLS V6R2012. V5-6R2012 ships with DSLS V6R2012x.

  27. We need to plan for any changes to our procedures and scripts that are needed. Are there any LUM functions that are not available in DSLS that we need to be aware of?
    We believe that DSLS offers equivalent functions to all of the LUM capabilities that were utilized by V5.

  28. How to retrieve my Target ID for DSLS?
    To generate your DSLS Target ID, please follow the steps below:

Article compiled courtesy of Sebastien Gaetan
Creative Application Engineer with Inceptra, LLC.

 
   
 
Contact Us