License Server

callas License Server introduces a dynamic way of licensing callas solutions. It allows pdfToolbox, pdfaPilot, and pdfChip to not be tied to a specific computer (real or virtual), but rather get permission to process jobs from License Server. This enables the use of callas solutions in Docker and auto-scaling environments and overall provides more flexibility than traditional computer-based activation.

License Server introduces a more dynamic way of licensing processing capacity based on peak performance. License Server-based licensing will allow callas products to run without being activated locally, rather checking with the License Server whether any licenses are available. This allows (virtual) machines to be brought online without having to go through the manual activation process.

The License Server makes models such as ‘load on demand’ or ‘capacity on demand’ possible. You either buy process cartridges and/or credit cartridges that are loaded in the License Server. One Process Cartridge enables you to run one callas process, processing one file at a time. Consequently, eight Process Cartridges will enable you to run 8 processes in parallel, no matter whether this is on one or more (virtual) machines. Process Cartridges would typically be used to run the daily production. To cater for peak production, the Credit Cartridges provide access to processing time, regardless of the number of parallel processes and/or (virtual) machines. For instance, a 50 000 Credit Cartridge handles 50 000 seconds of processing time. In an auto-scalable environment, this would allow for an unlimited number of server instances to be fired up, processing files until all credits are used, providing you access to unprecedented PDF processing power. For pure pay-per-use cases, you could of course choose to just use Credit Cartridges.

This type of licensing is initially compatible with pdfToolbox only. That’s why there are five licenses of pdfToolbox Desktop included with the purchase of License Server. This will be extended to other callas products later.

Auto-scalable solution
Cloud infrastructure
Possibility to load with Process Cartridges for daily production
Possibility to load with Credit Cartridges for unprecedented PDF processing power
Initially compatible with pdfToolbox only

Runs without being activated locally
The License Server will check whether or not any licenses are available. This allows (virtual) machines to be brought online without having to go through the manual activation process.
Caters with peak production
The License Server makes models such as ‘load on demand’ or ‘capacity on demand’ possible.
Pay-per-use environment
For pay-per-use cases, you can choose to use Credit Cartridges. They allow to be fired up for an unlimited number of server instances, processing files until all credits are used, providing you access to unprecedented PDF processing power.

License Server

Additionally, License Server supports processing capacity based on peak performance. Because License Server can use both process cartridges (that issue license based on a maximum number of parallel processes) and credit cartridges (that support processing time-based licensing), it is ideal for environments where processing peaks occur.

Avoid local activation

callas products such as pdfToolbox, pdfaPilot, of pdfChip, no longer have to be activated locally, if License Server is used. Instead, those products reach out to License Server and get the OK to process jobs from License Server.

This means that callas products can be hosted in a Docker environment, in a server-less environment such as Amazon Lambda, or in any auto-scaling platform where resources are created on-demand. The only requirement is that the products are capable of reaching License Server.

Flexibility in licensing

Because License Server uses two types of cartridges (processing modes), it can be used to respond to business needs in a more flexible way. Process cartridges provide a maximum number of parallel processes; this means that a set number of jobs can be processed in parallel. Credit cartridges contain an amount of processing time, and subtract the actual processing time needed for processed jobs (but they set no limits for the amount of parallel processing done).

In environments where required processing power is stable, process cartridges are the most economical solution. In environments where processing power is wildly unpredictable, credit cartridges may make the most sense. Both systems can be combined, to handle an average processing load in the most economical way, while using credits to cater for processing peaks.

Removing your single point of failure

Using traditional activation-based methods creates failure points, as licensing is tied to specific machines, and cannot be altered fully automatically (the activation process is manual). This potentially creates problems if machines go down.

License Server removes this single point of failure by allowing callas solutions to run on any machine, as long as that machine can communicate with License Server. In the cloud, License Server is hosted on a resilient Amazon AWS based platform to ensure uninterrupted availability. On-premise, License Server can be installed as a cluster that can handle problems with one of the machines in the cluster without interrupting service.

Floating desktop licenses

License Server offers an additional advantage for the callas desktop products (pdfToolbox Desktop and pdfaPilot Desktop). These products can also get their license from License Server. Desktop products ask for permission to run on startup, which removes the need to activate the product on each machine it’s running on.

This effectively means that the license becomes floating, and can be shared between a larger team. This increases flexibility and reduces the amount of licenses needed to make the desktop solutions available to the whole team.

In the cloud, or, on-premise

callas License Server is a cloud-based, SaaS solution. It is hosted by callas software in a secure Amazon AWS environment. When using the solution, you get a wallet that holds all of your callas product licenses. Communication to License Server is done using the ID of that wallet.

In certain cases, customers have a requirement to have a local, on-premise, version of callas License Server. This is also available (for an additional cost), and can run as a standalone solution, or as a synchronized License Server cluster. Keep in mind that local License Servers do need to be activated on the machine they run on, and as such can’t be installed in certain environments (such as on Docker machines).

Talk to our sales team about this product.

1.1.010

Fixes

Several smaller fixes and improvements for increased stability
Migrate/Restore: Improved handling
Issue solved, where activation in an Amazon Web Service environment was not successful
Improved formatting in the web monitor

1.1.013

Fixes

Problem solved, where migration failed with insufficient rights
Improved handling of the checksum in the blockchain [FP70557]
Issue solved, where uninstalling an expired cartridge failed [CA1032141, FP71051, FP71879]

1.2.021

Features

Support for Cartridge pools (requires pdfToolbox 14.3) [FP71980]
Support for developer licenses (requires pdfToolbox 14.3)
Improved handling of process and credits cartridges in failover setups
Enhanced log files with more detailed information about connection problems in failover setups
New log files with details of Cartridge uninstallations and License Server deactivations

Fixes

Problem solved, where the coordinator instance of the License Server could consume an increasing amount of memory [FP71902]
Issue fixed, where activation of a Cartridge for a newer product version but with the same serial number failed [FP66831]
Problem solved, where changing the time zone of a License Server resulted in invalidated Cartridges [FP65485]
Issue fixed, where the License Server could consume process licenses from different cartridges when cartridges for different major versions were installed
Issue fixed, where the deactivation of expired licenses was not successful
Problem solved, where expired cartridges could not be updated

1.2.022

Fixes

Problem solved, where migration failed in the --restore step when the /tmp folder resided on a different hard disk partition
Issue fixed, where the log file (log.json) became invalid in certain cases when the LicenseServer was stopped [FP76941]
Problem solved, where a penade License Server configuration could become unstable [FP76642]
Issue fixed, where updated IP addresses were not displayed correctly in the REST interface

1.2.023 Fixes

Problem solved, where license deactivation was not successful in certain cases (Linux only) [FP79935]
Problem solved, where long-running failover systems could allocate unnecessary amounts of memory in some cases [FP78650]