Áú»¢¶Ä²©

2 Setup from RHEL/CentOS packages

Overview

If installed from RHEL/CentOS packages, the following information will help you in setting up Áú»¢¶Ä²© Java gateway.

Configuring and running Java gateway

Configuration parameters of Áú»¢¶Ä²© Java gateway may be tuned in the file:

/etc/zabbix/zabbix_java_gateway.conf

For more details, see Áú»¢¶Ä²© Java gateway configuration parameters.

To start Áú»¢¶Ä²© Java gateway:

# service zabbix-java-gateway restart

To automatically start Áú»¢¶Ä²© Java gateway on boot:

RHEL 7 and later:

# systemctl enable zabbix-java-gateway

RHEL prior to 7:

# chkconfig --level 12345 zabbix-java-gateway on

Configuring server for use with Java gateway

With Java gateway up and running, you have to tell Áú»¢¶Ä²© server where to find Áú»¢¶Ä²© Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the server configuration file. If the host on which JMX application is running is monitored by Áú»¢¶Ä²© proxy, then you specify the connection parameters in the proxy configuration file 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.

Debugging Java gateway

Áú»¢¶Ä²© 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 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>

JMX monitoring

See JMX monitoring page for more details.