"java bridge" might be even more confusing, as zapcat's "second name" is "JMX Zabbix Bridge"

maybe renaming is not needed, but extensive & proper documentation on what it is and what it does (and how) might be very helpful.

The following ideas for new naming have been generated so far:

Zabbix Java Bridge
Zabbix Java Gateway
Zabbix Java Portal
Zabbix Java Door
Zabbix Java Connector
Zabbix Java Translator
Zabbix Java Wizard
Zabbix Java Speaker
Zabbix Java Caller
Zabbix Java Messenger
Zabbix Java Embassy
Zabbix Java Enabler
Zabbix Java Interface
Zabbix Java Transport
Zabbix Java Tunnel

<richlv> if it is renamed, i'd probably prefer "gateway"

<alexei> "gateway" is ok to me as well

<richlv> personally, i'm fine with "zabbix java proxy"

I just got confused, when I thought about the RPM sub-package description!

Also we have to change default port to 10052 for easier configuration when all components are on the same box.

<richlv> that's not iana registered, though - would be better not to use unassigned ports in default configuration

Available in development branch svn://svn.zabbix.com/branches/dev/ZBX-3710 .

Updated the following pages in documentation:

http://www.zabbix.com/documentation/2.0/manual/concepts/java

http://www.zabbix.com/documentation/2.0/manual/appendix/config/zabbix_java
http://www.zabbix.com/documentation/2.0/manual/appendix/config/zabbix_server
http://www.zabbix.com/documentation/2.0/manual/appendix/config/zabbix_proxy

http://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes
http://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/jmx_monitoring
http://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/7_internal_checks
http://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew200?&#direct_jmx_monitoring_support
http://www.zabbix.com/documentation/2.0/contrib/manual_outline

Available in pre-1.9.8 in r22824.