zabbix java gateway ( secure setup )

[gofree]

Hi all,

suggestion and question at the same time....

when I need to configure zabbix-java-gateway for secure ssl configuration through jmx protocol ( I know how ) I need to adjust /usr/sbin/zabbix_java_gateway starting script. The problem is that every time zabbix-java-gateway in updated ( example: yum update on CentOS7) the file gets overwritten and the secure communication adjustments are lost.

So what can I do?

a) create a copy of that script someplace else and adjust systemd unit file for the new path ( check on every update for changes )
b) adjust the /usr/sbin/zabbix_java_gateway after every update
c) any good ideas I cant see at the moment ?

Thanks guys

[Atsushi]

Is it not possible to realize it by describing it in the following configuration files?

/etc/zabbix/zabbix_java_gateway.conf
/etc/sysconfig/zabbix-java-gateway

[gofree]

I dont think so, sure not in the first file and the second is not created when installed from rpm packages.

Furthermore the documentation describes adding the -Djavax.net.ssl.* to startup.sh script ( not present when installed from rpm packages ) so I guess for rpm packages its /usr/sbin/zabbix_java_gateway ( bit pain to adjust it every update )

https://www.zabbix.com/documentation/5.0/manual/config/items/itemtypes/jmx_monitoring

[Atsushi]

Can't you add settings to JAVA_OPTIONS in the following files?
/etc/zabbix/zabbix_java_gateway.conf

This file should not be overwritten when the package is updated.

[gofree]

I'll try and report back - but I dont think it would work

https://www.zabbix.com/documentation/5.0/manual/appendix/config/zabbix_java

edit - I remeber now that this cant as the java option in the zabbix java gateway conf file file are intended for zabbix java gateway itself


# uncomment to enable remote monitoring of the standard JMX objects on the Zabbix Java Gateway itself
#JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12345
# -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"

edit2 - maybe I was to fast - it might work , will try out and get back

yes it works, I was thinking and reading too fast - anyway documentation could be a bit more clear on this topic ( in case I overlooked something pelase correct me)

JAVA_OPTIONS="$JAVA_OPTIONS -Djavax.net.ssl.trustStore=/path/to/file ....etc"