

- #Jrebel license file how to#
- #Jrebel license file driver#
- #Jrebel license file manual#
- #Jrebel license file archive#
- #Jrebel license file registration#
Below is the example log of a Tomcat server running with the new license enabled. C:\Program Files\ZeroTurnaround\JRebel\client.lic).ĩ After the file is placed in the correct location JRebel will use it to communicate with the central license server. To make JRebel installation aware of the fact that it should go to a particular URL for license verification, one should place client.lic file in the same directory where jrebel.jar is located, (e.g. Installing the license file JRebel application will use client.lic file to verify the license against the central server from where it was downloaded. The URL you will sent to the person will look similar to 2) Or, download client.lic file yourself by hitting Download developer token link, and send the file over to all the developers in your team.
#Jrebel license file how to#
Now there are two options of how to distribute the token: 1) Right mouse click, choose Copy link address, and send it to the person who needs a license. On the upper right of the screen, find a link Download developer token. On the screen you will find the information about your current licenses: the timeframe for which the licenses are valid, how many seats are available, etc.Ĩ Download developer token To make a single JRebel installation aware of the license server one should download the token from the license server. Managing your licenses To manage your licenses, proceed to the Account tab. On the dashboard, the general information is presented about the server and current active users. Additionally, the primary server host information is required in order for the fallback instance to communicate with the primary license server.Ħ Validating the installation On the very first screen after the user logs in to the application, the dashboard is displayed. To configure the fallback instance, click the Fallback License Server link at the setup page when the license server instance is started the first time.ĥ The setup form will ask for the same information as for the primary server instance. The fallback license server It is possible to setup a fallback instance of the license server either on the same host or some other machine that can reach the primary instance of the license server via the network.
#Jrebel license file registration#
The host name should be set to the IP of the machine where the license server will be hosted.Ĥ After submitting the registration for the server is ready for service. Note that the will serve as administrator user name for this server instance. Click the Primary License Server link to proceed with the registration: The next screen will ask for the server registration details. But generally the server can be started by the following command: java jar lib/zt-license-server.jar Once the command above is executed, the following messages will indicate that the server is started: 18:12:25,589 INFO ~ Connected to jdbc:hsqldb:file:data/db 18:12:26,796 INFO ~ Application 'ZeroTurnaround License Server' is now started! 18:12:27,680 INFO ~ Slf4jLog Started The license server is now available at open the URL in the browser and proceed with registration.ģ Configuration Browse to and you should see the following screen: If you upgrading your Jrebel License Server to new version, you can migrate the data from old server to the new one. The bin/ directory contains scripts for Windows and *nix platforms to execute the server. The conf/frontend.properties file allows you to list proxy server IP addresses if you want to use a front end HTTP server between your users and the license server, for example for load balancing. The database schema will be automatically created on startup, so the user should have create privileges. To switch to MySQL, replace the db.properties file with db.mysql.properties (rename db.mysql.properties to db.properties) and change the values to reflect your MySQL setup. By default the HSQLDB database is used, but MySQL is also supported.

#Jrebel license file driver#
The content of the directory should look as follows: C:/zt-license-server/ - bin/ - conf/ - db.properties `- frontend.properties - lib/ - Changelog.txt `- README.txt The conf/db.properties file determines the database driver and connection used by the license server for storing its data.
#Jrebel license file archive#
Installation Download the ZIP package available at and unzip the archive to the desired location. Once the user has received the license he purchased, the file can be uploaded to the central license server to be distributed among the developer seats.
#Jrebel license file manual#
1 ZeroTurnaround License Server User Manual 1.4.0Ģ Overview The ZeroTurnaround License Server is a solution for the clients to host their JRebel licenses.
