Skip to main content
C
Constantine18-Opal
18-Opal
September 1, 2019
Solved

Docker and ThingWorx license

  • September 1, 2019
  • 2 replies
  • 3421 views

Hello,

 

Running ThingWorx in Docker generates different device IDs every time container is restarted. We need to restart those containers frequently and automatically (several times per day). We have one ThingWorx license available, and even though we generate multiple device IDs, there is maximum one server running at a time. Is there a way to license it?

 

Regards,

Constantine

    Best answer by raluca_edu

    No, it will not consume license, basically will be same license , but for different device id each time the device id is changed (this was confirmed by someone from Licensing team).

    2 replies

    R
    raluca_edu17-Peridot
    17-Peridot
    September 2, 2019

    Hi,

     

    In this case, what will work is to use the online licensing by updating LS_USERNAME and LS_PASSWORD with the PTC account in yml file of Docker image, to get every time a new license based on the device ID.

     

    Best regards,

    Raluca Edu

    C
    Constantine18-OpalAuthor
    18-Opal
    September 2, 2019

    Thanks @raluca_edu, won't it consume a new license every time a container is restarted? We have only one license and one container.

    R
    raluca_edu17-PeridotAnswer
    17-Peridot
    September 3, 2019

    No, it will not consume license, basically will be same license , but for different device id each time the device id is changed (this was confirmed by someone from Licensing team).

      S
      smainente16-Pearl
      16-Pearl
      September 3, 2019

      Hi Constantine,

      Are you using "named" volumes for the ThingworxStorage and ThingworxPlatform folders ?
      What command are you using to "restart" the container ? Restarting the container should not change its device ID.

      Thanks.

      C
      Constantine18-OpalAuthor
      18-Opal
      September 3, 2019

      @smainente Sorry for causing confusion, here I use "restart" term loosely -- in fact our main use case are canary and red/black deployments in immutable infrastructure, so those containers are frequently destroyed. We also use volumeless containers in our CI pipeline, which triggers at least few times a day.

      S
      smainente16-Pearl
      16-Pearl
      September 3, 2019

      Thanks for the clarification Constantine.

      If you are not reusing the volumes, then I confirm that a new Device ID with be generated every time you spawn the container.

       
       
        Terms & ConditionsCookie settingsAccessibility statement