Anonymization management queue
The anonymization management queue allows you to update the anonymization configuration or the software license at runtime, without stopping the anonymization process. The data published to the anonymization management queue is broadcast to TaskManagers according to the Apache Flink JobManager and TaskManager configuration. The configuration and license data are updated in-memory.
Configuration
The anonymization management queue is configured and enabled through the optional MANAGEMENT_URI environment variable. In this variable, define the URI of the queue where you publish updated anonymization configuration or software license.
If you don't set this environment variable, the anonymization management queue is disabled.
Note
To learn more about the available configuration options and configuration examples, see Configuration of HERE Anonymizer Self-Hosted.
Message type auto-detection
The anonymization management queue automatically detects the pushed content type (configuration/license update) and logs appropriate messages to indicate whether the content parsing is successful or failed.
| Subject | Status | Message |
|---|---|---|
| Configuration | Success | INFO: Detected Source Message value IS Anonymization Config and parsed successfully. |
| Configuration | Failure | INFO: Detected Source Message value IS NOT Anonymization Config and cannot be parsed. |
| License | Success | INFO: Detected Source Message value IS Anonymization License and parsed successfully. |
| License | Failure | INFO: Detected Source Message value IS NOT Anonymization License and cannot be parsed. |
Update distribution
Configuration
To update the anonymization configuration, you must publish a complete configuration. Partial configuration or individual values published to the queue are treated as invalid data.
After publishing a message to the queue, the data is validated. Upon successful validation, the configuration is updated in-memory. If the validation fails, the configuration isn't updated.
License
After publishing a message that contains a license to the queue, the data is validated. Upon successful validation, the license is updated in-memory. If the validation fails, the license isn't updated and the current license is used until it expires.
The system logs the following messages when attempting license updates:
| Status | Message |
|---|---|
| Success | INFO: New License Installed Successfully. |
| Failure | WARN: New License Installation failed with license validation exception - Your license has expired and hence, the anonymization process has been stopped. |
| Failure | INFO: Current License will keep working till Expiry. |
Updated 26 days ago