Page History

...

• Depending on the product and component in use you might receive multiple license keys from SOS at different points in time.
• In such a case please add newly received license keys to the list of existing keys like this:
  
  [licence]
key1=SOS-DEMO-1-L54-4-7-22-???????
key2=SOS-DEMO-1-L54-4-7-23-???????
  
  Each license key is added to a separate line with the key1, key2, key3, ... configuration items. 

Use of limited License Keys

• Users who want to switch back from e.g. a trial license key or a subscription license key that is valid for a limited period to use of the Open Source license can proceed as follows:
  • Add both keys to the ./config/sos.ini configuration file like this:
    
    [licence]
key1=SOS-CUSTOMER-1-QCT-4-7-20170130-22-23-CG7R6I2
key2=SOS-DEMO-1-L54-4-7-22-T7I4FYA
     
  • The capabilities of both keys (key1 being a sample for a trial license key and key2 a sample for the Open Source license key) are merged. In case that key1 becomes invalid then key2 will allow to fall back to Open Source restricted mode for the use of Agents.
  • Should exclusively key1 be available and become invalid then the JobScheduler Master will not start due to an invalid license key.

Handling of License Keys for JobScheduler Agents

• JobScheduler Agents come with zero configuration, therefore no license keys are stored with the installation of an Agent.
• Licenses License keys for Agents are stored with the JobScheduler Master. The available license keys are handed over by the Master to the Agent before job execution. The Agent then checks if the license key is valid and applicable for the respective job.
• An Agent might refuse job execution if it is not forwarded an applicable license key.

...