JRebel Quick Start

Follow this quide to get JRebel up and running.
Pick your IDE on the right.

Watch it in action

JRebel Quick Start

NetBeans

Startup method: run via IDE (change) Startup method: command line (change) Startup method: remote server (change) Select server startup method

Installation Installing the JRebel plugin

  1. Open Tools > Plugins.
  2. Select the Available Plugins tab.
  3. Find JRebel and press Install.
  4. Next → Activation

Didn't work?

Don’t worry, you can also get the JRebel plugin from http://plugins.netbeans.org/plugin/22254/.

Once downloaded, open Tools > Plugins and find the Downloaded tab. Press Add Plugins, browse to the downloaded file and press Install.

Did this work?

If the installation was a success, your IDE will restart. After the restart, JRebel will alert you via a notification.

Activation Getting a license

  1. Open Help > JRebel > Activation.
  2. Fill out the form.
  3. Press Activate JRebel.
  4. Next → Startup configuration

Got a license?

Press I already have a license in the activation window.
  • Activation code. Paste your activation code if you have one already.
  • License file from the hard drive. Point to your jrebel.lic file. You get this file via email when you purchase JRebel.
  • Connect to License Server. Enter your Group URL and email. You get the Group URL from your network administrator.

Did this work?

JRebel will let you know that your license is activated via a notification.

Startup configuration Adding JRebel agent for your server or standalone application

How do you run your server?

  1. JRebel is automatically enabled for servers launched from NetBeans.
  2. Next → Project configuration

Good to know

Not running your server from the IDE? Select another application server startup method.

Did this work?

When successful, you will see the JRebel banner in the console right at server startup. This is what the JRebel banner should look like:
2016-11-15 12:19:20 JRebel:  #############################################################
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  JRebel Agent 7.0.0 (201611081555)
2016-11-15 12:19:20 JRebel:  (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Over the last 1 days JRebel prevented
2016-11-15 12:19:20 JRebel:  at least 0 redeploys/restarts saving you about 0 hours.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Licensed to ZeroTurnaround.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  #############################################################
  1. Open Help > JRebel > Configuration > Startup.
  2. Select Run locally from command line.
  3. Pick your desired Java and target environment.
  4. Follow the instructions provided to set up JRebel for your application server.
  5. Next → Project configuration

Good to know

Not running your server from a command line? Select another application server startup method.

You can find the same command line instructions in the JRebel reference manual.

Did this work?

When successful, you will see the JRebel banner in the console right at server startup. This is what the JRebel banner should look like:
2016-11-15 12:19:20 JRebel:  #############################################################
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  JRebel Agent 7.0.0 (201611081555)
2016-11-15 12:19:20 JRebel:  (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Over the last 1 days JRebel prevented
2016-11-15 12:19:20 JRebel:  at least 0 redeploys/restarts saving you about 0 hours.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Licensed to ZeroTurnaround.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  #############################################################
  1. Open Help > JRebel > Configuration > Startup.
  2. Select Run on a remote server.
  3. Pick your desired Java, target environment and operating system.
  4. Follow the instructions provided to set up JRebel for your remote application server.
  5. Next → Project configuration

Good to know

Not running your server remotely? Select another application server startup method.

You can find more help for setting JRebel up with a remote server over here.

Did this work?

When successful, you will see the JRebel banner in the console right at server startup. This is what the JRebel banner should look like:
2016-11-15 12:19:20 JRebel:  #############################################################
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  JRebel Agent 7.0.0 (201611081555)
2016-11-15 12:19:20 JRebel:  (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Over the last 1 days JRebel prevented
2016-11-15 12:19:20 JRebel:  at least 0 redeploys/restarts saving you about 0 hours.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Licensed to ZeroTurnaround.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  #############################################################

Project configuration Mapping your workspace to the deployed application

  1. Open Window > JRebel panel.
  2. Enable JRebel for the desired modules by selecting the column checkboxes.
  3. Redeploy your application!
  4. Next → IDE configuration

Didn't work?

Did this work?

When building your application, rebel.xml should be included within the application archive.
  • In case of JAR files, rebel.xml should be included in the root folder.
  • When working with WAR files, the rebel.xml should be located within the WEB-INF/classes folder.
  • EAR files require a rebel.xml for each internal EAR module (that means JARs and WARs).
  1. Open Window > JRebel panel.
  2. Enable JRebel for the desired modules by selecting the column checkboxes.
  3. Redeploy your application!
  4. Next → IDE configuration

Didn't work?

Did this work?

When building your application, rebel.xml should be included within the application archive.
  • In case of JAR files, rebel.xml should be included in the root folder.
  • When working with WAR files, the rebel.xml should be located within the WEB-INF/classes folder.
  • EAR files require a rebel.xml for each internal EAR module (that means JARs and WARs).
  1. Open Window > JRebel panel.
  2. Enable JRebel for the desired modules by selecting the column checkboxes.
  3. Redeploy your application!
  4. Next → IDE configuration

Didn't work?

Did this work?

When building your application, rebel.xml should be included within the application archive.
  • In case of JAR files, rebel.xml should be included in the root folder.
  • When working with WAR files, the rebel.xml should be located within the WEB-INF/classes folder.
  • EAR files require a rebel.xml for each internal EAR module (that means JARs and WARs).
  1. Open Window > JRebel panel.
  2. Enable JRebel for the desired modules by selecting the column checkboxes.
  3. Now select the jrebel-cloud-icon check-box next to your project. This will generate rebel-remote.xml.
  4. Redeploy your application!
  5. Next → IDE configuration

Didn't work?

Did this work?

When building your application, rebel.xml should be included within the application archive.
  • In case of JAR files, rebel.xml should be included in the root folder.
  • When working with WAR files, the rebel.xml should be located within the WEB-INF/classes folder.
  • EAR files require a rebel.xml for each internal EAR module (that means JARs and WARs).

IDE configuration Enabling compile on save

  1. Right-click your project node. Select Properties.
  2. Enable Build > Compile > Compile on Save.
  3. Disable Run > Deploy on Save.
  4. Next → Reload your code

Why do this?

These options will avoid unintended redeploys, making your experience a lot smoother.

JRebel relies upon your IDE to do the compiling. JRebel reloads your compiled .class files and not your .java files. When you change code, JRebel pushes the changed classes and resources to the server without redeploying.

Reload your code JRebel in action

  1. Restart your Java application.
  2. Change something in the application code and save.
  3. Refresh the application in the browser to see the changes!
Learn more at the JRebel Learn Center.