Figure 9: Programming by Update File
In order to ease the reprogramming process, the developer has the ability to generate the next context file, and
store it as a modified context file on an Internet server. The generation of and sending of the next context file is
triggered by the end-user. The developer’s server then sends the update files only. This is feasible, because only
the status of their own FIRM ITEM is relevant for programming the developer’s own license entries, i.e. the
counter in the FIRM ITEM. In the case where the CmStick is, in the meantime, re-programmed by another
developer, the update files, context files and modified context files stay valid.
In the offline case, the context file is automatically generated and uploaded by the user, the update file is
downloaded and stored, and a new context file is generated as and uploaded. Thus, the developer has an actual
overview of the licenses already stored with each individual customer.
You are able to integrate this functionality into your software, or you can use WIBU-SYSTEMS’ standard
software installed with the CodeMeter runtime. See chapter 8 License Management - Backoffice Integration for
a detailed description of the online module designed for developer use.
21 | 44