Skip to main content Skip to complementary content

Enabling JMX for Talend Remote Engine (optional)

Last updated: 9/9/2026
Starting with Talend Remote Engine v2.14.1, JMX monitoring is turned off by default. Enable it to monitor Talend Remote Engine locally or to configure remote JMX access from other machines.

About this task

After installation, enable JMX by installing the management feature from the Karaf console, as described in this procedure.

Procedure

  1. Connect to the Talend Remote Engine Karaf console using SSH.
  2. Run the following command:
    feature:install management

Results

JMX monitoring is enabled for Talend Remote Engine.

What to do next

To allow JMX connections from other machines, see Enabling remote access to Talend Remote Engine using JMX.

Enabling remote access to Talend Remote Engine using JMX

By default, JMX access is limited to localhost. To enable JMX connections from other machines, edit the configuration file.

About this task

Information noteWarning: Binding the engine to an address for remote access while the default credential in users.properties remains unchanged can be risky. For version-specific default credential behavior, see Changing the default Talend Remote Engine password.

This procedure configures the Karaf management (RMI) surface. It is separate from the JMXMP monitoring server configured by org.talend.jmxmp.ssl.*.

Procedure

  1. Open the <RemoteEngineInstallationDirectory>/etc/org.apache.karaf.management.cfg file.
    By default, the rmiRegistryHost and rmiServerHost values are set to localhost.
  2. Change the rmiRegistryHost and rmiServerHost values to 0.0.0.0, then save your changes.

Results

You can now connect to Talend Remote Engine from other machines using JMX.

What to do next

If your JMX client requests credentials, use the engine user configured in users.properties. For more information, see Changing the default Talend Remote Engine password.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!