1.1.1

Table Of Contents
connection (boot)Property Type
n/aPrex
jmx-manager-access-file
By default the JMX Manager allows full access to all MBeans by any client. If this property is set to the name of
a le, then it can restrict clients to only reading MBeans; they cannot modify MBeans. The access level can be
Description
congured differently in this le for each user name dened in the password le. For more information about the
format of this le see Oracle's documentation of the
com.sun.management.jmxremote.access.file system property. Ignored if
jmx-manager is false or if jmx-manager-port is zero. See Setting Up JMX Manager Authentication
on page 297.
not setDefault Value
connection (boot)Property Type
n/aPrex
jmx-manager-bind-address
By default, the JMX Manager when congured with a port listens on all the local host's addresses. You
can use this property to congure which particular IP address or host name the JMX Manager will listen
on. This property is ignored if jmx-manager is false or jmx-manager-port is zero.
Description
not setDefault Value
connection (boot)Property Type
n/aPrex
jmx-manager-hostname-for-clients
Hostname given to clients that ask the locator for the location of a JMX Manager. By default the IP address
of the JMX Manager is used. However, for clients on a different network, you can congure a different
Description
hostname to be given to clients. Ignored if jmx-manager is false or if jmx-manager-port
is zero.
not setDefault Value
connection (boot)Property Type
n/aPrex
jmx-manager-http-port
Not used. If you require HTTP access for JMX management, use a standalone JMX Agent instead
of a manager node. See Using a vFabric SQLFire JMX Agent on page 298.
Description
8080 (not used)Default Value
connection (boot)Property Type
n/aPrex
vFabric SQLFire User's Guide332
vFabric SQLFire Reference