JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 26

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A license check is performed if a Cluster cluster of JOC Cockpit instances, Controller instances or Agent instances is operated.

...

  • JOC Cockpit:
    • The positive license check indicates that a valid license is available, therefore this check works silently without further logging.
    • The GUI offers the information about the license in use when clicking the JS7 logo:

      Image Added

  • Controller:
    • The positive license check will log a single entry in the controller.log file on start-up of the Controller. The entry looks like this:
      • 2021-05-28T06:14:33,196 info com.sos.js7.license.controller.ClusterLicenseCheck - Product Name: js7.controller.cluster
      • Consider that the controller.log file is rotated and that the information is available from Controller start-up.
    • The license check will log two lines to the watchdog.log file on start-up of the Controller. The entries look like this:
      • Product Name: js7.controller.cluster
      • using Commercial License. Expiration Date: 2026-05-04 12:22:41
  • Director Agent:
    • The positive license check will log a single entry in the agent.log file on start-up of the Agent. The entry looks like this:
      • 2023-08-21T05:12:54,389 info com.sos.js7.license.agent.ClusterLicenseCheck - Product Name: js7.agent.cluster
      • Consider that the agent.log file is rotated and that the information is available from Agent start-up.
    • The license check will log two lines to the watchdog.log file on start-up of the Agent. The entries look like this:
      • Product Name: js7.controller.cluster
      • using Commercial License. Expiration Date: 2026-05-04 12:22:41

...

  • License keys do not implement technical license counting. SOS estimates there to be a risk that license counting could fail when used in restricted environments and could prevent the software from running.
  • You can technically use the same license key for any number of JobScheduler instances. However, this might not comply with the commercial license terms that are agreed on for the license model that is applicable to your environment. 

...