Licensing (Magic xpi 4.13)
The Magic xpi 4.6 license mechanism is floating by nature, with an option to reserve a minimum number of license threads for each project.
If you are running multiple projects, and some projects may consume all threads under stress conditions (for example, there are many Web services and/or HTTP requests), you should consider reserving a minimum fixed amount of license threads for critical projects that need to run continually. For information about how to do this, click here.
All licenses produced by Magic Software Enterprises are now host locked. This means that once activated, you must use them on the machine used for the activation. In Magic xpi 4.6 clustered environments, you only need a single host locked license for the entire cluster. All Magic xpi installations should be configured to point to the same license file (you can put it in a shared location). All Magic xpi servers will start normally, even if they are running on a different host, but they will not run any flows until the server that was host locked runs a Magic xpi engine. The Magic xpi engine that runs on the host locked server is the only one that can update the thread count in the Space.
It is not even required that the Magic xpi engine on the host locked server continues to run. Once it sets the thread count in the Space, it is not needed anymore to maintain the license. It can therefore be stopped and started like any other Magic xpi engine on the grid.
