FAQ
JRebel Enterprise is a lightweight service that acts as a central communication layer between the JRebel IDE plugin and remote JRebel agents running inside JVMs. It enables real-time code syncing and hot-reload across distributed environments, which is especially useful in fast-paced, cloud-native setups where redeployments are slow and expensive.
JRebel Enterprise is designed to support remote development workflows, allowing developers to push code changes directly from their IDE to remote applications running in containers, Kubernetes pods, or VMs without requiring full redeployment.
Traditional remoting involves a direct IDE and JRebel agent connection. JRebel Enterprise introduces an intermediate registry and messaging layer IDE – Broker – Agent, so you no longer need to configure individual VM details manually.
There are three steps to install and configure JRebel Enterprise.
- Broker Service: Deploy the Broker JAR on a reachable host.
- JR Agent: Point your existing JRebel-enabled JVMs at the Broker URL.
- IDE Plugin: In your IDE’s JRebel settings, enter the same Broker URL so it can discover registered agents.
The configuration manager within JRebel Enterprise operates as an intermediary. When a JRebel agent starts (within a JVM), it connects to the configuration manager and registers itself in a zone using a configured URL. The IDE plugin also connects to the same configuration manager and retrieves a list of available applications/modules grouped by zones.
No. You continue coding in your IDE exactly as before. Simply point JRebel’s remoting URL to your configuration manager and all remote JVMs appear automatically in your IDE under broker menu.
Agents and IDEs automatically retry registrations and sync transactions on reconnect. The three-phase protocol ensures partial transactions roll back cleanly, so no code is applied twice or left half-applied.
Yes, JRebel Enterprise is designed to support cloud-native scenarios including Kubernetes and Docker. Each JVM or pod can register separately with the configuration manager, and syncs are routed accordingly.
We’re happy to customize a JRebel Enterprise package to meet your organization’s unique needs. Request a quote today.
JRebel Enterprise integrates directly with IntelliJ IDEA. It works best with cloud-based, containerized, and remote development environments, e.g., Docker, Kubernetes, or virtual machines.
JRebel eliminates redeploys, enabling developers to visualize code changes instantly while maintaining application state. JRebel Enterprise builds upon that time-saving power while also offeringing simplified, one-time configuration for cloud development environments.
JRebel Enterprise is well-suited for clients working in remote, containerized, or cloud-based development environments.
JRebel Enterprise easily integrates into the developer’s IDE as plugin and automatically discovers and registers new JVMs via the broker functionality.
JRebel Enterprise works with Java 21 and newer versions.
Yes, you can absolutely customize the "zone" labels in the JRebel Broker configuration file. This allows you to name them according to your team names, environments (like dev/test/prod), or even specific tickets. Additionally, you can set up Access Control List (ACL) rules. These rules define specific permissions or restrictions for who can access certain zones.