WinCC OA Licensing, Further Information
WinCC OA Licensing - Selection of a License Container
The WinCC OA licensing uses CodeMeter containers. There can be several containers in one system. If a specific container must be used, the container can be specified with the config entry useCMContainerSerialNumber.
If no specific container is specified, the first container that contains an Event Manager license is used.
The container number used is displayed in license log messages. If a container does not exist, an error message is displayed for the non-existing container (see chapter Licensing Errors).
If no specific container is defined, the search for a valid container is performed in the following order:
- Local software container
- Hardware dongle
- License server
If a license server is found, the first container containing an Event Manager license is selected randomly.
Change Licence Container at Runtime
The WinCC OA license container can be changed at runtime by writing the container ID of the new license container into the data point element "_Event.License.setCMContainer". An automatic search for a new license container is not possible.
The changeover to the new license container is initiated immediately. It may take a few minutes in case of a network license (license server) and runs parallel to other WinCC OA Event Manager tasks. During the changeover of the license container all operations requiring a license check are blocked, which is indicated by the log message "… blocked due to service operation running".
A license from the original license container remains occupied should a licensed WinCC OA feature be stopped during the change of the license container.
The status of the change of the container is indicated on the DP element _Event.License.setCMContainerStatus, see chapter _Event.
License Validity Check
After the start with a valid license WinCC OA Licensing checks the validity of a license every 10 minutes or on update of the data point element _Event.ReadLicense.
License errors and failure scenarios
If a license error occurs, you can find the log messages in the PVSS_II.log file. An explanation of the log messages can be found in chapter Licensing Errors.
- Hardware dongle or software container was removed
- Software container was emptied
- Disconnection of the network connection to the license server or a defective network connection.
|
Runtime Exception handling |
Restart Exception handling |
|
|---|---|---|
| A license error occurs |
A warning message is displayed at 10-minute intervals (check interval). The message is "Invalid license, <number> minutes left." After the check interval has been repeated three times (30 minutes), the project switches to "7-day license mode". An alarm is triggered via the data point element "_Event.License.cmLicenseInvalid". When switching to the secured mode, UI managers in configuration mode (PARA, GEDI) are terminated. After the "7-day license mode" expires, the project is shut down completely. |
If no valid license is found, the project starts in demo mode. |
| A license error is fixed | At the next check (< 10 minutes), the message "License recovery was successful" is displayed and the system is fully functional with a valid license. | Project starts in normal mode. |
| Event license has expired
(expiration date exceeded) |
The project switches to the "7-day license mode". When the license has been updated, the project switches to normal mode. |
There is no valid WinCC OA license (Event license has expired). The project starts in demo mode. |
| Component license has expired (expiration date exceeded) or is withdrawn (Rehost) | The component continues to run (e.g. S7/S7+ driver). However, if it is terminated, it cannot be restarted. | The project starts in normal mode. The expired component cannot be used. |
| Demo mode: Licenses cannot be restored and a restart of the project is required. | ||
Debug Flag -report license
The debug flag -report license can be used for all managers. It outputs the current license options available for a manager.
