![]() ![]() The connection is treated by the license server as a local, not a network connection, which means that the license server can also use licenses that are made available by another host with CodeMeter as a network server. ![]() This is done by configuring the CODEMETER_HOST variable, which the CodeMeter libraries can read to make contact with the CodeMeter license server. The CodeMeter network needs to be connected with all containers involved, and all containers need to know the address of the container storing the CodeMeter license server. ![]() The solution: Just create an additional network. An application running in one container could never find the CodeMeter license server in another container. But this straightforward setup is broken when working with Docker or similar container-based systems. On conventional operating systems, CodeMeter works according to a simple rule: the CodeMeter functions built into an application’s protection will find the necessary CodeMeter license server on the same system. With the changes, CodeMeter now stays true to the basic principle of “one container, one application” and also includes a special form of binding for CmActLicenses in Docker containers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |