KEYnote 36 English - Fall 2018 - Page 9

System Setup A TMR Server Setup consists of a total of five servers, typically operated as virtual machines. The downstream interface with the clients is provided by a double TMR server that the clients can access via a virtual IP address. The TMR server creates the virtual CmContainers and the TMR licenses within them based on the CmContainers kept on the three upstream CodeMeter servers. partner immediately of all changes in its state, including the system configuration, the virtual CmContainers, the current license allocations, and all handles used by the upstream Code- Meter servers. will facilitate integration into existing business processes. This will include mechanisms for replacing individual CmContainers efficiently, e.g. if some hardware problems require a CodeMeter server to be replaced. Whenever the servers are forced to switch places, errors or required maintenance interventions can mean a downtime of a few seconds or the potential loss of individual packets. At the same time, the software for the TMR server is expanded to create a license request file for the entire group that contains all the required individual context files. Such update Client TMR Server A CodeMeter Communication Failover TMR Server Setup CodeMeter Communication In case of error, IP takeover Replication Client Client Client TMR Server B Client Virtual IP Address Linux TMR Server In the corporate network, the TMR Server Setup can be reached via a single virtual IP address, which channels all queries to the active TMR server. When the TMR server first connects to the network infrastructure, the switch, it informs the system that it wants to receive packets destined both for its own IP address and for the assigned virtual IP addresses. The TMR service running on the TMR server is a new development that supports all incoming CodeMeter API calls that are compatible with the first CodeMeter version supporting the Universal Firm Code, namely Version 6.10. The system itself is an original Debian OS equipped with open source software and the TMR service. The passive TMR server monitors the avail- ability of the active TMR server via a regular keep-alive check. Should the active TMR server not be available, its passive counter- part informs the network that the packets for the virtual IP address should now go to it – seamlessly stepping into the place of the active TMR server. Active and Passive For this feat to work, the passive TMR server has to be aware of the current state of the active server at all times. The active TMR server ensures this by notifying its passive Upstream from the double TMR servers, there are the three CodeMeter servers, which can be run under Linux or Windows. With minimal changes to the CodeMeter settings, the licenses on these servers can only be accessed through the two TMR servers. No client could ever use them directly. files received through the same channel will be unpacked and installed onto the upstream CodeMeter servers in the sequence of their arrival. This ensures perfect cooperation between CodeMeter License Central and the TMR Server Setup – using the same processes that one would use for a single CodeMeter server. ISVs might only have to add tiny adjustments to their activation software. Licensing The first version of the TMR package will be available for licensing from Wibu-Systems beginning in November 2018. Payment is handled by subscription for each installed TMR Server Setup. Business Processes TMR licenses can be programmed separate- ly with the high-level programming API or its incarnation in the command line tool CmBoxPgm. When doing so, the mentioned TMR ID would have to be assigned manually. From early 2019, CodeMeter License Central 9