Pre requisites

1. EnablingJava RemoteRuntime JMXEnvironment
The Monitoringplugin forruns an Oculix JAR file, so it is necessary to have Java Applications
Ainstalled and accessible in the system PATH. Java application17 doesor nothigher requireis additionalrecommended.

software

2. installed,Graphical butenvironment
The plugin uses mss to take screenshots, so it requires a running X11 server (graphical environment). If running in a headless environment, a virtual X server such as Xvfb can be used.

3. Write permissions
The plugin needs write permissions in the artifacts directory (--artifacts) to store screenshots, baseline images, and diffs.

4. Tentacle (optional)
If the tentacle transfer mode is used, the tentacle_client binary must be startedinstalled withand accessible on the following command line options to enable support for remote JMX monitoring.system.

At the very least, if you only want to start monitoring a basic Java application on a local host without security, use these options:

-Dcom.sun.management.jmxremote \
-Dcom.sun.management.jmxremote.authenticate=false \
-Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.port=9090 \
-Dcom.sun.management.jmxremote.rmi.port=9090 \
-Djava.rmi.server.hostname=localhost"

This configures Java to accept incoming JMX connections on port 9090 from localhost only, with no authentication or SSL required.

If authentication is required, it must be enabled:

-Dcom.sun.management.jmxremote \
-Dcom.sun.management.jmxremote.authenticate=true \
-Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.port=9090 \
-Dcom.sun.management.jmxremote.rmi.port=9090 \
-Djava.rmi.server.hostname=localhost \
-Dcom.sun.management.jmxremote.password.file=/usr/local/tomcat/conf/jmxremote.password \
-Dcom.sun.management.jmxremote.access.file=/usr/local/tomcat/conf/jmxremote.access

2. The system running the plugin must have connectivity and be able to reach the JMX server.