0N/A#####################################################################
0N/A# Default Configuration File for Java Platform Management
0N/A#####################################################################
0N/A# will be read if one of the following system properties is set:
0N/A# The default Management Configuration file is:
0N/A# Another location for the Management Configuration File can be specified
0N/A# by the following property on the Java command line:
0N/A# number for the management agent can be specified in the config file
0N/A# using the following lines:
0N/A# ################ Management Agent Port #########################
0N/A# For setting the JMX RMI agent port use the following line
0N/A# For setting the SNMP agent port use the following line
0N/A#####################################################################
0N/A# Optional Instrumentation
0N/A#####################################################################
0N/A# By default only the basic instrumentation with low overhead is on.
0N/A# The following properties allow to selectively turn on optional
0N/A# instrumentation which are off by default and may have some
0N/A# additional overhead.
0N/A# This option enables thread contention monitoring if the
0N/A# Java virtual machine supports such instrumentation.
0N/A# interface - see isThreadContentionMonitoringSupported() method.
0N/A# To enable thread contention monitoring, uncomment the following line
0N/A#####################################################################
0N/A# SNMP Management Properties
0N/A#####################################################################
0N/A# - The SNMP agent (with the Java virtual machine MIB) is started
0N/A# that listens on the specified port for incoming SNMP requests.
0N/A# - the following properties for read for SNMP management.
0N/A# The configuration can be specified only at startup time.
0N/A# Later changes to the above system property (
e.g. via setProperty method), this
0N/A# config file, or the ACL file has no effect to the running SNMP agent.
0N/A# ##################### SNMP Trap Port #########################
0N/A# Specifies the remote port number at which managers are expected
0N/A# to listen for trap. For each host defined in the ACL file,
0N/A# the SNMP agent will send traps at <host>:<trap-destination-port-number>
0N/A# Default for this property is 162.
0N/A# To set port for sending traps to a different port use following line
0N/A# ################ SNMP listen interface #########################
0N/A# Specifies the local interface on which the SNMP agent will bind.
0N/A# This is usefull when running on machines which have several
0N/A# interfaces defined. It makes it possible to listen to a specific
0N/A# subnet accessible through that interface.
0N/A# Default for this property is "localhost".
0N/A# The format of the value for that property is any string accepted
0N/A# For restricting the port on which SNMP agent listens use following line
0N/A# #################### SNMP ACL file #########################
0N/A# Default for this property is true. (Case for
true/false ignored)
0N/A# If this property is specified as false then the ACL file
0N/A# is not checked: all manager hosts are allowed all access.
0N/A# For SNMP without checking ACL file uncomment the following line
0N/A# Specifies location for ACL file
0N/A# This is optional - default location is
0N/A# then this property and the ACL file are ignored.
0N/A# Otherwise the ACL file must exist and be in the valid format.
0N/A# If the ACL file is empty or non existent then no access is allowed.
0N/A# The SNMP agent will read the ACL file at startup time.
0N/A# Modification to the ACL file has no effect to any running SNMP
0N/A# agents which read that ACL file at startup.
0N/A# For a non-default acl file location use following line
0N/A#####################################################################
0N/A# RMI Management Properties
0N/A#####################################################################
0N/A# - A MBean server is started
0N/A# - JRE Platform MBeans are registered in the MBean server
0N/A# - RMI connector is published in a private readonly registry at
0N/A# specified port using a well known name, "jmxrmi"
0N/A# - the following properties are read for JMX remote management.
0N/A# The configuration can be specified only at startup time.
0N/A# Later changes to above system property (
e.g. via setProperty method),
0N/A# this config file, the password file, or the access file have no effect to the
0N/A# running MBean server, the connector, or the registry.
0N/A# ###################### RMI SSL #############################
0N/A# Default for this property is true. (Case for
true/false ignored)
0N/A# If this property is specified as false then SSL is not used.
0N/A# For RMI monitoring without SSL use the following line
0N/A# The value of this property is a string that is a comma-separated list
0N/A# of
SSL/TLS cipher suites to enable. This property can be specified in
0N/A# in order to control which particular
SSL/TLS cipher suites are enabled
0N/A# for use by accepted connections. If this property is not specified then
0N/A# are enabled by default.
0N/A# The value of this property is a string that is a comma-separated list
0N/A# of
SSL/TLS protocol versions to enable. This property can be specified in
0N/A# in order to control which particular
SSL/TLS protocol versions are
0N/A# enabled for use by accepted connections. If this property is not
0N/A# protocol versions that are enabled by default.
0N/A# Default for this property is false. (Case for
true/false ignored)
0N/A# If this property is specified as true in conjunction with the previous
0N/A# Socket Factory will require client authentication.
0N/A# For RMI monitoring with SSL client authentication use the following line
0N/A# Default for this property is false. (Case for
true/false ignored)
0N/A# If this property is specified as true then the RMI registry used
0N/A# to bind the RMIServer remote object is protected with
SSL/TLS 0N/A# RMI Socket Factories that can be configured with the properties:
0N/A# If the two properties below are true at the same time,
i.e. 0N/A# then the RMIServer remote object and the RMI registry are
0N/A# both exported with the same
SSL/TLS RMI Socket Factories.
0N/A# For using an
SSL/TLS protected RMI registry use the following line
0N/A# ################ RMI User authentication ################
0N/A# Default for this property is true. (Case for
true/false ignored)
0N/A# If this property is specified as false then no authentication is
0N/A# performed and all users are allowed all access.
0N/A# For RMI monitoring without any checking use the following line
0N/A# ################ RMI Login configuration ###################
0N/A# Specifies the name of a JAAS login configuration entry to use when
0N/A# authenticating users of RMI monitoring.
0N/A# Setting this property is optional - the default login configuration
0N/A# specifies a file-based authentication that uses the password file.
0N/A# When using this property to override the default login configuration
0N/A# then the named configuration entry must be in a file that gets loaded
0N/A# by JAAS. In addition, the login module(s) specified in the configuration
0N/A# should use the name
and/or password callbacks to acquire the user's
0N/A# credentials. See the NameCallback and PasswordCallback classes in the
0N/A# false, then this property and the password & access files are ignored.
0N/A# For a non-default login configuration use the following line
0N/A# ################ RMI Password file location ##################
0N/A# Specifies location for password file
0N/A# This is optional - default location is
0N/A# false, then this property and the password & access files are ignored.
0N/A# Otherwise the password file must exist and be in the valid format.
0N/A# If the password file is empty or non-existent then no access is allowed.
0N/A# For a non-default password file location use the following line
0N/A# ################ RMI Access file location #####################
0N/A# Specifies location for access file
0N/A# This is optional - default location is
0N/A# false, then this property and the password & access files are ignored.
0N/A# Otherwise, the access file must exist and be in the valid format.
0N/A# If the access file is empty or non-existent then no access is allowed.
0N/A# For a non-default password file location use the following line