White Paper
The CodeMeter Runtime Service also acts as license server in the network. The user only installs the CodeMeter
Runtime Service on a server in the network, configured as the license server for that network. The software then
communicates with a local installation of the CodeMeter Runtime Service, which in turn communicates with the
network server’s CodeMeter Runtime Service that manages and allocates the available licenses.
Let Us Count That for You: License Quantity
Every license in the CodeMeter universe has a stated license quantity, defined by the software vendor when the
license is created. The standard quantity is one.
When you integrate CodeMeter, you determine the manner of counting in your software. You can choose between
“per access”, “per machine,” and “no count.” All licenses, whether on a CmDongle, a local CmActLicense, or a
license server, are treated completely alike.
Per access - UserLimit
Using the “per access” count, one license is flagged as used for each access (API command CmAccess2) to be
released once the access ends (API command CmRelease). Each license can only be used for the number of times
allowed by the license quantity value.
Per machine - StationShare
Using the “per machine” count, CodeMeter automatically records certain details about the software environment
(session, IP address, process ID…) and transmits them to the CodeM