JRebel License Server
What you get with the JRebel License Server (in brief):
When you upload JRebel commercial licenses to the License Server…
- Developers simply download a license server token so that…
- You don’t have to distribute multiple licenses to multiple developers,
- There is no confusion about which licenses to use and
- You get to see:
- a) an overview of license utilization
- b) an overview of expiration dates
The JRebel License Server comes included with JRebel Enterprise and provides an easy way for companies to manage their multiple enterprise license subscriptions.
All of a company’s licenses are managed from a single point, providing a clear overview of the total available licenses, expiring licenses and current usage among the development team. Headcounts, license key emails, and setting up individual machines with different keys all become non-existent, freeing you to get back to work (hurrah!).
***
Downloads
Latest version 1.4.5
NB! “Offline mode” feature requires JRebel 4.5.5+
- zt-license-server.zip (md5/sha1)
- usage: java -jar zt-license-server.jar [port]
- Installation and configuration guide
Nightly build
***
Reporting with JRebel License Server – Redeploys prevented, time and financial savings
***
Technical information
- Built on Java™ technology (requires Java 1.6)
- Single JAR file
- Hosts all company’s licenses
- JRebel makes an HTTP request to the server to get a token
- JRebel requests a token every 10 minutes, as the current token expires
- The number of tokens given out cannot exceed the number of licenses
- Developers need to be connected to the network
***
How does it work?
- Your administrator downloads and installs the server on your network
- Purchased JRebel licenses are uploaded to that server
- Developers download a client license from that server
- On startup and after every 10 minutes, JRebel will ask for a token from the server
- Server gives a valid token if the number of concurrent users has not exceeded number of licenses
