- GetInstanceID - returns instance/device ID which is created at startup
- WriteLicenseUsageData - writes encrypted license usage (same as system data table) to ThingworxStorage\reports\LicenseUsageReport folder
The license file is now bound to the platform Instance ID aka Device ID - (unlike most other PTC products where the license is bound to the hardware : CPUID, MAC, ...)
This Instance ID is generated during first startup and stored in the database
Instance ID is accessible in composer with LicensingSubsystem::GetInstanceID
Q: What happens when license files are bad or missing?
A: If there is an invalid license file, with 8.0 valid license.bin needs to be in the folder before starting up; tomcat will crash. In 8.1 no need for license file as long as connected (platform-settings.json), no need to take an extra step, dynamic connection. In disconnected scenario, ThingWorx will run for 30 days in limited mode with monitoring mashup accessible to check logs.
Q: Where is the InstanceID stored ?
A: It's stored in the database
Q: Will the instanceID change during updates (minor 8.1.0 to 8.1.1)
A: Device id's don't change.
Q: What will happen in disconnected scenario if there is no valid license after 30 days? The application will not start anymore or user is not able to login?
A: It shuts down, so there is no more "limited" mode. However, a user can come along on day 55 (for example) and can drop in a valid license and start the web app to get it fully running.
Q: What happens if the customer has to reinstall the platform after the license has been fetched ? Is it possible to "return" the license ?
A: Reinstalling the platform results in the generation of a new Device ID, therefore a new license file will need to be generated.