The "License Monitoring Details" page displays detailed information on the license allocation.
Only accesses relevant to licensing can be displayed via a separate checkbox.
Figure 43: CodeMeter WebAdmin – "License Monitoring | License Monitoring Details"
For example, in the figure above you see:
•the licenses for the application derive from the licensor with the Firm Code 600010 and describe the product with the Product Code 14.
•the licenses are stored in the CmContainer with the mask and serial number 3-3448482.
•in total 1 client, identified by ID, Client (::1(WIBU \ fs) and Client Process ID columns, 4 times accessed the application "Chart Processing" using Station Share. Here multiple instances can be started on a single PC but allocate only a single license. An access from another PC would be possible as the upper table (Total 2, Available 1) shows.
StationShare avoids unnecessary duplication of license allocation by ensuring that license accesses - locally or over a network - and the defined allocation sequence do not overlap.
For example, if a license access (handle) made via network (LAN) with StationShare will be detected, then no new license will be assigned locally despite the defined allocation sequence (first locally, then via network, i.e. LOCAL_LAN tag).
In addition, if a license is already accessed locally, no new license access (handle) will be made via the network, if the local access could also be made via StationShare.
•There is no expiration date.
•Client ::1(WIBU \ fs for the first time accessed the application (First and Last Access columns are of same date).
•Using the 
pictogram of the Action column allows you to remove single allocations..
|
You cannot deallocate and reallocate borrowed licenses before they have been returned. |
For example, this is necessary when all licenses are allocated but an additional instance of the application needs to be started.
|
After removing an allocation the license is deallocated and available again. The client of the application receives a respective error message. |
Access to cloud licenses from other systems
With CodeMeter version 8.40, this additional area is shown when CmCloudContainer licenses are accessed across networks from external CodeMeter License Servers using the same credentials (credential files).
This feature lets you detect and release these external license allocations. For example, if a license was reserved by another CodeMeter License Server using the same credentials on another system. This frees up allocated licenses so other users can use them again. Allocated licenses can be freed by clicking on the symbol 
.
|
Required are license allocations on the other system via CodeMeter Runtime version 8.40 or higher. When creating a CmCloudContainer in CmCloud Dashboard, administrators can use an additional control to specify whether license allocations on other systems should be shown. If this option is not activated, CodeMeter License Server will still display allocations within the same network. Allocations by individual users (clients) can then be specifically released. |
|
For example, employees start a licensed application (network-spanning on external system), but later leave the workstation without closing the software. As a result, the licenses used remains blocked. Administrators or other authorized persons can identify and release the allocation so that these licenses can be used again. |
Accesses to CmCloudContainer licenses from other systems are also listed via the CodeMeter API function CmGetInfo(CM_GEI_NETINFOCLUSTER) and the command line tool cmu -n.
