Book a Demo

Author Topic: Floating licenses on Pro Cloud  (Read 3012 times)

DavidM

  • EA User
  • **
  • Posts: 82
  • Karma: +0/-0
    • View Profile
Floating licenses on Pro Cloud
« on: November 17, 2022, 02:45:23 am »
Hi Everyone,
This is a request on behalf of a colleague.
Does anyone have any simple instructions on how to set up Floating licenses on cloud, for an on-premise installation?
I am unable to advise and was wondering if anyone here had.
He has been though the numerous documentation and links provided by Sparx support, but seems to have still trouble configuring the Por cloud client for cloud based keys.

I think it is the actual key store server name based in Pro cloud that he is looking for,  in the Link part of the Sparx key store configuration client

THanks
« Last Edit: November 17, 2022, 02:56:46 am by DavidM »

Sunshine

  • EA Practitioner
  • ***
  • Posts: 1340
  • Karma: +121/-10
  • Its the results that count
    • View Profile
Happy to help
:)

DavidM

  • EA User
  • **
  • Posts: 82
  • Karma: +0/-0
    • View Profile
Re: Floating licenses on Pro Cloud
« Reply #2 on: November 17, 2022, 07:37:28 pm »
Thank you for the reply. Yes, he has been through these guidelines, what the issue is, is  he has installed the Pro cloud and the Floating key client, but doesn't know the url for the
Floating key repository stored in the cloud, he's tried contacting Sparx, but they just sent him the guidelines again. but I couldn't figure it out either.

So it is the details you put in the Link (I think) to the Sparx floating key configuration client to link it to the Pro cloud keystore that is the important information he cannot find. He contacted Sparx support, but he said they sent him the guidelines again first time, second time they didn't respond.

« Last Edit: November 17, 2022, 08:44:35 pm by DavidM »

BobM

  • EA User
  • **
  • Posts: 144
  • Karma: +9/-0
    • View Profile
Re: Floating licenses on Pro Cloud
« Reply #3 on: November 18, 2022, 08:38:41 pm »
Hi David,

the licence server is the server DNS where the keystore application is installed
example for the DNS: lic-srv-ea.DavidMGroup

  • Start -> help -> register and manage your licence keys
  • Add key
  • Get shared key -> …  (dots next to Shared Keystore)
  • Sparks keystore server -> fill in licentie server DNS -> OK
    Protocol should stay on ssks://
  • Select your licence edition (eg. EA corporate edition) -> Ok

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1163
  • Karma: +30/-8
    • View Profile
Re: Floating licenses on Pro Cloud
« Reply #4 on: November 18, 2022, 09:28:48 pm »
If he is using the PCS floating license server, it may be better to use https as the protocol.

The URL of the floating license server is either the IP address or DNS of the server hosting PCS. A couple of comments based on recent experience with PCS v5.

If the floating license client is installed on the same server as PCS, it may not be able to connect to floating license server using the DNS. We found that the floating license client could only connect to the floating license server using the DNS, if the client was installed on a separate machine. This was reported as a bug.

If running the floating license client from a different machine, you also may need to whitelist the IP address of these machine. PCS v5.0 has a bug, that I think was corrected in a previous version and reappeared, effectively stopping PCS from running with an empty whitelist. Each time the configuration client is run it repopulates the whitelist with default values.

DavidM

  • EA User
  • **
  • Posts: 82
  • Karma: +0/-0
    • View Profile
Re: Floating licenses on Pro Cloud
« Reply #5 on: November 18, 2022, 10:34:43 pm »
Hi Everyone,
Thanks for that really useful information, I have passed it on!!
Many thanks

christofn

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Floating licenses on Pro Cloud
« Reply #6 on: December 22, 2022, 06:19:56 pm »
I have PCS v5.1 running. I also was unable to connect the license client to the license server (both running on the same VM). By disabling IPv6 and whitelisting the server in the admin client whitelist of PCM, it seems to work. I now use both floating license client and server on the same virtual machine.