Installing the JRebel plugin and activation

https://www.jrebel.com/products/jrebel/quickstart/eclipse#!/activation

Installing the JRebel plugin

  1. Open Help > Eclipse Marketplace...
  2. Search for JRebel and XRebel. Found it? Press Install.

Didn't work?

Don't worry, you can also install JRebel using:

  1. Update site URL. Open Help > Install New Software and enter the URL for our update site: http://update.zeroturnaround.com/update-site. We recommend you uncheck the option for Contact all update sites during install to find required software. Follow the prompts to complete the installation.
  2. Download ZIP. The Eclipse plugin update can also be downloaded as ZIP archive from http://update.zeroturnaround.com/update-site/update-site.zip. Once downloaded, open Help > Install New Software and press Add. Select Archive to point to the ZIP archive of the update site. Press OK to proceed.

When you do not have m2eclipse installed, uncheck the JRebel m2eclipse plugin during installation.

 


https://manuals.jrebel.com/license-server/configuration/client-configuration.html

Client activation

This section provides details on how to activate clients with Rebel Licenses On-Premise.

License activation rules

The license can be shared between devices. The same license cannot be used on different devices simultaneously. The following restrictions apply:

  • The previous device loses its seat within 60 minutes.

  • The license can be switched between devices only every 60 minutes.

Offline seats

The offline seat mode allows Rebel Licenses On-Premise users to go offline for a predefined period of time. This is useful when working away from the office or in an offline environment. During this time, the active offline seat is locked on the Rebel Licenses On-Premise and the product can be used without an active Rebel Licenses On-Premise connection.

The offline seat mode has to be activated manually, in the IDE plugin, or by using a command line parameter. Taking the seat offline has to happen while still connected to the Rebel Licenses On-Premise. An offline seat will cease working as soon as the predefined duration elapses or once the user manually disables offline seat mode.

Eclipse

  1. Open Help > JRebel Configuration.

  2. Locate Licensing.

  3. Set the desired duration and press Work offline.

You can cancel offline seat mode by pressing Work online whenever Rebel Licenses On-Premise connection is restored.

IntelliJ IDEA

  1. Open File > Settings > JRebel > Offline mode.

  2. Set the desired duration and press Work offline.

You can cancel offline seat mode by pressing Work online whenever Rebel Licenses On-Premise connection is restored.

NetBeans

  1. Open Tools > Options > JRebel > Offline.

  2. Set the desired duration and press Work offline.

You can cancel offline seat mode by pressing Work online whenever Rebel Licenses On-Premise connection is restored.

XRebel

  1. Open Settings > About.

  2. Set the desired duration and press Work offline.

You can cancel offline seat mode by pressing Work online whenever Rebel Licenses On-Premise connection is restored.

Offline seat with standalone configuration

Rebel Licenses On-Premise requires a connection to be maintained to the Rebel Licenses On-Premise at all times. If you need to work offline, you can acquire an offline seat:

$ java -Drebel.license.url=http://your.server:9000/01234abcd01234abcd -jar jrebel.jar -go-offline

The default offline seat will last for 24 hours. You can ask for an offline seat for a period up to 15 days by providing the desired number of days as the last argument:

$ java -Drebel.license.url=http://your.server:9000/01234abcd01234abcd -jar jrebel.jar -go-offline 7

Be aware that this will keep one license seat occupied on the server-side for the entire offline period. To delete your offline seat and release the seat for others to use, use -go-online. This seat is reserved on the Rebel Licenses On-Premise until offline mode expiration or until the user manually deletes the offline seat.

$ java -Drebel.license.url=http://your.server:9000/01234abcd01234abcd -jar jrebel.jar -go-online

Should the -go-online command fail for some reason, you may consider manually deleting the offline seat. Use the -delete-offline command to force the deletion of your local offline seat.

Warning

Please note that this command should only be used as a last resort. Manually deleting an offline seat will remove the license from the local machine, but the seat will not be freed up on the server.

$ java -Drebel.license.url=http://your.server:9000/01234abcd01234abcd -jar jrebel.jar -delete-offline

Activating JRebel standalone with Rebel Licenses On-Premise

JRebel can be activated with Rebel Licenses On-Premise licensing with the command line command -activate, i.e.:

$ java -jar jrebel.jar -activate http://license-server.mycompany.com/1a2b-3c4d-e56f-7gh8 john@mycompany.com

Tip

Alternatively, you can use the standalone activation wizard to activate standalone JRebel (executed by the script at bin/activate-gui.[sh|cmd]).

Another way to activate JRebel with Rebel Licenses On-Premise is by directly setting the properties either in jrebel.properties file or on command line. Set the property rebel.license.url to your Team URL and property rebel.license.email to your email:

rebel.license.url=http://license-server.mycompany.com/1a2b-3c4d-e56f-7gh8
rebel.license.email=john@mycompany.com

Standalone configuration options

Customize username

Rebel Licenses On-Premise displays the JRebel user name. This defaults to the operating system user name, but can be customized as:

rebel.user=john@company.com

Average deploy time

Rebel Licenses On-Premise uses the average deploy time reported by JRebel to calculate time saved. To specify the average deploy time (in seconds):

rebel.stats.time=120
https://manuals.jrebel.com/jrebel/advanced/hybris.html#startup-configuration

Debugging with JRebel

To enable JRebel for Hybris while debugging, the following JVM startup parameters need to be added to $PLATFORM_HOME/config/local.properties. We recommend using the JRebel IDE plugins for the best debugging experience.

  1. Add the following to use the JRebel Agent while debugging:

    JDK

    Startup parameter

    Windows 64-bit JDK

    tomcat.debugjavaoptions=-agentpath:[c:\path\to]\lib\jrebel64.dll

    Windows 32-bit JDK

    tomcat.debugjavaoptions=-agentpath:[c:\path\to]\lib\jrebel32.dll

    Mac OS X 64-bit JDK

    tomcat.debugjavaoptions=-agentpath:[path/to]/lib/libjrebel64.dylib

    Mac OS X 32-bit JDK

    tomcat.debugjavaoptions=-agentpath:[path/to]/lib/libjrebel32.dylib

    Linux 64-bit JDK

    tomcat.debugjavaoptions=-agentpath:[path/to]/lib/libjrebel64.so

    Linux 32-bit JDK

    tomcat.debugjavaoptions=-agentpath:[path/to]/lib/libjrebel32.so

  2. Add the tomcat.debugjavaoptions value to your $PLATFORM_HOME/bin/platform/project.properties file. It should also include -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000, otherwise the JVM will not start in debug mode.

    Example: tomcat.debugjavaoptions=-agentpath:c:\jrebel\lib\jrebel64.dll -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000

Tip

Run the command ant all after changing the properties file to apply the new configuration!

You can verify that JRebel is started by running Hybris with the debug command:

./hybrisserver.sh debug

Look for the following lines in the console log:

2019-04-02 14:23:55 JRebel:  JRebel Agent 2020.1.0 (202001051049)
2019-04-02 14:23:55 JRebel:  (c) Copyright 2007-2020 Perforce Software, Inc.

Comments

Post a Comment

Popular Posts