[comment]: # ({7b11dd6e-e983a9df})
# Setup from Debian/Ubuntu packages

[comment]: # ({/7b11dd6e-e983a9df})

[comment]: # ({136210e6-a044dd01})
#### Overview

If [installed from packages](https://www.zabbix.com/download), the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java).

[comment]: # ({/136210e6-a044dd01})

[comment]: # ({c724b6af-01191552})
#### Configuring and running Java gateway

Java gateway configuration may be tuned in the file:

    /etc/zabbix/zabbix_java_gateway.conf

For more details, see Zabbix Java gateway configuration [parameters](/manual/concepts/java/java_gateway_params).

To start Zabbix Java gateway:

    systemctl restart zabbix-java-gateway

To automatically start Zabbix Java gateway on boot:

    systemctl enable zabbix-java-gateway

[comment]: # ({/c724b6af-01191552})

[comment]: # ({5bc1e089-81ca4902})
#### Configuring server for use with Java gateway

With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway.
This is done by specifying `JavaGateway` and `JavaGatewayPort` parameters in the [server configuration file](/manual/concepts/server/server_params).
If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/concepts/proxy/proxy_params) instead.

    JavaGateway=192.168.3.14
    JavaGatewayPort=10052

By default, server does not start any processes related to JMX monitoring.
If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers.
You do this in the same way you specify regular pollers and trappers.

    StartJavaPollers=5

Do not forget to restart server or proxy, once you are done with configuring them.

[comment]: # ({/5bc1e089-81ca4902})

[comment]: # ({aab546df-05f991d0})
#### Debugging Java gateway

Zabbix Java gateway log file is:

    /var/log/zabbix/zabbix_java_gateway.log

If you like to increase the logging, edit the file:

    /etc/zabbix/zabbix_java_gateway_logback.xml

and change `info` in `level="info"` to `debug` or even `trace` (for deep troubleshooting):

    <configuration scan="true" scanPeriod="15 seconds">
    [...]
          <root level="info">
                  <appender-ref ref="FILE" />
          </root>

    </configuration>

[comment]: # ({/aab546df-05f991d0})

[comment]: # ({27e67930-4332cfb8})
#### JMX monitoring

See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details.

[comment]: # ({/27e67930-4332cfb8})