e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#####################################################################

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# Default Configuration File for Java Platform Management

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#####################################################################

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# The Management Configuration file (in java.util.Properties format)

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# will be read if one of the following system properties is set:

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# -Dcom.sun.management.jmxremote.port=<port-number>

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# or -Dcom.sun.management.snmp.port=<port-number>

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# or -Dcom.sun.management.config.file=<this-file>

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# The default Management Configuration file is:

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# $JRE/lib/management/management.properties

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# Another location for the Management Configuration File can be specified

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# by the following property on the Java command line:

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

fb86717633bfcfe161571aed7058ea6a39b7a69bkiirala# -Dcom.sun.management.config.file=<this-file>

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# If -Dcom.sun.management.config.file=<this-file> is set, the port

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# number for the management agent can be specified in the config file

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# using the following lines:

000dfc9dd0bc3d8cd37fabe93f6f9d1ede190adfnicholasbishop#

000dfc9dd0bc3d8cd37fabe93f6f9d1ede190adfnicholasbishop# ################ Management Agent Port #########################

000dfc9dd0bc3d8cd37fabe93f6f9d1ede190adfnicholasbishop#

000dfc9dd0bc3d8cd37fabe93f6f9d1ede190adfnicholasbishop# For setting the JMX RMI agent port use the following line

000dfc9dd0bc3d8cd37fabe93f6f9d1ede190adfnicholasbishopcom.sun.management.jmxremote.port=4444

000dfc9dd0bc3d8cd37fabe93f6f9d1ede190adfnicholasbishop#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# For setting the SNMP agent port use the following line

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# com.sun.management.snmp.port=<port-number>

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#####################################################################

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# Optional Instrumentation

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#####################################################################

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# By default only the basic instrumentation with low overhead is on.

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# The following properties allow to selectively turn on optional

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# instrumentation which are off by default and may have some

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# additional overhead.

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# com.sun.management.enableThreadContentionMonitoring

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# This option enables thread contention monitoring if the

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# Java virtual machine supports such instrumentation.

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# Refer to the specification for the java.lang.management.ThreadMBean

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# interface - see isThreadContentionMonitoringSupported() method.

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# To enable thread contention monitoring, uncomment the following line

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# com.sun.management.enableThreadContentionMonitoring

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#####################################################################

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# SNMP Management Properties

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#####################################################################

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# If the system property -Dcom.sun.management.snmp.port=<port-number>

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# is set then

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# - The SNMP agent (with the Java virtual machine MIB) is started

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# that listens on the specified port for incoming SNMP requests.

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# - the following properties for read for SNMP management.

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

fb86717633bfcfe161571aed7058ea6a39b7a69bkiirala# The configuration can be specified only at startup time.

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala# Later changes to the above system property (e.g. via setProperty method), this

aec1b94c999035922cd8c19878a4618883f5179bbryce# config file, or the ACL file has no effect to the running SNMP agent.

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala#

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala#

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala# ##################### SNMP Trap Port #########################

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala#

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala# com.sun.management.snmp.trap=<trap-destination-port-number>

59a89a640809c6f03a69fd3df823c5bef1260424kiirala# Specifies the remote port number at which managers are expected

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# to listen for trap. For each host defined in the ACL file,

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# the SNMP agent will send traps at <host>:<trap-destination-port-number>

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# Default for this property is 162.

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# To set port for sending traps to a different port use following line

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# com.sun.management.snmp.trap=<trap-destination-port-number>

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# ################ SNMP listen interface #########################

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# com.sun.management.snmp.interface=<InetAddress>

9a3bd4fde0634126efeedaa71a0b66acf6ef07a2jucablues# Specifies the local interface on which the SNMP agent will bind.

9a3bd4fde0634126efeedaa71a0b66acf6ef07a2jucablues# This is usefull when running on machines which have several

1a37ce4a40095c20d83ed6ab3dce34f53bac1b65kiirala# interfaces defined. It makes it possible to listen to a specific

9a3bd4fde0634126efeedaa71a0b66acf6ef07a2jucablues# subnet accessible through that interface.

9a3bd4fde0634126efeedaa71a0b66acf6ef07a2jucablues# Default for this property is "localhost".

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# The format of the value for that property is any string accepted

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# by java.net.InetAddress.getByName(String).

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# For restricting the port on which SNMP agent listens use following line

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues# com.sun.management.snmp.interface=<InetAddress>

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues

1730be3267d05b3e758c91af8ed41a026f6babb6jucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# #################### SNMP ACL file #########################

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# com.sun.management.snmp.acl=true|false

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# Default for this property is true. (Case for true/false ignored)

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# If this property is specified as false then the ACL file

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# is not checked: all manager hosts are allowed all access.

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# For SNMP without checking ACL file uncomment the following line

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# com.sun.management.snmp.acl=false

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues#

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# com.sun.management.snmp.acl.file=filepath

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# Specifies location for ACL file

e50fb78bbe0c001b3ca6040ba25ae6e75dc9385fjucablues# This is optional - default location is

# $JRE/lib/management/snmp.acl

#

# If the property "com.sun.management.snmp.acl" is set to false,

# then this property and the ACL file are ignored.

# Otherwise the ACL file must exist and be in the valid format.

# If the ACL file is empty or non existent then no access is allowed.

#

# The SNMP agent will read the ACL file at startup time.

# Modification to the ACL file has no effect to any running SNMP

# agents which read that ACL file at startup.

#

