Server configuration

To enable the JRebel Agent for the container that the application is deployed to, you need to add a -agentpath parameter to the JVM arguments list. For that you need to modify your server startup script. The remote server support plugin is disabled by default. You need to add a JVM argument to activate it:

-agentpath:[/path/to/JRebel Agent] -Drebel.remoting_plugin=true

The JRebel Agent library differs based on operating system and architecture: Add the following to use the JRebel Agent:

JDK	Startup parameter
Windows 64-bit JDK	-agentpath:[c:\path\to]\lib\jrebel64.dll
Windows 32-bit JDK	-agentpath:[c:\path\to]\lib\jrebel32.dll
Mac OS X 64-bit JDK	-agentpath:[path/to]/lib/libjrebel64.dylib
Mac OS X 32-bit JDK	-agentpath:[path/to]/lib/libjrebel32.dylib
Linux 64-bit JDK	-agentpath:[path/to]/lib/libjrebel64.so
Linux 32-bit JDK	-agentpath:[path/to]/lib/libjrebel32.so

For more information on JRebel Agent startup, please refer to running servers from the command line.

Using a dedicated port (optional)

When your application, deployed to a remote server does not have an HTTP endpoint (e.g. EJB modules and standalone applications), you can designate a port for remote server support to enable JRebel’s embedded Jetty container. Adding -Drebel.remoting_port=[port number] (e.g. -Drebel.remoting_port=12345) enables the embedded Jetty container inside JRebel. This will be used for handling HTTP requests from the IDE plugin.

Warning

Enabling Jetty will impact performance.

Server-side password configuration

To enable password-based security on the server, set the server password using the following command:

$ java -jar jrebel.jar -set-remote-password