Enabling remote JMX with no authentication or SSL The following simple example starts the Network Server on the command line with insecure remote JMX management and monitoring enabled, using an Oracle JDK JVM. Java Management Extensions (JMX) technology JMXenabling without authentication

Password authentication over SSL is enabled by default, but here these security features are disabled, to keep the example simple.

It is not recommended to disable authentication or SSL in production environments.

java -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -jar $DERBY_HOME/lib/derbyrun.jar server start

When you start the Network Server from the command line, it automatically installs a security manager using a basic default security policy, unless you specify the -noSecurityManager option. You may need to customize this policy to make it suit your needs. See for details.