# For a non-default acl file location use following line

# com.sun.management.snmp.acl.file=filepath

#####################################################################

# RMI Management Properties

#####################################################################

#

# If system property -Dcom.sun.management.jmxremote.port=<port-number>

# is set then

# - A MBean server is started

# - JRE Platform MBeans are registered in the MBean server

# - RMI connector is published in a private readonly registry at

# specified port using a well known name, "jmxrmi"

# - the following properties are read for JMX remote management.

#

# The configuration can be specified only at startup time.

# Later changes to above system property (e.g. via setProperty method),

# this config file, the password file, or the access file have no effect to the

# running MBean server, the connector, or the registry.

#

#

# ###################### RMI SSL #############################

#

# com.sun.management.jmxremote.ssl=true|false

# Default for this property is true. (Case for true/false ignored)

# If this property is specified as false then SSL is not used.

#

# For RMI monitoring without SSL use the following line

# com.sun.management.jmxremote.ssl=false

# com.sun.management.jmxremote.ssl.enabled.cipher.suites=<cipher-suites>

# The value of this property is a string that is a comma-separated list

# of SSL/TLS cipher suites to enable. This property can be specified in

# conjunction with the previous property "com.sun.management.jmxremote.ssl"

# in order to control which particular SSL/TLS cipher suites are enabled

# for use by accepted connections. If this property is not specified then

# the SSL/TLS RMI Server Socket Factory uses the SSL/TLS cipher suites that

# are enabled by default.

#

# com.sun.management.jmxremote.ssl.enabled.protocols=<protocol-versions>

# The value of this property is a string that is a comma-separated list

# of SSL/TLS protocol versions to enable. This property can be specified in

# conjunction with the previous property "com.sun.management.jmxremote.ssl"

# in order to control which particular SSL/TLS protocol versions are

# enabled for use by accepted connections. If this property is not

# specified then the SSL/TLS RMI Server Socket Factory uses the SSL/TLS

# protocol versions that are enabled by default.

#

# com.sun.management.jmxremote.ssl.need.client.auth=true|false

# Default for this property is false. (Case for true/false ignored)

# If this property is specified as true in conjunction with the previous

# property "com.sun.management.jmxremote.ssl" then the SSL/TLS RMI Server

# Socket Factory will require client authentication.

#

# For RMI monitoring with SSL client authentication use the following line

# com.sun.management.jmxremote.ssl.need.client.auth=true

# com.sun.management.jmxremote.registry.ssl=true|false

# Default for this property is false. (Case for true/false ignored)

# If this property is specified as true then the RMI registry used

# to bind the RMIServer remote object is protected with SSL/TLS

# RMI Socket Factories that can be configured with the properties:

# com.sun.management.jmxremote.ssl.enabled.cipher.suites

# com.sun.management.jmxremote.ssl.enabled.protocols

# com.sun.management.jmxremote.ssl.need.client.auth

# If the two properties below are true at the same time, i.e.

# com.sun.management.jmxremote.ssl=true

# com.sun.management.jmxremote.registry.ssl=true

# then the RMIServer remote object and the RMI registry are

# both exported with the same SSL/TLS RMI Socket Factories.

#

# For using an SSL/TLS protected RMI registry use the following line

com.sun.management.jmxremote.registry.ssl=true

#

# ################ RMI User authentication ################

#

# com.sun.management.jmxremote.authenticate=true|false

# Default for this property is true. (Case for true/false ignored)

# If this property is specified as false then no authentication is

# performed and all users are allowed all access.

#

# For RMI monitoring without any checking use the following line

com.sun.management.jmxremote.authenticate=false

#

# ################ RMI Login configuration ###################

#

# com.sun.management.jmxremote.login.config=<config-name>

# Specifies the name of a JAAS login configuration entry to use when

# authenticating users of RMI monitoring.

#

# Setting this property is optional - the default login configuration

# specifies a file-based authentication that uses the password file.

#

# When using this property to override the default login configuration

# then the named configuration entry must be in a file that gets loaded

# by JAAS. In addition, the login module(s) specified in the configuration

# should use the name and/or password callbacks to acquire the user's

# credentials. See the NameCallback and PasswordCallback classes in the

# javax.security.auth.callback package for more details.

#

# If the property "com.sun.management.jmxremote.authenticate" is set to

# false, then this property and the password & access files are ignored.

#

# For a non-default login configuration use the following line

# com.sun.management.jmxremote.login.config=<config-name>

#

# ################ RMI Password file location ##################

#

# com.sun.management.jmxremote.password.file=filepath

# Specifies location for password file

# This is optional - default location is

# $JRE/lib/management/jmxremote.password

#

# If the property "com.sun.management.jmxremote.authenticate" is set to

# false, then this property and the password & access files are ignored.

# Otherwise the password file must exist and be in the valid format.

# If the password file is empty or non-existent then no access is allowed.

#

# For a non-default password file location use the following line

# com.sun.management.jmxremote.password.file=filepath

#

# ################ RMI Access file location #####################

#

# com.sun.management.jmxremote.access.file=filepath

# Specifies location for access file

# This is optional - default location is

# $JRE/lib/management/jmxremote.access

#

# If the property "com.sun.management.jmxremote.authenticate" is set to

# false, then this property and the password & access files are ignored.

# Otherwise, the access file must exist and be in the valid format.

# If the access file is empty or non-existent then no access is allowed.

#

# For a non-default password file location use the following line

# com.sun.management.jmxremote.access.file=filepath