Using the License Server on-premise

In order to avoid having to activate a callas software product, you can use a reference to a running License Server in the call to that product. The License Server on-premise needs to be activated, it needs to be running and it needs to have valid cartridges installed.

The --licenseserver command points the callas software product to the License Server on-premise so it can get permission to run your call.

./pdfToolbox --licenseserver=<ip or hostname of licenseserver> <other command-line parameters>
Click to copy

The command specifies the IP address of the License Server you want to use. Please note that all callas products also support DNS names for the --licenseserver option. Optionally, this can be followed with a colon and a port number. If you use the default License Server port (1400), the port doesn't have to be specified.

Support for 'configuration file' with defined IPs

There is a way to change all usages of our configurators if new or extra IPs are to be defined. It is possible using a 'global' configuration file.

This can be done by storing a "LicenserServer.txt" that contains IPs (and ports) at the same place where a "License.txt" would usually be searched. The system path for different Operating Systems are mentioned here.

Please note:

The formatting of this "LicenserServer.txt" should be a single LicenseServer per line, like:<valid port if required>
Click to copy

Important to note:

  • If a LicenseServer.txt exists, a --licenseserver command is not necessary. If --licenseserver is defined nonetheless, these IPs will be tried first
  • Needless to say that in order to initialise and use the LicenseServer, at least one --licenseserver option OR LicenseServer.txt is needed

Using a developer cartridge

Cartridges can be obtained for production or development purposes (e.g. for internal testing). For development purposes you have to request a license from a DEV cartridge with the --lsdev command in addition to the --licenseserver command.

./pdfToolbox --licenseserver=<ip or hostname of licenseserver> <other command-line parameters> --lsdev
Click to copy

Set a cartridge pool

Cartridge pools allow assigning some of the licenses available on the License Server for specific tasks. To request a license for any number of pools you have to specifying the cartridge pool on the command line by using the --lspool parameter.

./pdfToolbox --licenseserver=<ip or hostname of licenseserver> <other command-line parameters> --lspool=<POOLNAME>
Click to copy

Using the License Server with Desktop products

Once the License Server is activated and running with a valid cartridge for pdfToolbox/pdfaPilot Desktop installed, you can run your Desktop and Server products without activating a hardware bound license to it. Simply go to callas pdfToolbox > About callas pdfToolbox

Once a new window pops up, you can click on the checkbox 'Use License Server'.

Then click on the 'License Server settings' edit button in order to define your IP to use License Server via the desktop product. Here you have several options:

  1. To use the License Server on-premise to activate pdfToolbox Desktop, you must enter the IP address of the server here. More information on how to activate the License Server on-premise can be found here.
  2. Input field to specifying a cartridge pool. More information can be found here.
  3. To use the License Server (SaaS solution) to activate pdfToolbox Desktop, you must enter the Wallet ID here. More information on how to use the License Server can be found here.

License server details in 'LicenseServer.json'

A "licenseserver.json" can alternatively be placed manually in User-Preferences OR AllUser-Preferences OR Program-folder, which defines if a license server is available over UDP or IP (in case of the latter, over which IPs it is available). The format of 'LicenseServer.json' is as follows:

    "use": true,
    "udp": false,
    "fixed": true,
    "url": ["", "xx.x.x.xx", ...]
Click to copy

While looking for pdfToolbox, it checks for License.txt but if a LicenseServer.json exists, the keys are searched there while overwriting  the original application settings.

Using the License Server with pdfToolbox/pdfaPilot Server/CLI

  • Start the server via the CLI with: pdftoolbox --server --licenseserver='URL'
/Applications/callas pdfToolbox Server 13/cli/pdfToolbox --server --licenseserver=""
Click to copy

This would open the status window:

  • With "Connect with remote server" or "Start a server" the jobs should be visible and can be started.