Skip to end of metadata
Go to start of metadata

We are trying to keep a licensing model as simple and usable as possible. Thus, Q7 Professional uses only floating licenses, which is useful even when there's a single Q7 user – having one license it is possible to run Q7 Professional on different machines with different operating systems. On contrary side, Q7 Runner uses license files locked to a specific machine, so that dedicated build servers without internet access can be licenses for execution of Q7 tests during continuous integration. 

Floating licenses for Q7 Professional reside on our centralized license server located at However, by customer request, we give a customer license file so that the local license server can be installed in company's intranet. The license server is a single JAR file (we officially support Oracle JRE 1.6+) which can be started in a command line with a few arguments, in a simplest form just like this:

$ java -jar q7.server.local.jar -licenseFile

The table below summarizes the full list of command line arguments

licenseFile​Path to a customer license file​


c:\Users\user\q7\ ​

portPort to start a license server on. Default value is 808080
dataDirThe directory where license server can store temporary files. By default it is created in $user.home/.q7statesc:\Users\users\q7data
remoteAddrThe domain name of a machine this server is running on as it is visible to its users. This property is purely cosmetic and only affects the License URL for Q7 as it is displayed on a server

Once local license server is launched, the url http://local-license-server:8080/pool can be used in Q7 Professional settings. Also as with a centralized license server, customer credentials can be used to log in into license server web interface to see the current Q7 Professional license usage and manage (activate/deactivate/download) Q7 Runner licenses.